From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Broken ecc.size when switching between sw and hw ecc (beagleboard)
Date: Thu, 1 Mar 2012 11:32:33 -0600 [thread overview]
Message-ID: <4F4FB2B1.9040705@freescale.com> (raw)
In-Reply-To: <4F4F3E95.1060102@flatfrog.com>
On 03/01/2012 03:17 AM, Orjan Friberg wrote:
> On 02/29/2012 10:00 PM, Scott Wood wrote:
>> ECC mode is normally not something that you want to be runtime
>> switchable, as changing it usually changes the on-flash format. It also
>> requires driver cooperation -- the actual implementation (as opposed to
>> the command-line wrapper) is in drivers/mtd/nand/omap_gpmc.c.
>
> Are you saying that it shouldn't be switchable through a command line
> option (but rather based on information in the partition table or
> something similar), or are you saying that we shouldn't need different
> ECC modes for different parts of the flash (boot ROM vs. software
> implementations, whether block 0 has different ECC requirement etc)?
I'm saying that right now it's an OMAP-specific requirement and the
implementation of necessity involves the OMAP driver. If another driver
grows this as a requirement, we can consider refactoring so the command
line frontend is common.
Different ECC modes for different parts of the flash is unfortunate, but
sometimes mandated by circumstance. The NAND subsystem isn't really set
up to handle this, though changing it temporally is a hackish substitute.
-Scott
next prev parent reply other threads:[~2012-03-01 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 12:12 [U-Boot] Broken ecc.size when switching between sw and hw ecc (beagleboard) Orjan Friberg
2012-02-29 21:00 ` Scott Wood
2012-03-01 9:17 ` Orjan Friberg
2012-03-01 17:32 ` Scott Wood [this message]
2012-03-02 8:39 ` Orjan Friberg
2012-03-05 18:58 ` Tom Rini
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=4F4FB2B1.9040705@freescale.com \
--to=scottwood@freescale.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox