Hi Jason, On Mon, Sep 12, 2011 at 4:37 PM, Jason <u-b...@lakedaemon.net> wrote: > 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 would like to use the kernel fdt unmodified, so yes. Unused things in the fdt bloat U-Boot but shouldn't otherwise matter. It is also possible to create a tool to filter them out. > > 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. Yes that's the intent. You still need CONFIGs for enabling each feature (i.e. bringing in the code), but configuring it can be done in common with the kernel. > > 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... You probably need to look at a branch: http://git.chromium.org/gitweb/?p=chromiumos/third_party/u-boot.git;a=shortlog;h=refs/heads/chromeos-v2011.06 This is based on U-Boot 2011.06. Regards, Simon > > thx, > > Jason. > _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot