All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] DTB /OF_TREE Newbie and U-boot
Date: Thu, 18 Jan 2007 13:07:16 -0600	[thread overview]
Message-ID: <45AFC564.6080609@freescale.com> (raw)
In-Reply-To: <000301c73b2f$635eb000$6405a8c0@absolut>

Russell McGuire wrote:

> I realize now that for SOC chips such as a MPC8360E that passing a DTB 
> structure into the bootm command is probably a required step??? Is this 
> True?

Yes.

> If so I see in some cases that this structure might be partly 
> constructed within the U-boot code, at least I see code doing something 
> with OF_TREE?s.

Yes, U-Boot updates the tree with its own values.

> 1)       Is the U-boot compilation process generating a .dtb structure 
> that we can burn into firmware, at least or certain CPU architectures?

No.  You need to use the DTC compiler, which is available here: 
http://www.jdl.com/git_repos/?p=dtc.git

> 2)       Is this a manual process that requires an outside dtb compiler, 

Yes.

> and if so why is U-boot code dealing with this?

Because the Linux kernel is currently coded such that the boot loader must pass 
the DTB to it.  To reduce the amount of dual-maintenance, U-Boot can take some 
of the data that it knows about, and put that into the tree.

> 3)       Is this built into the bd_info structure?

I'm not sure I understand.  The DTB itself is not part of U-Boot, but U-Boot can 
parse the tree and modify it.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-01-18 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 18:35 [U-Boot-Users] DTB /OF_TREE Newbie and U-boot Russell McGuire
2007-01-18 19:07 ` Timur Tabi [this message]
2007-01-18 19:32   ` Jerry Van Baren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45AFC564.6080609@freescale.com \
    --to=timur@freescale.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.