public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cmd_nand: add biterror insertion command for NAND Flash
Date: Thu, 5 Jan 2012 13:11:47 -0600	[thread overview]
Message-ID: <4F05F5F3.4010507@freescale.com> (raw)
In-Reply-To: <4F056660.3060700@keymile.com>

On 01/05/2012 02:59 AM, Holger Brunck wrote:
> Hi Scott,
> 
> On 01/04/2012 06:44 PM, Scott Wood wrote:
>> On 01/04/2012 09:32 AM, Holger Brunck wrote:
>>>
>>> Initial implementation for unsafe feature for biterror insertion on
>>> NAND-Flash devices. The code flips single bits in the data block of the
>>> flash to simulate single bit-errors.
>>> Tested with Samsung K9F1G08U0D and Micron MT29F1G08ABADAWP on
>>> km_kirkwood boards.
>>
>> Do we still need dedicated code for this now that we have the ability to
>> do raw writes?
>>
> 
> to be able to do raw writes was very usefull for me to reproduce a bug in the
> UBI layer in the past. Bitflips happen very rarely but they happen, and with
> this code you are able to force this and see how other SW layer handle this. Due
> to the fact there was an empty implementation in the u-boot code for this I
> thought it might be usefull for others too.

The biterr stub has been around since before we had raw writes.  If we
decide we don't need a separate biterr command, we should remove the stub.

Anything the biterr command does should be possible with raw writes, so
while having a dedicated command might be slightly more convenient, I
don't think it's worth the extra code size, review/fix iterations, and
maintenance.

Does anyone else have a strong opinion on the matter?

-Scott

      reply	other threads:[~2012-01-05 19:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 15:32 [U-Boot] [PATCH] cmd_nand: add biterror insertion command for NAND Flash Holger Brunck
2012-01-04 17:44 ` Scott Wood
2012-01-05  8:59   ` Holger Brunck
2012-01-05 19:11     ` Scott Wood [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=4F05F5F3.4010507@freescale.com \
    --to=scottwood@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox