On Mon, Aug 05, 2013 at 07:29:33AM +0200, Wolfgang Denk wrote: > Dear Rob Herring, > > In message > <CAL_JsqK++KbAajYtp9UnJuHWd=f8pjhsk0x3hzf73pchdl_...@mail.gmail.com> you > wrote: > > > > > Maybe can be mkenvimage a solution (tools/mkenvimage) ? It creates an > > > environment image from a simple ASCII text. The resulting image could be > > > concatenated together with u-boot and in CONFIG_EXTRA_ENV_SETTINGS we > > > could have for all boards a way to load it. Only a first idea, but as we > > > recognize the issue, any idea to solve it ? > > > > I definitely agree that we should move this out of C code and support > > standalone text files as input. IIRC, CONFIG_EXTRA_ENV_SETTINGS is > > replaced by any separate environment. I think it also needs to support > > being merged with a separate environment. > > Why would you ever want to compile this into U-Boot at all? Then any > changes you need to make mean compiling and installing a new U-Boot, > which is something you normally don't want to do. > > U-Boot is perfectly able to import such settings from text files (or > text blobs stored somewhere, even attached to the U-Boot image, if you > want), so just use the text files separately, instead of hard > compiling them into the code.
But we have to start _somewhere_ with a compiled-in set of defaults. Yes, some boards are easily updatable (it's just an SD card), but on others it's not. And there's a strong desire on the generic distro side (and on a lot of kernel hackers sides) to treat U-Boot as never-touch binaries. What ships is what's used. So a default that tries to load a controlable file is what started all of the boot.scr or uEnv.txt stuff. -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
