public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] "nand biterr" ... got an implementation?
Date: Thu, 18 Jun 2009 20:10:32 -0700	[thread overview]
Message-ID: <200906182010.32562.david-b@pacbell.net> (raw)
In-Reply-To: <20090422161922.GA9218@ld0162-tx32.am.freescale.net>

This is still in my mailbox, don't know that I'll get around to
it any time soon, but another requirement came to mind.


On Wednesday 22 April 2009, Scott Wood wrote:
> On Tue, Apr 21, 2009 at 07:38:27PM -0700, David Brownell wrote:
> > I was hoping that I could use that to test some NAND code, but
> > then I noticed it wasn't implemented.  I would have expected that
> > U-Boot command wouldn't exist until they're implemented...
> 
> Sorry about that. :-(
> 
> It probably existed in an older version of the NAND code, and never got
> reimplemented.
> 
> > I'm hoping someone has an implementation.  With at least these
> > characteristics:
> > 
> >  - Doesn't toggle the same bit each time
> >  - Repeating N times on a block introduces N distinct 1-bit errors

     - Needs to reflect ECC structure.  That is, when a 2K page is
       split into four distinct 512-byte ECC regions (plus OOB),
       it must be possible to force e.g. four errors in the second
       region while leaving the others alone.

> >  - Normally affects only the data area, not spare/OOB
> >      * although forcing bit errors in ECC would be valuable too
> >      * ditto the rest of the OOB ... though likely they'd be ignored
> 
> A general write-to-oob command would be nice as well.
> 
> -Scott
> 
> 

      reply	other threads:[~2009-06-19  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22  2:38 [U-Boot] "nand biterr" ... got an implementation? David Brownell
2009-04-22 16:19 ` Scott Wood
2009-06-19  3:10   ` David Brownell [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=200906182010.32562.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --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