From: Steven Hein <ssh@sgi.com>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: Aw: Re: Hardware ECC in NAND flash driver
Date: Mon, 12 Aug 2002 16:49:15 -0500 [thread overview]
Message-ID: <3D582D5B.A18054F@sgi.com> (raw)
In-Reply-To: 34a9835a72.35a7234a98@t-online.de
tglx@linutronix.de wrote:
> >
> > Dumb question--is ECC calculation "generic" enough to be
> > applicable from
> > one hardware ECC generator to the next, even if they do the same
> > numberof ECC bytes for the same block size? Is it very likely
> > that the
> > algorithm
> > is actually going to be the same between platforms?
> I think so, because Samsung and others will bring up similar chips,
> which
> incorporate the same ECC generator, but with maybe different registers
> or
> opcodes. But the algorithm will be the same for interdevice compability.
> So
> IMHO it's correct to put it in the generic nand_ecc code.
>
Sounds fine with me!
Any preference on how the correct_data function should be named
(the one I should add to nand_ecc.c)? Let me know what you'd prefer
and I'll use that name from the start.
> > THANKS for adding this!! I'll try it today/tomorrow.
> I'm curious, how many bugs you will detect. :)
>
The final tally is.......ZERO!! I tried it and it worked great.
Thanks again!
> > Another question--how do you typically handle adding new HW drivers
> > to the NAND flash code? I know that in my case, the HW implementation
> > uses access to specific S3C2410 processor registers, and those
> > register definitions live in include/asm-arm/arch-s3c2410 directory
> > in the Linux kernel tree. I would expect that these arch-specific
> > files would not live in the MTD tree. Let me know--I'd like to get
> > this HW driver incorporated into the standard tree as soon as I
> > get it working!
>
> That's easy, you include <asm/hardware.h> and you should be done. When
> your
> driver is ready, let me know. I will take care for incorporation.
>
I'll let you know when I have it done (I'm working with a Samsung
employee on the 2410 port; when we get it cleaned up I'll
send it to you).
Steve
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Hein (ssh@sgi.com) Engineering Diagnostics/Software
Silicon Graphics, Inc.
1168 Industrial Blvd. Phone: (715) 726-8410
Chippewa Falls, WI 54729 Fax: (715) 726-6715
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
prev parent reply other threads:[~2002-08-12 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 17:26 Aw: Re: Hardware ECC in NAND flash driver tglx
2002-08-12 21:49 ` Steven Hein [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=3D582D5B.A18054F@sgi.com \
--to=ssh@sgi.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.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.