On Sun, Mar 25, 2018 at 11:50 AM, Wolfgang Denk <[email protected]> wrote: > Dear Alex, > > In message > <CAO5Uq5Tvbc_YumNXrFC8YHkRiADzEzKjr4bYb_Q=usvst1c...@mail.gmail.com> you > wrote: >> I'm trying to set up a configuration where I've largely got a hardcoded >> environment (ENV_IS_NOWHERE) with a very small list of variables that come >> from a loadable environment (ENV_IS_IN_FAT for my use case) - things like >> serial# and regulatory region. Even then I want them largely set once in >> the factory and not really written again. >> >> I could've sworn I'd seen patches that implemented this kind of thing >> around the time of the environment rework, but I'm failing to find them >> either merged or pending. > > Why do you need code to do that?
I don't... just thinking about it the wrong way! > Why can't you just "env import" > these additional fragments as part of your hard coded startup > sequence? > Other than wanting to filter the variables that can come in that way, it does everything I need. In fact with sufficient care I probably don't even need to filter it. Thanks for the pointer! -- Alex Kiernan _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
