From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: [RFC] S3C24xx: Fixing the NAND handling
Date: Sat, 12 Mar 2011 20:37:12 +0100 [thread overview]
Message-ID: <201103122037.13163.jbe@pengutronix.de> (raw)
In-Reply-To: <201103071424.14270.jbe@pengutronix.de>
Hi,
sorry for the noise, but:
Juergen Beisert wrote:
> The NAND support for the S3C24xx CPU seems totally broken in the current
> kernel:
No, it isn't.
> - the driver's local OOB layout for small page NANDs overwrites the
> vendors bad block marker (a really bad idea!)
It does not. I mixed it up with large page NANDs. :-(
> - the ECC setup for large page NANDs violates NANDs partial write count
> (it forces 8 partial writes instead of allowed 4 per 2048 byte page)
It does not. The MTD framework writes the data in 8 pieces in this case. But
from the NANDs point of view it is a single write only.
So, no need to fix anything in the kernel. Maybe only in my brain....
jbe
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-03-12 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 13:24 Juergen Beisert
2011-03-08 2:08 ` Zoltán Kócsi
2011-03-08 2:44 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-12 19:37 ` Juergen Beisert [this message]
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=201103122037.13163.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=barebox@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