From: Vladimir Barinov <vbarinov@embeddedalley.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-mtd@lists.infradead.org,
Sascha Hauer <s.hauer@pengutronix.de>,
dwmw2@infradead.org, linux-arm-kernel@lists.arm.linux.org.uk,
Lothar Wassmann <LW@karo-electronics.de>
Subject: Re: [PATCH] [MTD] MXC NAND driver fixes (v3)
Date: Thu, 30 Apr 2009 15:42:41 +0400 [thread overview]
Message-ID: <49F98EB1.10804@embeddedalley.com> (raw)
In-Reply-To: <200904301309.54859.hs4233@mail.mn-solutions.de>
Holger Schurig wrote:
>> Hello Holger,
>>
>> Could you explain how this message is related to this thread?
>> This patch as well as linux-mtd mail list doesn't care about
>> platform specific code that you can do in your custom mx21
>> based board.
>>
>
> The thread is about a NAND flash driver for Linux MTD. And this
> driver will work with i.MX27 and i.MX21 SoCs. However, the
> i.MX21 has a specific error in it's silicon, where the hardware
> ECC cannot one-bit-errors IF they are in two consecutive NAND
> blocks.
>
This thread is about minor fixes for MXC NAND driver :)
> If the NAND driver, that is supposed to be used for i.MX21,
> cannot handle this (e.g. using software ECC), then the NAND
> driver is buggy.
>
>
You have pointed to the way how to resolve the mx21 h/w bug via platform
data.
> This has nothing to do with board-specific things, my question
> was just if the board setup code can keep ".ecc = 0". Or if that
> won't work, we have to fix the MXC NAND driver with some
> cpu_is_mx21() code paths.
>
It's up to you to see if it work using .hw_ecc = 0. I have no mx21
hardware at all.
Regards,
Vladimir
next prev parent reply other threads:[~2009-04-30 11:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1238709260-17439-1-git-send-email-vbarinov@embeddedalley.com>
2009-04-03 5:38 ` [PATCH] [MTD] MXC NAND driver fixes Sascha Hauer
2009-04-03 8:21 ` Vladimir Barinov
[not found] ` <1238748195-10757-1-git-send-email-vbarinov@embeddedalley.com>
2009-04-04 11:37 ` [PATCH] [MTD] MXC NAND driver fixes (v2) Sascha Hauer
2009-04-06 9:11 ` Vladimir Barinov
[not found] ` <1239210502-822-1-git-send-email-vbarinov@embeddedalley.com>
2009-04-08 17:28 ` [PATCH] [MTD] MXC NAND driver fixes (v3) Sascha Hauer
2009-04-29 10:52 ` Holger Schurig
2009-04-30 10:29 ` Vladimir Barinov
2009-04-30 11:09 ` Holger Schurig
2009-04-30 11:42 ` Vladimir Barinov [this message]
2009-04-30 12:30 ` Holger Schurig
2009-04-29 11:12 ` Holger Schurig
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=49F98EB1.10804@embeddedalley.com \
--to=vbarinov@embeddedalley.com \
--cc=LW@karo-electronics.de \
--cc=dwmw2@infradead.org \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.