Steven Zedeck wrote:
> Scott Wood-2 wrote:
>> On Fri, Feb 12, 2010 at 06:14:51PM -0800, Steven Zedeck wrote:
>>> int board_nand_init(struct nand_chip *nand)
>>> {
>>> nand->ecc.mode = NAND_ECC_SOFT;
>>> #ifdef CFG_NAND_DBW_16
>>> nand->options = NAND_BUSWIDTH_16;
>>> #endif
>>> nand->cm
Scott Wood-2 wrote:
>
> On Fri, Feb 12, 2010 at 06:14:51PM -0800, Steven Zedeck wrote:
>> Its in board/atmel/at91sam9rlek/nand.c
>>
>> It doesn't do much but set up the various GPIO connections. Here's the
>> function:
>>
>> int board_nand_init(struct nand_chip *nand)
>> {
>> nand->ecc.m
On Fri, Feb 12, 2010 at 06:14:51PM -0800, Steven Zedeck wrote:
> Its in board/atmel/at91sam9rlek/nand.c
>
> It doesn't do much but set up the various GPIO connections. Here's the
> function:
>
> int board_nand_init(struct nand_chip *nand)
> {
> nand->ecc.mode = NAND_ECC_SOFT;
> #ifdef CFG_N
Scott Wood-2 wrote:
>
> Steven Zedeck wrote:
>>
>>
>> Steven Zedeck wrote:
>>>
No, I mean in the NAND driver for your specific hardware
(fsl_elbc_nand.c, mxc_nand.c, ndfc_nand.c, etc).
>>> You have been so helpful. I looked at the mtd/nand/Makefile and the only
>>> file that's incl
Steven Zedeck wrote:
>
>
> Steven Zedeck wrote:
>>
>>> No, I mean in the NAND driver for your specific hardware
>>> (fsl_elbc_nand.c, mxc_nand.c, ndfc_nand.c, etc).
>> You have been so helpful. I looked at the mtd/nand/Makefile and the only
>> file that's included besides the nand* files is:
>>
Steven Zedeck wrote:
>
>
>> No, I mean in the NAND driver for your specific hardware
>> (fsl_elbc_nand.c, mxc_nand.c, ndfc_nand.c, etc).
>
> You have been so helpful. I looked at the mtd/nand/Makefile and the only
> file that's included besides the nand* files is:
>
> COBJS-y += fsl_upm.o
>
> No, I mean in the NAND driver for your specific hardware
> (fsl_elbc_nand.c, mxc_nand.c, ndfc_nand.c, etc).
You have been so helpful. I looked at the mtd/nand/Makefile and the only
file that's included besides the nand* files is:
COBJS-y += fsl_upm.o
However, in that code:
#if defined(CONFI
Steven Zedeck wrote:
> First of all, I inherited much of this code, especially the NAND-related
> stuff. I've never needed to go into this portion of the code.
>
> It seems we are using the mtd driver as all our files dealing with nand are
> in drivers/mtd/nand. The only place I see NAND_USE_FLASH
>> U-Boot supports creating a bad block table in flash, and has done so since
>> before 2008.10 (assuming you're not using legacy NAND). Whether it does
>> this depends on whether the NAND driver requests it with NAND_BBT_CREATE
>> in
>> nand_bbt_descr.options and NAND_USE_FLASH_BBT in nand_chip.
Steven Zedeck wrote:
>> U-Boot supports creating a bad block table in flash, and has done so since
>> before 2008.10 (assuming you're not using legacy NAND). Whether it does
>> this depends on whether the NAND driver requests it with NAND_BBT_CREATE
>> in
>> nand_bbt_descr.options and NAND_USE_FLA
>
> Hi,
> I know this message is about 18 months old. I am using Uboot 2008.10,
> which
> seems to not include support for creating the Nand BBT (bad block table).
> Was this patch released and if so when? Forgive me as I don't know how to
> find out.
>
> How best to add BBT support to Uboot? I
On Thu, Feb 11, 2010 at 06:49:33PM -0800, Steven Zedeck wrote:
>
> Hi,
> I know this message is about 18 months old. I am using Uboot 2008.10, which
> seems to not include support for creating the Nand BBT (bad block table).
> Was this patch released and if so when? Forgive me as I don't know how
Hi,
I know this message is about 18 months old. I am using Uboot 2008.10, which
seems to not include support for creating the Nand BBT (bad block table).
Was this patch released and if so when? Forgive me as I don't know how to
find out.
How best to add BBT support to Uboot? I need to have a BBT
13 matches
Mail list logo
