public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "vimal singh" <vimalsingh@ti.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	nsnehaprabha@ti.com, linux-mtd@lists.infradead.org,
	akpm@linux-foundation.org, dwmw2@infradead.org,
	tglx@linutronix.de
Subject: Re: [PATCH 2/2] NAND on DM355: Add 4-bit ECC support for large page NAND chips
Date: Thu, 7 May 2009 09:54:10 -0700	[thread overview]
Message-ID: <200905070954.10987.david-b@pacbell.net> (raw)
In-Reply-To: <41906.192.168.10.89.1241689856.squirrel@dbdmail.itg.ti.com>

On Thursday 07 May 2009, vimal singh wrote:
> >> How about leaving bytes '4' and '5' for bad block marker, to support 16-bit
> >> NAND parts too.
> >
> > This 4-bit ECC engine only works for 8-bit wide parts ...
> > or are you suggesting that in case TI re-engineers that
> > engine in the future?
>
> I am omap guy and was not aware of that. In omap HW BCH
> ECC (4- or 8- bit correction)can work both kind of memories.

I'm somewhat more of an OMAP guy too -- just got sucked in to
trying to get a dm355 board to run off NAND in mainline-bound
code, and you can see where that landed me!

Last I looked at the OMAP2/OMAP3 NAND controller driver, it
didn't yet support most fancy hardware features, like ECC
using more than one bit or the prefetch/postwrite logic. 

One nice feature of that OMAP2/OMAP3 controller, beyond the
support for 8 bit ECC, is that it buffers the ECC syndrome
data so that it doesn't need NAND_ECC_HW_OOB_FIRST logic to
prevent trashing the manufacturer OOB markers.  The limit
of max 4K pages seems like not a big worry for now.

- Dave

  reply	other threads:[~2009-05-07 16:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46149.192.168.10.89.1241686786.squirrel@dbdmail.itg.ti.com>
2009-05-07  9:50 ` [PATCH 2/2] NAND on DM355: Add 4-bit ECC support for large page NAND chips vimal singh
2009-05-07 16:54   ` David Brownell [this message]
     [not found] <43965.192.168.10.89.1241763647.squirrel@dbdmail.itg.ti.com>
2009-05-09  4:24 ` vimal singh
2009-05-07  8:59 vimal singh
2009-05-07  9:11 ` David Brownell
  -- strict thread matches above, loose matches on Subject: below --
2009-05-07  2:29 nsnehaprabha
2009-05-07  7:16 ` David Brownell
2009-05-07 14:13   ` Narnakaje, Snehaprabha
2009-05-07 17:11     ` David Brownell
2009-05-07 18:02       ` Narnakaje, Snehaprabha
2009-05-07 22:37       ` Troy Kisky
2009-05-08  0:03         ` Narnakaje, Snehaprabha

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=200905070954.10987.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@linux-foundation.org \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nsnehaprabha@ti.com \
    --cc=tglx@linutronix.de \
    --cc=vimalsingh@ti.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