public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Sneha Narnakaje <nsnehaprabha@ti.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	Sandeep Paulraj <s-paulraj@ti.com>
Subject: Re: [PATCH] MTD-NAND: Changes to read_page APIs to support NAND_ECC_HW_SYNDROME mode on TI DaVinci DM355
Date: Tue, 7 Apr 2009 01:07:44 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0904070102260.21577@localhost.localdomain> (raw)
In-Reply-To: <1238601784-9563-1-git-send-email-nsnehaprabha@ti.com>

Sneha,

On Wed, 1 Apr 2009, nsnehaprabha@ti.com wrote:

Would you please care to CC the still caring but admittedly lazy and
distracted maintainer on such patches ?

> From: Sneha Narnakaje <nsnehaprabha@ti.com>
> 
> The NAND controller on TI DaVinci DM355 supports NAND devices with large page size (2K and 4K), but the HW ECC is handled for every 512byte read/write chunks. The current HW_SYNDROME read_page/write_page APIs in the NAND core (nand_base) use the "infix OOB" scheme. The core APIs overwrite NAND manufacturer's bad block meta data, thus complicating the jobs of non-Linux NAND programmers (end equipment manufacturering). These APIs also imply ECC protection for the prepad bytes, causing nand raw_write operations to fail.

Please use proper line breaks. 523 characters do not fit into a
terminal.

Thanks,

	tglx

  parent reply	other threads:[~2009-04-06 23:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 16:03 [PATCH] MTD-NAND: Changes to read_page APIs to support NAND_ECC_HW_SYNDROME mode on TI DaVinci DM355 nsnehaprabha
2009-04-05 22:56 ` David Brownell
2009-04-06 22:59   ` Thomas Gleixner
2009-04-07  1:49     ` David Brownell
2009-04-07 16:02       ` Narnakaje, Snehaprabha
2009-04-07 16:45         ` Thomas Gleixner
2009-04-07 18:34           ` Narnakaje, Snehaprabha
2009-04-07 19:48             ` Thomas Gleixner
2009-04-07 23:08               ` David Brownell
2009-04-09 13:41               ` Narnakaje, Snehaprabha
2009-04-07 22:46             ` David Brownell
2009-04-14 17:36               ` David Brownell
2009-04-07 22:44         ` David Brownell
2009-04-06 23:07 ` Thomas Gleixner [this message]
2009-04-07 15:07   ` Narnakaje, Snehaprabha
  -- strict thread matches above, loose matches on Subject: below --
2009-04-01 16:32 nsnehaprabha

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=alpine.LFD.2.00.0904070102260.21577@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nsnehaprabha@ti.com \
    --cc=s-paulraj@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