From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Date: Mon, 23 Apr 2007 14:50:47 -0500 Subject: [U-Boot-Users] RFC: hidden environment variables In-Reply-To: <1177356492.3904.78.camel@saruman.qstreams.net> References: <462CE302.7030302@freescale.com> <1177356492.3904.78.camel@saruman.qstreams.net> Message-ID: <462D0E17.20106@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Ben Warren wrote: > This is a pretty serious drawback. If you really want to have > persistent storage for autonomous code, maybe we should look at a way of > allocating a block of persistent storage (either flash or serial EEPROM) > outside of ENV that gets saved when modified. I'm looking for something that's much more generic. I want to use an existing infrastructure, and I want something that's not hardware-specific. >> One advantage of this feature is that we can develop new commands that store data >> permanently without having to add hooks into _do_setenv(). >> > I guess I don't see why anything needs to be hidden. Well, it doesn't *have* to be hidden, it just makes things simpler that way. If the variable can't be touched by the user, then I don't have to hook into the _do_setenv() command. -- Timur Tabi Linux Kernel Developer @ Freescale