public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: alfred steele <alfred.jaquez@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: About the mxc nand driver
Date: Fri, 23 Oct 2009 10:19:49 +0200	[thread overview]
Message-ID: <200910231019.49157.jbe@pengutronix.de> (raw)
In-Reply-To: <528f13590910221417i393958b6tc0d402e9e206ff51@mail.gmail.com>

On Donnerstag, 22. Oktober 2009, alfred steele wrote:
> > 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.
>
> So does the mxc_nand driver without "Saschas" latest patches work for
> NAND transactions on the mx35 nfc.

The current mainline mxc nand driver does not work on i.MX35. The i.MX35 NFC 
is of the next generation. We are on the way to merge the new features into 
this driver. 

> This probably suggests that the for 
> a 4K page size NAND, it would boil down to 8 cycles. Does that still
> hold true?

Yes, a 4 kiB page would generate 8 stripes of ECC data, 16 bytes each. 7 free, 
9 for ECC.

AFAIK i.MX35 (4 symbols ECC):

512 byte page:

* OOB offset: 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
*      Usage: |<----------------->|<----------------------->|
*                      User                   ECC

2048 byte page:

* OOB offset: 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
* OOB offset: 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
* OOB offset: 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
* OOB offset: 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
*      Usage: |<----------------->|<----------------------->|
*                       User                  ECC

4096 byte page:

* OOB offset: 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
* OOB offset: 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
*             .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
* OOB offset: 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F
* OOB offset: 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F
*      Usage: |<----------------->|<----------------------->|
*                       User                  ECC

But recent 4 kiB NANDs also provide 218 bytes of OOB. In this case this NFS 
also supports 18 byte of ECC. But currently I'm not sure about its layout.

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/  |

  reply	other threads:[~2009-10-23  8:20 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
2009-10-22 21:17     ` alfred steele
2009-10-23  8:19       ` Juergen Beisert [this message]
     [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=200910231019.49157.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=alfred.jaquez@gmail.com \
    --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