From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [RFC] S3C24xx: Fixing the NAND handling
Date: Mon, 7 Mar 2011 14:24:13 +0100 [thread overview]
Message-ID: <201103071424.14270.jbe@pengutronix.de> (raw)
Hi,
anyone here with an idea how to fix this:
The NAND support for the S3C24xx CPU seems totally broken in the current
kernel:
- the driver's local OOB layout for small page NANDs overwrites the vendors
bad block marker (a really bad idea!)
- 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)
How to adapt barebox according to the kernel? If we do OOB and ECC setup
correctly in barebox, the mainline kernel cannot work with this data. If we
do it in the same way than the kernel, we lose the bad block markers or do
more writes than the manufacturer allows for reliable data security.
Changing the kernel is also hard to do, because it breaks existing software
installations which should just run with more recent kernels.
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/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2011-03-07 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 13:24 Juergen Beisert [this message]
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
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=201103071424.14270.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