Charles Manning wrote:
> Hi Stanley
>
> I guess the other approach is to not modify nand_write but rather modify 
> mkyaffs2 and use that to write in the image.
>   

We usually run mkyaffs2 on the host PC, and it can't get the nand flash 
information
on the target board.

Stanley.

> -- Charles
>
>
> On Thursday 22 April 2010 15:15:38 stanley.miao wrote:
>   
>> Charles Manning wrote:
>>     
>>> We should put this in an FAQ...
>>>
>>> On Tuesday 20 April 2010 11:43:52 Guy Lancaster wrote:
>>>       
>>>> I built a file system image using mkyaffs2image v1.5 but but won't
>>>>         
>>> mkyaffsimage (the yaffs1 version) worked reasonably well because yaffs1
>>> tends/tended to be used with a single straight-forward flash format.
>>>
>>> With yaffs2, the actual binary layout is defered to the flash driver (mtd
>>> in the case of Linux). This varies from device to device.
>>>
>>> As a result, the current mkyaffs2image is really a bit of a mess and
>>> needs to be whittled and sandpapered to fit with your flash.
>>>       
>> Yes, The NAND oob layout varies from device to device, mkyaffs2image
>> can't know
>> the layout. So we should leave this job to nandwrite.
>>
>> This is the patch for it.
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2010-February/028923.html
>>
>>
>> Stanley.
>>
>>