From: Juergen Beisert <jbe@pengutronix.de>
To: linux-mtd@lists.infradead.org
Subject: Re: About the mxc nand driver
Date: Thu, 22 Oct 2009 12:26:06 +0200 [thread overview]
Message-ID: <200910221226.07328.jbe@pengutronix.de> (raw)
In-Reply-To: <200910211330.38141.gianlucarenzi@eptar.com>
On Mittwoch, 21. Oktober 2009, Gianluca Renzi wrote:
> On Tuesday 20 October 2009 15:11:58 Sascha Hauer wrote:
> > Hi all,
> >
> > I frequently get reports about bugs in the Freescale mxc nand driver.
> > Juergen Beisert and me invested some time to see what's going on in this
> > driver, so here are some results.
>
> The problem is caused by the fact the FreeScale's NAND Core Controller
> manages the 2K Largepage NAND as 4 SmallPage pages joined with their own
> ECC codes and badblock markers positions i.e. the smallpage badblock marker
> is located at 6th byte of the oobpage data (offset 5) (repeated for each
> page).
I can currently speak only about the i.MX35 NFC. But it handles larger pages
than 512 byte in the same way the i.MX27 NFC does. The tables in the
datasheet suggests they define a fixed location for the bad block marker in
the spare area and this will be repeated 4 times for a 2048 byte page. But it
seems the NFS does not touch any other byte than the ones defined for ECC
usage.
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | Phone: +49-8766-939 228 |
Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2009-10-22 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 13:11 About the mxc nand driver Sascha Hauer
2009-10-20 13:28 ` Juergen Beisert
2009-10-20 13:32 ` Sascha Hauer
2009-10-21 11:30 ` Gianluca Renzi
2009-10-22 10:26 ` Juergen Beisert [this message]
2009-10-22 21:17 ` alfred steele
2009-10-23 8:19 ` Juergen Beisert
[not found] <2132956280B09448AB947D9C8A291AC6011F88BE@SMFIDF806A.main.fr.ds.corp>
2009-10-20 17:08 ` Juergen Beisert
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=200910221226.07328.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--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