public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Russell McGuire <rmcguire@videopresence.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] DTB /OF_TREE Newbie and U-boot
Date: Thu, 18 Jan 2007 10:35:11 -0800	[thread overview]
Message-ID: <000301c73b2f$635eb000$6405a8c0@absolut> (raw)

All,

 

Now that I have u-boot up and running on my MPC8360E I am going to begin
trying to boot Linux 2.6.15 or newer.

However, I keep seeing mention of these Device Tree Blobs and OF_TREE's
throughout the code.

 

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?

 

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.

 

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

2)       Is this a manual process that requires an outside dtb compiler, and
if so why is U-boot code dealing with this?

3)       Is this built into the bd_info structure?

 

Or I guess if somebody just has a documentation link I can just read, I
didn't see anything about OF_TREE's in the DULG manual.

 

Thanks,

 

-Russ

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20070118/65eecfba/attachment.htm 

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 18:35 Russell McGuire [this message]
2007-01-18 19:07 ` [U-Boot-Users] DTB /OF_TREE Newbie and U-boot Timur Tabi
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='000301c73b2f$635eb000$6405a8c0@absolut' \
    --to=rmcguire@videopresence.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox