public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 1/2] NAND: Add support for transparent hardware ECC.
Date: Thu, 24 May 2007 10:45:09 -0500	[thread overview]
Message-ID: <4655B305.9080904@freescale.com> (raw)
In-Reply-To: <200705241226.26158.sr@denx.de>

Stefan Roese wrote:
> I would like to know the status of this "tranparent" hardware ECC mechanism
> in the Linux source. I assume that you want to integrate this support there
> too, right? I couldn't find any reference to this in the current mtd/nand
> implementations and/or any reference to the MPC831x.

I have a Linux patch from Nick Spence for nand on the 831x, but it needs 
a lot of cleanup before I can submit it, which I haven't had a chance to 
do yet.  It currently uses a rather ugly hack to get around the lack of 
transparent ECC support (as did the u-boot patch before I reworked it).

> I'm asking, since the U-Boot nand code is based on the Linux mtd codebase,
> and we should try to keep features common between both source codes as
> often as possible.

Agreed, though when writing the u-boot patch I looked at the kernel 
source, and it appears to have already diverged quite a bit.  When I get 
a chance to look at the 831x NAND Linux patch, I'll most likely 
implement similar transparent ECC support there.

-Scott

      reply	other threads:[~2007-05-24 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 16:27 [U-Boot-Users] [PATCH 1/2] NAND: Add support for transparent hardware ECC Scott Wood
2007-05-24 10:26 ` Stefan Roese
2007-05-24 15:45   ` Scott Wood [this message]

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=4655B305.9080904@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