From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd/gpmi : add BBT support
Date: Mon, 30 Jan 2012 18:32:35 +0800 [thread overview]
Message-ID: <4F2671C3.6000809@freescale.com> (raw)
In-Reply-To: <20120130094610.GA15596@pengutronix.de>
? 2012?01?30? 17:46, Wolfram Sang ??:
> On Mon, Jan 30, 2012 at 12:36:14PM +0800, Huang Shijie wrote:
>> add the BBT support to the gpmi nand driver.
>> Signed-off-by: Huang Shijie <b32955@freescale.com>
>> ---
>> drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
>> index 493ec2f..4fbb341 100644
>> --- a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
>> +++ b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
>> @@ -1493,6 +1493,7 @@ static int __devinit gpmi_nfc_init(struct gpmi_nand_data *this)
>> chip->ecc.mode = NAND_ECC_HW;
>> chip->ecc.size = 1;
>> chip->ecc.layout = &gpmi_hw_ecclayout;
>> + chip->bbt_options = NAND_BBT_USE_FLASH | NAND_BBT_NO_OOB;
> You are making this default. Is there a bootloader which supports that
> on MXS?
>
The bootloader usually is burned on /dev/mtd0, while the BBT is placed
at the end
of the NAND chip.
I tested the NAND boot mode too.
What's your concern?
Huang Shijie
next prev parent reply other threads:[~2012-01-30 10:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 4:36 [PATCH] mtd/gpmi : add BBT support Huang Shijie
2012-01-30 9:46 ` Wolfram Sang
2012-01-30 10:32 ` Huang Shijie [this message]
2012-01-30 10:44 ` Wolfram Sang
2012-01-30 11:29 ` Huang Shijie
2012-01-30 11:41 ` Wolfram Sang
2012-01-30 12:27 ` Marek Vasut
2012-01-30 13:12 ` Wolfram Sang
2012-01-30 13:30 ` Marek Vasut
2012-01-30 13:41 ` Wolfram Sang
2012-01-30 14:33 ` Marek Vasut
2012-01-31 8:47 ` Huang Shijie
2012-01-31 9:24 ` Wolfram Sang
2012-01-31 9:38 ` Huang Shijie
2012-01-31 11:37 ` Marek Vasut
2012-01-31 11:49 ` Wolfram Sang
2012-01-31 12:21 ` Marek Vasut
2012-01-30 12:24 ` Marek Vasut
2012-01-30 13:19 ` Wolfram Sang
2012-01-30 13:35 ` Marek Vasut
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=4F2671C3.6000809@freescale.com \
--to=b32955@freescale.com \
--cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).