From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Hein <ssh@sgi.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Hardware ECC in NAND flash driver
Date: Wed, 07 Aug 2002 15:15:38 +0200 [thread overview]
Message-ID: <1028726139.19447.255.camel@thomas.tec.linutronix.de> (raw)
In-Reply-To: <3D511B55.6ADABE4D@sgi.com>
On Wed, 2002-08-07 at 15:06, Steven Hein wrote:
> Hello,
>
> I'm working on the Linux port to the Samsung S3C2410 PDA controller
> (ARM 920T core with many interfaces, including a NAND flash controller,
> built-in). The 2410's NAND flash controller generates ECC codes
> (3 bytes ECC per each 512 bytes data). Are there any plans to
> incorporate hardware ECC support into this driver? Specifically,
> I guess that would mean adding "hooks" so the hardware-specific
> driver could handle the ECC parts (I only had to make
> a few small changes to nand.c to get this working for the 2410.)
> If there's an effort underway in this area, I'd be happy to
> participate in the development.
>
We thougt about that already, but nobody made an attempt to do so,
because we had no hardware supporting this.
I was thinking about a similar hook as it is used for command function
and dev_ready function. So the hardware ecc support would be located in
the corresponding hardware driver.
If you send me a diff against current CVS, we can find a clean way
together to incorporate it into nand.c
--
Thomas
____________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2002-08-07 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 13:06 Hardware ECC in NAND flash driver Steven Hein
2002-08-07 13:15 ` Thomas Gleixner [this message]
2002-08-07 13:28 ` David Woodhouse
2002-08-07 13:39 ` Thomas Gleixner
[not found] ` <3D527739.5B19816C@sgi.com>
2002-08-10 10:33 ` Thomas Gleixner
2002-08-10 23:05 ` Thomas Gleixner
2002-08-12 16:10 ` Steven Hein
2002-08-12 16:00 ` Steven Hein
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=1028726139.19447.255.camel@thomas.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=ssh@sgi.com \
/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