[U-Boot-Users] using a flat device tree to drive u-boot config

[Robert Schwebel <r.schwebel@pengutronix.de>]

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.

The idea is interesting; we have already thought about generating device
trees in u-boot-v2 from the driver model.

As u-boot-v2 has a module concept (think of it as in linux -> insmod
plus EXPORT_SYMBOL), it would even be possible to change the driver
model to device tree transformation by uploading a new module; this is
necessary, as upstream maintainers tend to break oftree semantics with
almost every kernel release - seems to be part of the design :-)

However, no time to investigate this further atm.

rsc
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9