RE: [EXT] Re: [PATCH V1] mtd: core: Micron SLC NAND filling block

["Bean Huo (beanhuo)" <beanhuo@xxxxxxxxxx>]

Hi, Boris and Miquel
Thanks for your email.
Since the patch is based on v4.2 which doesn't separate specific NAND vendor
driver into vendor specific chip driver file. I will rebase my patch to latest linux kernel,
and implement  a specific hook funciton in the nand_micron.c as you suggested.
After testing well, you will see the version 2.

//Bean Huo

>> Boris,
>>
>> Are there  non UBI/UBIFS cases?
>> Can you please be specific?
>
>UBI is one user of MTD.
>
>What about direct accesses to MTD devices? Squashfs?
>
>In any case, I don't think it is exaggerated to say that Linux has been built on
>"layering". This issue is NAND chip specific, hence must be handled at the
>NAND core level. In the NAND erase path I would like to see a call to a vendor
>specific hook that:
>1/ checks if the part is affected by comparing its ID to a list, 2/ if yes, checks if
>the block must be filled before erasing.
>
>The logic of 1/ and 2/ should probably reside in
>drivers/mtd/nand/raw/nand_micron.c
>
>
>Thanks,
>Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/