From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Date: Mon, 23 Apr 2007 14:45:43 -0500 Subject: [U-Boot-Users] RFC: hidden environment variables In-Reply-To: <1177357190.3904.80.camel@saruman.qstreams.net> References: <462CE302.7030302@freescale.com> <1177356492.3904.78.camel@saruman.qstreams.net> <009701c785de$2e8a7bd0$9003960a@atmel.com> <1177357190.3904.80.camel@saruman.qstreams.net> Message-ID: <462D0CE7.1060009@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: > Sure, but I don't think info overload was Timur's primary concern. I > thought he wanted to make the variables RO from the command prompt. > Maybe I misunderstood. No, I just wanted a way for U-Boot code to store data in the environment without interference from the user. The reason I want to use the environment is that it already exists, and it already has a mechanism for saving itself to flash. So, the obvious question is, "well, what kind of data?". I have an idea where the user can tell U-Boot how the board is jumpered, so that when it boots the kernel, it can modify the device tree on-the-fly based on the jumper settings. I don't want to use the setenv command, however, to specify these jumper settings. I want to use a new command that does some parameter checking and performs other operations. -- Timur Tabi Linux Kernel Developer @ Freescale