From: Nishanth Menon <menon.nishanth@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Multiple flash Support
Date: Thu, 24 Aug 2006 06:55:55 -0500 [thread overview]
Message-ID: <44ED93CB.6070901@gmail.com> (raw)
In-Reply-To: <20060824094057.2C56D353A63@atlas.denx.de>
Wolfgang Denk stated on 8/24/2006 4:40 AM:
> In message <000e01c6c752$e8502510$654765d5@atmel.com> you wrote:
>> Maybe this is too late,
>> but it may make sense to add an 8 kB serial EEPROM to a board
>> (which is probably a development board anyway)
>> and store the environment in this chip.
>
> No! Please DON'T do this.
Agreed. It is too late for that and to top it all, our marketing folks
will not like the extra cost :(.
Ulf Samuelsson stated on 8/24/2006 2:57 AM:
> If you can read the switch, you can make decisions inside your boot.
yes that is the implementation we have currently done.
> I can see a point in the request.
> If it is a board that is sold as a development tool, and one of their
customers
> wants to download and upgrade the u-boot binary from their website,
> then it is a significant chance that the customer will download the
wrong image to the flash memory
> This results in a call the support team, which is costly and the
customer problem will often reflect on them.
Aaah, Ulf, you are reading my mind :).
The base question remains: Is the current U-Boot architecture flexible
enough to support this? if not, what is the suggested approach?
Regards,
Nishanth Menon
next prev parent reply other threads:[~2006-08-24 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 2:30 [U-Boot-Users] Multiple flash Support Nishanth Menon
2006-08-24 7:04 ` Wolfgang Denk
2006-08-24 7:57 ` Ulf Samuelsson
2006-08-24 9:40 ` Wolfgang Denk
2006-08-24 11:05 ` Ulf Samuelsson
2006-08-24 11:55 ` Nishanth Menon [this message]
2006-08-24 12:25 ` Ulf Samuelsson
[not found] <20060824122227.3A440353A61@atlas.denx.de>
2006-08-24 13:02 ` Nishanth Menon
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=44ED93CB.6070901@gmail.com \
--to=menon.nishanth@gmail.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 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.