From: Kim Phillips <kim.phillips@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Device tree home
Date: Thu, 18 Jan 2007 15:38:15 -0600 [thread overview]
Message-ID: <20070118153815.034af9fc.kim.phillips@freescale.com> (raw)
In-Reply-To: <45AFC3A8.8090802@smiths-aerospace.com>
On Thu, 18 Jan 2007 13:59:52 -0500
Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com> wrote:
> Kim Phillips wrote:
> > 3. does a subsystem maintainer get leverage into changes made in the
> > higher level components of Das U-Boot? E.g., I'm still a firm
> > believer that the device tree source should live in the bootloader ;)
> >
> > Kim
>
> Hi Kim,
>
> Back to the fdt/of methodology (I started a new thread since it is kind
> of a new topic)... I have a hot project that I have not quite gotten to
> yet to integrate the fdt more tightly into u-boot rather than it being
> some magic wedged into bootm.
>
> The ultimate goal (for me) is to have an option where the u-boot env
> gets stored in a fdt rather than the current env so that the fdt really
> is native to u-boot. The goal would be that all the current env
> commands would Just Work[tm].
>
I'm not sure I understand the benefit of this - I thought the only parts of the device tree likely to get changed on the command line are the mac addresses and the chosen node's bootargs property, which today's u-boot handles well.
My belief is merely that the device tree data should belong in the u-boot image; they are both equally board specific.
Kim
next prev parent reply other threads:[~2007-01-18 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 18:59 [U-Boot-Users] Device tree home Jerry Van Baren
2007-01-18 21:38 ` Kim Phillips [this message]
2007-01-18 21:50 ` Timur Tabi
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=20070118153815.034af9fc.kim.phillips@freescale.com \
--to=kim.phillips@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