From: Grant Likely <grant.likely@secretlab.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] using a flat device tree to drive u-boot config
Date: Mon, 28 Jul 2008 11:40:43 -0600 [thread overview]
Message-ID: <20080728174043.GA21534@secretlab.ca> (raw)
In-Reply-To: <A8499417-7011-4DFA-B453-B6C05EC6AEAB@kernel.crashing.org>
On Mon, Jul 28, 2008 at 10:07:49AM -0500, Kumar Gala wrote:
> One topic that come up during OLS in discussions and u-boot BOF was
> the idea of driving u-boot configuration from a device tree instead of
> from "config.h". I was wondering if anyone has actually looked at
> doing this.
>
> One question I have is how does (or should) u-boot identify where to
> find the device tree. I think the idea would be that this "area"
> could be easily reflashed with a new blob to get a new configuration.
In principle I like the idea of having configuration retrieved from the
device tree blob, but the idea of reflashing the blob in the context of
u-boot scares me. In particular, if u-boot depends too much on the
presence of the blob, then it becomes a method of bricking a board if
users are able/expected to reflash the blob.
g.
next prev parent reply other threads:[~2008-07-28 17:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 15:07 [U-Boot-Users] using a flat device tree to drive u-boot config Kumar Gala
2008-07-28 17:28 ` Ben Warren
2008-07-28 17:32 ` Scott Wood
2008-07-28 17:35 ` Ben Warren
2008-07-28 17:43 ` Scott Wood
2008-07-28 18:05 ` Ben Warren
2008-07-28 18:59 ` Scott Wood
2008-07-29 8:26 ` André Schwarz
2008-07-29 8:41 ` Wolfgang Grandegger
2008-07-29 9:09 ` André Schwarz
2008-08-03 1:10 ` Jerry Van Baren
2008-07-29 16:41 ` Timur Tabi
2008-07-28 17:40 ` Grant Likely [this message]
2008-07-28 18:17 ` Kumar Gala
2008-07-28 19:07 ` Scott Wood
2008-07-29 7:54 ` Haavard Skinnemoen
2008-07-28 18:13 ` Wolfgang Grandegger
2008-07-28 18:19 ` Kumar Gala
2008-07-29 14:30 ` Jon Loeliger
2008-07-29 15:51 ` Robert Schwebel
2008-07-29 15:51 ` Robert Schwebel
2008-07-29 16:46 ` Timur Tabi
2008-08-03 1:58 ` Jon Smirl
2008-08-03 7:51 ` Wolfgang Denk
2008-08-03 12:57 ` Jon Smirl
2008-08-03 15:47 ` Wolfgang Denk
2008-08-03 17:49 ` Timur Tabi
2008-08-03 19:06 ` Grant Likely
2008-08-03 20:08 ` Timur Tabi
2008-08-04 8:08 ` Albert ARIBAUD
2008-08-04 7:16 ` Jens Gehrlein
2008-08-03 19:45 ` Wolfgang Denk
2008-08-04 14:33 ` Timur Tabi
2008-08-04 15:31 ` Wolfgang Denk
2008-08-04 15:36 ` Timur Tabi
2008-08-03 20:47 ` Andrew Dyer
2008-08-04 15:02 ` Jon Smirl
2008-08-04 15:05 ` 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=20080728174043.GA21534@secretlab.ca \
--to=grant.likely@secretlab.ca \
--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