From: Vladimir Barinov <vbarinov@embeddedalley.com>
To: Holger Schurig <h.schurig@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 14:29:06 +0400 [thread overview]
Message-ID: <49F97D72.8030109@embeddedalley.com> (raw)
In-Reply-To: <200904291252.15650.h.schurig@mn-solutions.de>
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.
Holger Schurig wrote:
> Hmm, in u-boot v2, drivers/nand/nand_imx.c, I read:
>
>
> /*
> * MX21 Hardware contains a bug which causes HW ECC to fail for two
> * consecutive read pages containing 1bit Errors (See MX21 Chip Erata,
> * Erratum 16). Use software ECC for this chip.
> */
>
> BTW, in my version of MC9328MX21CE.pdf it's number 18.
>
>
> Do you know if all I need on i.MX21 is then
>
> static struct mxc_nand_platform_data nand_board_info = {
> .width = 1,
> .hw_ecc = 0, /* Broken hardware */
> };
>
Great, so the current mxc_nand driver can support your imx21 cpu through
platform data.
Regarding to me then I use mx27 cpu and it's errata taken from FSL site
says nothing about HW ECC:
http://www.freescale.com/files/32bit/doc/errata/MCIMX27CE.pdf?fsrch=1
nor in addendum:
http://www.freescale.com/files/dsp/doc/ref_manual/MCIMX27RMAD.pdf?fsrch=1
I can successfully flash jffs2 image to NAND flash, mount and read the
context.
Ditto I can do with ubifs. All this with hw_ecc = 1.
Regards,
Vladimir
next prev parent reply other threads:[~2009-04-30 10:29 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 [this message]
2009-04-30 11:09 ` Holger Schurig
2009-04-30 11:42 ` Vladimir Barinov
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=49F97D72.8030109@embeddedalley.com \
--to=vbarinov@embeddedalley.com \
--cc=LW@karo-electronics.de \
--cc=dwmw2@infradead.org \
--cc=h.schurig@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.