-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 08/07/2013 07:16 PM, Dennis Gilmore wrote:
On Wed, 7 Aug 2013 13:09:08 -0500 Matt Sealey neko@bakuhatsu.net wrote:
Define "transparently load".
omap systems have a findfdt command that gives you the dtb file name expected for the board. I expect that u-boot will know the name of the file for its dtb. Hardware vendors would have the choice of how they implement loading the dtb. They could load a dtb shipped in onboard storage or load one from our common dtb directory. The user or distro can specifiy that the distro dtb be used
Why wouldn't you just mandate that there are certain features enabled and that all platforms need a boot script - therefore abstracting the board name, dtb name, location, kernel version/naming scheme from the bootloader as a whole?
because we don't need a boot script. we as distros shouldn't need to worry about things like memory locations. we should only need to load a kernel, initramfs, and pass boot args. http://lists.denx.de/pipermail/u-boot/2013-August/160080.html is my proposal to u-boot upstream on defining a standard platform. you are free to use a boot script still, however I strongly feel that using a extlinux config with the sysboot command offers a much better user experience.
One thing I wanted to bring back to this list as well is that I think part of the logic provided needs to come from outside the flashed-in-and-forever-locked (as some folks would like to see it) side of U-Boot. This is part of the discussion I'd like to see happen with the rest of the U-Boot list as well, but the distro must not have to worry about memory locations but must worry about providing the rest of their experience. The distro wants to provide the user with a consistent look and feel and experience from architecture to architecture and that involves getting your 'whatever' in front of them asap.
- -- Tom