From: John Otken <jotken@softadvances.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Leonid <Leonid@a-k-a.net>, linuxppc-embedded@ozlabs.org
Subject: Re: uboot environment variables size for Yosemite board.
Date: Mon, 17 Jul 2006 06:02:33 -0500 [thread overview]
Message-ID: <44BB6E49.3030505@softadvances.com> (raw)
In-Reply-To: <20060717070018.21ED1353C61@atlas.denx.de>
Wolfgang Denk wrote:
> In message <FAB00A8DC59FAB42B13C2B3B0F6877010D14478B@ehost011-3.exch011.intermedia.net> you wrote:
>> I'm using uboot-1.1.4 for AMCC PPC440E Yosemite board. I've downloaded
>
> Note that this is off topic here. You should have posted this on the
> U-Boot-Users mailing list instead.
>
>> this uboot from DENX site. It uses EEPROM to store environment
>> variables. Since EEPROM on Yosemite board is only 512 bytes, there can
>> not be more environment variables which is not very convenient.
>
> Thisi s wrong. The Yosemite configuration uses (like most (all?) AMCC
> eval boards - two redundand flash sectors to store the environment.
> And available environment size is 8 kB:
He has an older Yosemite. The original Yosemite U-Boot used the EEPROM
for environment variables.
> => print
> ...
> Environment size: 1355/8187 bytes
>
>> There is theoretical possibility to save these variables on flash (64M
>> from which I use only part) and yosemite.h header file even has defines,
>> allowing this option. But is it going work in reality? What is simplest
>> way for Yosemite board to increase environment variables storage space?
>
> I have no idea where you got your board configuration from, but it is
> definitely not current code, nor the binary image at
> ftp://ftp.denx.de/pub/u-boot/images/amcc/yosemite/u-boot.bin
>
> The current code does use (redundand) flash for environment storage.
>
> Best regards,
>
> Wolfgang Denk
>
prev parent reply other threads:[~2006-07-17 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 5:09 uboot environment variables size for Yosemite board Leonid
2006-07-17 7:00 ` Wolfgang Denk
2006-07-17 11:02 ` John Otken [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=44BB6E49.3030505@softadvances.com \
--to=jotken@softadvances.com \
--cc=Leonid@a-k-a.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.