From: "Zoltán Kócsi" <zoltan@bendor.com.au>
To: barebox@lists.infradead.org
Subject: Re: [RFC] S3C24xx: Fixing the NAND handling
Date: Tue, 8 Mar 2011 13:08:02 +1100 [thread overview]
Message-ID: <20110308130802.72018ed3@manocska.bendor.com.au> (raw)
In-Reply-To: <201103071424.14270.jbe@pengutronix.de>
On Mon, 7 Mar 2011 14:24:13 +0100
Juergen Beisert <jbe@pengutronix.de> wrote:
> - 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.
I believe that kernel has to be fixed. If it is broken and violates the
chip manufacturer's speifications, then you can't (or shouldn't) use it
on the field anyway. In that case you have to accept that upgrading the
kernel will mean that you also have to rewrite whatever code you have
which depends on the *incorrect* treatment of the hardware.
Prolonging the existence of mistreatment of hardware in the name of
backward compatibility is not a good thing, I believe.
Zoltan
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-03-08 2:08 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 [this message]
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=20110308130802.72018ed3@manocska.bendor.com.au \
--to=zoltan@bendor.com.au \
--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