From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] mx51evk: savenv or env save command does not work
Date: Wed, 17 Nov 2010 08:44:32 +0100 [thread overview]
Message-ID: <4CE387E0.10809@denx.de> (raw)
In-Reply-To: <AANLkTikB6NYTdz=4cMr_RDuhVXQjTa9zUKaed+vW4C+s@mail.gmail.com>
On 11/17/2010 02:44 AM, Jason Liu wrote:
>
> I set it according to the following reason,
>
> - Keep the same setting as the original when you commit the mx51
> support patch. Why you select 128KB? :)
No idea, I cannot remember, probably I missed the point. When I commit
the mx51 stuff, there is no possibility to store the environment, so
there are no drawbacks, but I commit some dead code.
> - As I looked through other platform such as OMAP4 for MMC ENV
> setting, it's also set for 128KB
Well, probably the value was copied even in from a flash setup. In case
of flash (NAND or NOR) we must reserved at least 1 sector to store the
environment, and because nowadays flash chips are bigger as in the past
it is very common that the sector size is 128KB or even larger.
However, this does not apply to MMC. A large environment space when we
do not need requires more time to save and to read, last thing has
consequences on the boot time.
> - Leave much room for the user to store customer env.
I do not think there someone needing 128KB to store the environment....
> It's always the trade-off, set to 512B or less will save some time
> according to 128KB, but it will face much risk to change the code
> frequently to meet the increasing env size requirement.
> what's the size do you think is suitable?
I have expected a value such as 8-16KB.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2010-11-17 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 8:41 [U-Boot] [PATCH 1/1] mx51evk: savenv or env save command does not work Jason Liu
2010-11-16 17:28 ` Stefano Babic
2010-11-17 1:44 ` Jason Liu
2010-11-17 7:03 ` Wolfgang Denk
2010-11-17 7:29 ` Jason Liu
2010-11-17 7:42 ` Wolfgang Denk
2010-11-17 21:28 ` Scott Wood
2010-11-17 21:50 ` Wolfgang Denk
2010-11-17 7:54 ` Stefano Babic
2010-11-17 8:03 ` Jason Liu
2010-11-17 13:00 ` Wolfgang Denk
2010-11-17 7:44 ` Stefano Babic [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=4CE387E0.10809@denx.de \
--to=sbabic@denx.de \
--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