From: Juergen Beisert <jbe@pengutronix.de>
To: linux-mtd@lists.infradead.org
Subject: S3C24xx NFC: Bad oob layout and partial write count violation
Date: Tue, 8 Mar 2011 16:58:03 +0100 [thread overview]
Message-ID: <201103081658.03969.jbe@pengutronix.de> (raw)
Hi,
when I tried to get the NAND memory on my S3C2440 based mini2440 to work, I
noticed the NFC driver uses its own 'nand_ecclayout' for small page NANDs and
this layout may overwrites the bad block markers.
On the other hand this driver sets up the 'ecc.size' to 256 bytes for large
page NANDs which ends up with 8 partial writes into one 2048 byte page. This
violates the spec of at least my NAND device, which only allows 4 partial
writes per page.
Does anyone know why the setup is done in this way?
For both cases I see no hardware restriction. I think for small page NANDs the
generic OOB layout can be used, and for large page NANDs the 'ecc.size'
should be increased at least to 512 (to be compatible with the S3C2410) to
decrease the partial write count. But a change of these settings would break
existing installations. How to proceed in this case?
jbe
reply other threads:[~2011-03-08 16:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201103081658.03969.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