[Yaffs-archive] Re: [yaffs] About NAND_YAFFS_OOB

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Edward J. Lee
Date:  
To: tglx, yaffs
Subject: [Yaffs-archive] Re: [yaffs] About NAND_YAFFS_OOB
Thomas Gleixner ? ?:

>On Saturday 08 March 2003 01:59, Edward J. Lee wrote:
>
>
>>Hi folks.
>>I'm still struggling with the compilation
>>(I used 'USE_OLD_MTD' till now, and because of the catastrophic speed
>> I guess I'll have to use a different method)
>>and I just can't manage to get over the NAND_YAFFS_OOB, NAND_NONE_OOB
>>problem.
>>
>>
>NAND_YAFFS_OOB, NAND_NONE_OOB is not longer supported in actual MTD code. We
>changed the rules for OOB-selection. The current YAFFS CVS code is aware of
>this changes.
>
>from yaffs_mtdif.c
>
>#ifndef    CONFIG_YAFFS_USE_OLD_MTD
>    if(data && spare)
>    {
>        if(dev->useNANDECC)
>        {
>                u8 tmpSpare[ YAFFS_BYTES_PER_SPARE + (2*sizeof(int)) ];
>            retval = 
>mtd->read_ecc(mtd,addr,dev->nBytesPerChunk,&dummy,data,tmpSpare,yaffs_oobinfo);

>

Hmm. I just got a new set of code from the CVS
(:pserver::/home/aleph1/cvs co yaffs)
, looked into yaffs_mtdif.c and couldn't find the string yaffs_oobinfo.
Strange. I'm Puzzled. Is there a different CVS running so that I
couldn't get the latest code?

>                memcpy(spareAsBytes, tmpSpare, YAFFS_BYTES_PER_SPARE);
>        }
>        else
>        {
>            retval = 
>mtd->read_ecc(mtd,addr,dev->nBytesPerChunk,&dummy,data,spareAsBytes,&yaffs_noeccinfo);
>        }
>    }
>    else
>    {
>#endif

>
>Use latest MTD-CVS code and latest YAFFS CVS code and you will be fine.
>
>
>




---------------------------------------------------------------------------------------
This mailing list is hosted by Toby Churchill open software (www.toby-churchill.org).
If mailing list membership is no longer wanted you can remove yourself from the list by
sending an email to with the text "unsubscribe"
(without the quotes) as the subject.