On Tue, Aug 6, 2013 at 12:50 PM, Stephen Warren <swar...@wwwdotorg.org> wrote: > On 08/06/2013 05:37 AM, Wolfgang Denk wrote: >> Dear Rob Herring, >> >> In message >> <CAL_JsqJTg4CVfk0o9hLd4ZVksj+DNEsKLjcv6T7-6F-=br+...@mail.gmail.com> you >> wrote: >>> >>>> 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. >>> >>> You may want to have factory default and "user" settings. Building in >>> the factory settings would be one way to accomplish that. >> >> No. Handling these independently, outside of the compiled U-Boot image >> is as easy, and much more flexible. >> >>>> 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. >>> >>> In my case, I don't want to compile the environment into u-boot. But >>> some people do as I copied my scripts from Tegra which has them >>> built-in. > > We have the *default* environment built-in, which is used when no valid > environment is found in flash. If there's an environment in flash, it > gets used rather than the built-in default.
How can someone 'overwrite' the default environment from system or when generating a FIT image? I am interested in let my customers to revert back to a sane default running: env -f -d -a saveenv -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://projetos.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
