public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Williams <gfi8d1h02@sneakemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: boot commands
Date: Wed, 31 Mar 2004 13:15:02 -0800	[thread overview]
Message-ID: <13319-35603@sneakemail.com> (raw)
In-Reply-To: <20040331205714.15B80C10A4@atlas.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."

      reply	other threads:[~2004-03-31 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <406B2558.2070000@icarus.com>
2004-03-31 20:36 ` [U-Boot-Users] Re: boot commands Stephen Williams
2004-03-31 20:57   ` Wolfgang Denk
2004-03-31 21:15     ` Stephen Williams [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13319-35603@sneakemail.com \
    --to=gfi8d1h02@sneakemail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox