On Tuesday 06 March 2012 12:07:10 you wrote:
> On Mon, Mar 5, 2012 at 8:27 PM, Mike Frysinger wrote:
> > also, doesn't the existing `env import`
> > do this ?
> >
> > * env import [-d] [-t | -b | -c] addr [size]
> > * -d: delete existing environment before importing;
> > * otherwise overw
Dear Doug Anderson,
In message
you wrote:
>
> It's not quite possible to just import the default from the saved for two
> reasons:
> 1. I don't know of any way to import the default. It's not stored at any
> well-known address or with any well-known size.
Then save it to a well-known address.
Mike,
On Mon, Mar 5, 2012 at 8:27 PM, Mike Frysinger wrote:
> this is kind of a crappy interface.
>
Agreed.
> also, doesn't the existing `env import`
> do this ?
> * env import [-d] [-t | -b | -c] addr [size]
> * -d: delete existing environment before importing;
> * otherwise overwr
On Tuesday 14 February 2012 18:30:55 Doug Anderson wrote:
> Create a saved enviroment with this env variable set to "1" to merge the
> saved environment on top of the default environment. The idea is that your
> saved environment would just contain variables that you'd like to override
> from the
This is a useful mechanism any time you have a way to update the
saved environment outside of u-boot. This can be a tool like
fw_setenv or could be a tool like we use in Chrome OS that
modifies the variables in a binary image before flashing (see
factory_setup/update_firmware_vars.py in
http://git
5 matches
Mail list logo
