From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joachim Jaeger Date: Fri, 14 Jul 2006 09:10:37 +0200 Subject: [U-Boot-Users] skipping bad blocks when erasing nand In-Reply-To: References: <000001c6a6ca$bd0b3230$a134800a@RudiDell> <20060713224545.0CD89353A2A@atlas.denx.de> Message-ID: <44B7436D.7010506@fsforth.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi, Dave Hylands wrote: > Hard-drives have bad blocks, but you don't see them being reported > when you format. > > Somebody who knows that NAND chips have bad blocks as a normal course > of events won't be suprised to see them. People (i.e. end users - not > the programmers) who are unaware that NAND chips can have bad blocks > will be suprised, so the whole thing about bad blocks being normal now > has to be documented. > > I think that if a block is marked as bad, then doing an erase should > just ignore blocks that already marked bad. However, if a block goes > bad as a result of the formatting, then that's worth reporting > (although, this is also a fact of life). I also think the patch from David is OK, because the bad blocks are not skipped, which would be fatal crossing partition boundaries, but just ignored. I think even reporting about these ignored blocks isn't necessary. Instead it would be much more interesting to know about the really bad block free space. > > I think having a command to list the bad blocks would be useful. This already exists (nand bad) Regards Joachim > -- Joachim Jaeger FS Forth-Systeme GmbH A DIGI International Company Kueferstrasse 8 79206 Breisach Germany Phone: +49-7667-908-0 Fax: +49-7667-908-200 mailto:joachim_jaeger at digi.com web: www.fsforth.de, www.digi.com