On Mon, Sep 12, 2011 at 03:04:23PM -0700, Simon Glass wrote: > This device tree is for U-Boot's own use and is not necessarily the > same one as is passed to the kernel.
Are there plans to keepup with being able to use a kernel generated fdt? eg effectively ignoring things we don't care about like sound cards and wifi? I can see definite advantages for manufacturers to be able to roll one kernel and one bootloader across a product line, then one fdt per model. It almost makes this whole mess make sense. :-) The kirkwood SoC would be a good example. Do you have a git tree up that I could base off of? git.chromium.org's version of u-boot doesn't seem to have your code... thx, Jason. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
