linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	linux-mtd@lists.infradead.org,
	"boris.brezillon@free-electrons.com >> Boris Brezillon"
	<boris.brezillon@free-electrons.com>,
	computersforpeace@gmail.com
Subject: Re: should nand driver create ECC for a page after ERASE cmd?
Date: Sun, 21 Dec 2014 15:13:25 +0100	[thread overview]
Message-ID: <5496D585.8070605@rempel-privat.de> (raw)
In-Reply-To: <54962684.9040003@vanguardiasur.com.ar>

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

Am 21.12.2014 um 02:46 schrieb Ezequiel Garcia:
> On 12/20/2014 05:42 AM, Oleksij Rempel wrote:
>> Hello all,
>>
>> i'm trying to pass mtd/tests for my driver.. on pagetest i fail on this
>> place:
>> http://lxr.free-electrons.com/source/drivers/mtd/tests/pagetest.c#L311
>>
>> after ERASE cmd this test trying to read same page. Driver will report
>> ECC error on read, because erased page has no ECC data in OOB.
>>
>> What is correct way to handle it?
>>
> [..]
> 
> This might help, although I'm not sure it's the best solution.
> 
> $ git grep is_buf_blank drivers/mtd/nand/pxa3xx_nand.c
> 

Thank you! It should be good starting point.


-- 
Regards,
Oleksij


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  reply	other threads:[~2014-12-21 14:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-20  8:42 should nand driver create ECC for a page after ERASE cmd? Oleksij Rempel
2014-12-21  1:46 ` Ezequiel Garcia
2014-12-21 14:13   ` Oleksij Rempel [this message]
2014-12-21 16:28 ` Boris Brezillon
2014-12-21 18:44   ` Oleksij Rempel
2014-12-22 18:41     ` Brian Norris
2014-12-22 19:50       ` Oleksij Rempel
2014-12-23 11:27         ` Boris Brezillon

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=5496D585.8070605@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=linux-mtd@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).