On 08/08/2012 02:25 PM, Rob Herring wrote:
Stephen Warren <swarren@...> writes:
Related to this topic also are:
93d87d5 tegra: define fdt_load/fdt_high variables 4878343 tegra: bootcmd enhancements
I do like this and it's similar to what I've done for highbank. Actually, yours is a bit more flexible. We have the additional need to select a boot source by a boot device selection register which is set via ipmi.
So how do we combine these and have some level of enforcement? There's not much concept of common/minimum environment in u-boot. The default environment is entirely optional. I worry leaving it as just environment settings does not "encourage" people to use it.
Perhaps the issue isn't so much enforcement at a U-Boot level, but more that we create some standard for what boot.scr/... can expect to exist in the environment, and say:
distros: this is what you can rely upon in your boot.scr.
board vendors: this is what you need to provide in order for common Linux distros to work out-of-the-box.
Hopefully that's enough incentive for people to make their U-Boots work? At least for Tegra I think it will be, but we are pretty early on in upstream U-Boot terms, so we're quite flexible right now.