From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nishanth Menon Date: Thu, 24 Aug 2006 06:55:55 -0500 Subject: [U-Boot-Users] Multiple flash Support In-Reply-To: <20060824094057.2C56D353A63@atlas.denx.de> References: <20060824094057.2C56D353A63@atlas.denx.de> Message-ID: <44ED93CB.6070901@gmail.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 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