Re: erase block < 8KiB

[angelo <angelo70@gmail.com>]

Hi Artem,
i already managed my issue, this flash and jffs2 works perfect with a 
64KB sector. There should be in the archive my patch posted.

CFI driver actually do an operation called "fixup". It detect this 
flash, and know that this flash has 2 sector sizes, 4KB and 64KB.
The fixup chose the 4KB as erasesize, so excluding the jffs2 usage.

The patch to mkfs.jffs2 tool to allow the usage of 4KB erasesize works, 
but is not safe.
If 4KB was not allowed, there was a reason.

So i also tried to use some other FS, like logfs or UBIFS. But i 
couldn't easily port all the tools needed since i am in a "Coldfire" 
architecture and using uClinux for coldfire.
So i decided to patch the erasesize to 64KB.

At the end, who is interested can use it, the patch is very simple and 
is available searching the archive.

Regards.
angelo





On 14/10/2011 11:15, Artem Bityutskiy wrote:
> On Fri, 2011-10-14 at 10:50 +0200, angelo wrote:
>    
>> I already done this, and posted the patch for 64 KB sector.
>>
>> But i none here still answered to the question :
>> why the cfi_cmdset_0002 selects for this flash the 4KB sector instead of
>> the 64KB  ? In this way, the non-working of jffs2 is guaranteed, since
>> the minimal block size is 4K + some bytes.
>>      
> I do not know CFI, sorry, but you probably should do this on a higher
> level than CFI, something between JFFS2 and MTD.
>
>