From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MPC8360 Rev 2 patch?
Date: Fri, 09 Feb 2007 15:53:40 -0600 [thread overview]
Message-ID: <45CCED64.2040400@freescale.com> (raw)
In-Reply-To: <45CCEB2F.1010902@sgi.com>
Steven Hein wrote:
> At this point, I know *nothing* about device trees or OF......
> Is this something that lives outside of u-boot?
Yes. The device tree source is in arch/powerpc/boot/dts in the kernel. You
compile that with dtc into a dtb, transfer the dtb to U-Boot via tftp, and then
boot the kernel, passing the dtb as the third parameter.
> I guess someone probably needs to point me to some "device trees
> for dummies" info........
I don't know where such a document exists.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-02-09 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 23:15 [U-Boot-Users] MPC8360 Rev 2 patch? Steven Hein
2007-02-05 23:20 ` Kim Phillips
2007-02-08 16:28 ` Steven Hein
2007-02-08 16:59 ` Kim Phillips
2007-02-08 22:50 ` Steven Hein
2007-02-09 20:57 ` Kim Phillips
2007-02-09 20:59 ` Timur Tabi
2007-02-09 21:44 ` Steven Hein
2007-02-09 21:53 ` Medve Emilian-EMMEDVE1
2007-02-09 21:53 ` Timur Tabi [this message]
2007-02-09 22:16 ` Ben Warren
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=45CCED64.2040400@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox