From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Williams Date: Wed, 31 Mar 2004 13:15:02 -0800 Subject: [U-Boot-Users] Re: boot commands In-Reply-To: <20040331205714.15B80C10A4@atlas.denx.de> References: <20040331205714.15B80C10A4@atlas.denx.de> Message-ID: <13319-35603@sneakemail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk wd-at-denx.de |u-boot-users| wrote: > In message <31968-89888@sneakemail.com> you wrote: > >>Arg! It seems like *all* the autoboot related variables, including >>BOOTARGS and AUTOBOOT_PROMPT are ignored if there is *any* >>environment. This makes no sense to me. Surely people want to > > > Wrong. They are not ignored. They are used to define the DEFAULT > environment. > > >>set per-board stuff in environment and keep common autoboot >>settings compiled in. My BOOTCOMMAND and BOOTARGS together are >>too large to fit into my 256byte EEPROM. > > > You misunderstand how the environment works. There are no two > separate sets, it is only one set, which gets pre-initialized form > the default settings, which get used in case of corrupted checksum or > so... Ah, I get it now. And yes, it does make sense. I was able to find more EEPROM space and when I cleared out the EEPROM, I got my compiled in values, which I was then able to store into the EEPROM and use there from then on. Autoboot is happy now, and so am I. Thanks, -- Steve Williams "The woods are lovely, dark and deep. steve at XXXXXXXXXX But I have promises to keep, http://www.XXXXXXXXXX and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."