All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: alfred steele <alfred.jaquez@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mxc_nand: i.MX35 hardware ECC fixups
Date: Sun, 13 Dec 2009 15:00:10 +0100	[thread overview]
Message-ID: <4B24F36A.40108@eukrea.com> (raw)
In-Reply-To: <528f13590912121558h26a95a1awcc2f8f384e8c3076@mail.gmail.com>

Hi Alfred,

alfred steele a écrit :
> I am having a issue with using nandwrite mtd util and it so happens
> that the nandwrite gets stuck at a particular block and the sonsole
> hangs there forever.
> We are using the mx27(mxc) with a large size page NAND(4k). The annd
> write suceeds for the kernel MTD parition. I am suspecting my NAND
> driver is somehow obsolete. How do i find out as to what could be the
> root cause of the problem?
are you sure the i.MX27's NAND controler supports 4k NAND ?

 From the Reference Manual is only support 512 & 2k :
The NFC interfaces standard NAND Flash devices to the IC and hides the 
complexities of accessing the NAND Flash. It provides a glueless 
interface to both 8-bit and 16-bit NAND Flash parts with page sizes
of 512 bytes or 2 Kbytes, and densities up to 64 Gbits per 2-Kbyte page 
size NAND Flash, and 8 Gbits per 512 byte page size NAND Flash.

There is no mention of 4k NAND and the NFC's RAM buffer is only 2k + 64 
which may be not enough for 4k NAND (the v2 NFC has 4k + 512 and support 
4k).

Eric

  reply	other threads:[~2009-12-13 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 17:06 [PATCH] mxc_nand: i.MX35 hardware ECC fixups John Ogness
     [not found] ` <528f13590911071823sa26e1ane027d51d16357c79@mail.gmail.com>
     [not found]   ` <80y6mg5e34.fsf@merkur.tec.linutronix.de>
2009-12-12 23:58     ` alfred steele
2009-12-13 14:00       ` Eric Bénard [this message]
2009-12-13 14:36       ` John Ogness

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=4B24F36A.40108@eukrea.com \
    --to=eric@eukrea.com \
    --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 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.