On Wed, Aug 14, 2013 at 10:44:22AM -0600, Stephen Warren wrote: ... > Certainly, that approach actively causes issues whereby every distro > must somehow install ensure the DTBs get into /boot, rather than the > system "just providing" them somehow. Having distros have to manage this > probably doesn't scale very well, hence people are advocating that the > DTB be part of the firmware image, so it's already there without the > distro having to put it into the filesystem. I advocate that it be stored on the same media as the bootloader (eg flash), but separate from the bootloader, similar to how u-boot has a separate flash partition for it's environment. This way, a distro can upgrade the DTB if they _choose_ to, but managing the dtbs *isn't* mandatory. It makes bootloader init via DT a little more difficult, since the flash chip/bus parameters would have to be hardcoded into the bootloader. Plus the offset to the dtb. But bootloader init via DT is at best a nice-to-have, imho. I don't think it should get in the way of a properly upgradeable system. thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
