From: David Brownell <david-b@pacbell.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot and CONFIG_SYS_DAVINCI_BROKEN_ECC
Date: Sun, 26 Apr 2009 11:11:48 -0700 [thread overview]
Message-ID: <200904261111.48584.david-b@pacbell.net> (raw)
I was looking at the DaVinci NAND support in current U-Boot
code (i.e. 2009.03 plus patches merged since that release),
and am puzzled by the above-named config option.
Before I submit a patch to remove it from U-Boot GIT (nothing
there enables it, and it will nastify 4-bit support), I thought
I'd see if anyone knows exactly what software it was trying to
emulate. Differences from the current NAND driver in GIT:
- Matches MVL 4.0 (2.6.10) and 5.0 (2.6.18) drivers in handling
NANDx1ECC registers: 0PQR0stu maps to PsQRtu, while the NAND
driver in mainline maps it to ~PQRstu.
- Custom ECC layouts, "not compatible with Linux or RBL/UBL".
- Does some very broken stuff for large page support.
The first of those I can understand; someone wrote some odd and
overly-complex ECC code way back, it worked and then got shipped.
(Although TI's U-Boot 1.2.0 uses soft ECC, instead...)
The other two look like they were experimental code that
should probably not have been merged anywhere...
- Dave
next reply other threads:[~2009-04-26 18:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 18:11 David Brownell [this message]
2009-04-26 22:40 ` [U-Boot] U-Boot and CONFIG_SYS_DAVINCI_BROKEN_ECC Jean-Christophe PLAGNIOL-VILLARD
2009-04-26 22:51 ` Wolfgang Denk
2009-04-26 22:57 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-26 23:56 ` David Brownell
2009-04-27 2:08 ` Hugo Villeneuve
2009-04-27 18:56 ` Scott Wood
2009-04-27 19:46 ` David Brownell
2009-04-27 20:11 ` Scott Wood
2009-04-27 21:16 ` David Brownell
2009-05-04 0:39 ` Stephen Irons
2009-05-04 2:44 ` David Brownell
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=200904261111.48584.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=u-boot@lists.denx.de \
/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.