All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
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 12:26:25 +0200	[thread overview]
Message-ID: <200705241226.26158.sr@denx.de> (raw)
In-Reply-To: <20070516162713.GA6786@ld0162-tx32.am.freescale.net>

Hi Scott,

sorry for the late response.

On Wednesday 16 May 2007, Scott Wood wrote:
> Some NAND controllers (such as on the MPC831x chips) have hardware ECC,
> but can only do it during a transfer (i.e. we can't implement
> calculate_ecc()).  When NAND_ECC_TRANSPARENT is used, then ECC errors on
> reads are reported through correct_data() (with no arguments other than
> the mtd device), and on writes through waitfunc()'s return value.

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'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.

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2007-05-24 10:26 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 [this message]
2007-05-24 15:45   ` Scott Wood

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=200705241226.26158.sr@denx.de \
    --to=sr@denx.de \
    --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.