From: Artem Bityutskiy <dedekind1@gmail.com>
To: Hong Xu <hong.xu@atmel.com>
Cc: linux-mtd@lists.infradead.org, David.Woodhouse@intel.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] MTD: atmel_nand: Update Kconfig to support PMECC
Date: Mon, 12 Dec 2011 22:58:19 +0200 [thread overview]
Message-ID: <1323723514.2297.8.camel@koala> (raw)
In-Reply-To: <1323327219-17895-1-git-send-email-hong.xu@atmel.com>
On Thu, 2011-12-08 at 14:53 +0800, Hong Xu wrote:
> +config MTD_NAND_ATMEL_PMECC_HW
> + bool "Programmable Hardware ECC (BCH code)"
> + depends on ARCH_AT91SAM9X5 || ARCH_AT91SAM9N12
> + help
> + Use Programmable Hardware ECC (PMECC) controller.
> +
> + The PMECC Controller is a programmable binary BCH (Bose, Chaudhuri
> + and Hocquenghem) encoder/decoder. This controller can be used to
> + generate redundancy information for both SLC and MLC NAND Flash
> + devices.
> +
> + NB : hardware and software ECC schemes are incompatible.
> + If you switch from one to another, you'll have to erase your
> + mtd partition.
Does it have to be a config option, can we avoid adding config options
uless we really have to?
WARNING: multiple messages have this Message-ID (diff)
From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] MTD: atmel_nand: Update Kconfig to support PMECC
Date: Mon, 12 Dec 2011 22:58:19 +0200 [thread overview]
Message-ID: <1323723514.2297.8.camel@koala> (raw)
In-Reply-To: <1323327219-17895-1-git-send-email-hong.xu@atmel.com>
On Thu, 2011-12-08 at 14:53 +0800, Hong Xu wrote:
> +config MTD_NAND_ATMEL_PMECC_HW
> + bool "Programmable Hardware ECC (BCH code)"
> + depends on ARCH_AT91SAM9X5 || ARCH_AT91SAM9N12
> + help
> + Use Programmable Hardware ECC (PMECC) controller.
> +
> + The PMECC Controller is a programmable binary BCH (Bose, Chaudhuri
> + and Hocquenghem) encoder/decoder. This controller can be used to
> + generate redundancy information for both SLC and MLC NAND Flash
> + devices.
> +
> + NB : hardware and software ECC schemes are incompatible.
> + If you switch from one to another, you'll have to erase your
> + mtd partition.
Does it have to be a config option, can we avoid adding config options
uless we really have to?
next prev parent reply other threads:[~2011-12-12 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 6:53 [PATCH 1/2] MTD: atmel_nand: Update Kconfig to support PMECC Hong Xu
2011-12-08 6:53 ` Hong Xu
2011-12-08 6:53 ` [PATCH 2/2] MTD: atmel_nand: Update driver code to support Programmable HW ECC controller Hong Xu
2011-12-08 6:53 ` Hong Xu
2011-12-12 20:58 ` Artem Bityutskiy [this message]
2011-12-12 20:58 ` [PATCH 1/2] MTD: atmel_nand: Update Kconfig to support PMECC Artem Bityutskiy
2011-12-13 1:14 ` Hong Xu
2011-12-13 1:14 ` Hong Xu
2011-12-13 1:58 ` Hong Xu
2011-12-13 1:58 ` Hong Xu
2011-12-17 15:33 ` Artem Bityutskiy
2011-12-17 15:33 ` Artem Bityutskiy
2011-12-19 1:58 ` Hong Xu
2011-12-19 1:58 ` Hong Xu
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=1323723514.2297.8.camel@koala \
--to=dedekind1@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=hong.xu@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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.