[U-Boot] [PATCH] Add support for setting environment variable from RAM.

This is useful for allowing scripts to read environment variables from file, among other things. This is a slightly modified version of what Alessandro submitted to the mailing list last July: http://www.mail-archive.com/u-boot-us...@lists.sourceforge.net/msg07932.html I changed the name

[U-Boot] [PATCH] Add support for setting environment variable from RAM.

This is useful for allowing scripts to read environment variables from file, among other things. This is a slightly modified version of what Alessandro submitted to the mailing list last July: http://www.mail-archive.com/u-boot-us...@lists.sourceforge.net/msg07932.html I changed the name

Re: [U-Boot] [PATCH] Add support for setting environment variable from RAM.

Hi Eric, On Tue, 2009-02-03 at 08:28 -0700, Eric Nelson (Boundary Devices) wrote: > / > + * Set a new environment variable from RAM. > + * Requires three arguments: the variable name, a memory address and a > length. > + * >

Re: [U-Boot] [PATCH] Add support for setting environment variable from RAM.

Wolfgang Denk wrote: > Dear Eric, > > In message <4988936e.3070...@boundarydevices.com> you wrote: >>> In the email thread you mentioned above, Detlev mentions 2 alternatives >>> to the "ramenv" command - loading a uImage script and running it via >>> autoscr, or modifying autoscr to be able to ra

Re: [U-Boot] [PATCH] Add support for setting environment variable from RAM.

Dear Eric Nelson, In message <4988bbc0.4070...@boundarydevices.com> you wrote: > > As I mentioned, the customer requesting the feature has a regulatory > requirement any time __code__ changes. They have interpreted boot loader > scripts as being executable, so they have to write checks if the scri

Re: [U-Boot] [PATCH] Add support for setting environment variable from RAM.

Hello Peter, Peter Tyser wrote: > Hi Eric, > > On Tue, 2009-02-03 at 08:28 -0700, Eric Nelson (Boundary Devices) wrote: >> / >> + * Set a new environment variable from RAM. >> + * Requires three arguments: the variable name,

Re: [U-Boot] [PATCH] Add support for setting environment variable from RAM.

Dear Eric, In message <4988936e.3070...@boundarydevices.com> you wrote: > > > In the email thread you mentioned above, Detlev mentions 2 alternatives > > to the "ramenv" command - loading a uImage script and running it via > > autoscr, or modifying autoscr to be able to raw files (non-uImages). >

Re: [U-Boot] [PATCH] Add support for setting environment variable from RAM.

Dear "Eric Nelson (Boundary Devices)", In message <1233631739-17568-1-git-send-email-eric.nel...@boundarydevices.com> you wrote: > This is useful for allowing scripts to read environment variables from > file, among other things. > > This is a slightly modified version of what Alessandro submitt

Re: [U-Boot] [PATCH] Add support for setting environment variable from RAM.

Wolfgang Denk wrote: > Dear "Eric Nelson (Boundary Devices)", > > In message > <1233631739-17568-1-git-send-email-eric.nel...@boundarydevices.com> you wrote: >> This is useful for allowing scripts to read environment variables from >> file, among other things. >> >> This is a slightly modified ve

Re: [U-Boot] [PATCH] Add support for setting environment variable from RAM.

Dear Eric Nelson, In message <498b56fe.1080...@boundarydevices.com> you wrote: > > > Please use a script image with "askenv" instead. > > > Thanks for the tip. I hadn't noticed askenv previously. Sorry, typo. I meant "autoscr". Best regards, Wolfgang Denk -- DENX Software Engineering GmbH,

Re: [U-Boot] [PATCH] Add support for setting environment variable from RAM.

Wolfgang Denk wrote: > Dear Eric Nelson, > > In message <498b56fe.1080...@boundarydevices.com> you wrote: >>> Please use a script image with "askenv" instead. >>> >> Thanks for the tip. I hadn't noticed askenv previously. > > Sorry, typo. I meant "autoscr". > Muscle memory. Can't live with it, c