* Erase Block size
@ 2008-09-10 17:14 Sugathan, Rupesh
2008-09-11 7:41 ` Ricard Wanderlof
0 siblings, 1 reply; 4+ messages in thread
From: Sugathan, Rupesh @ 2008-09-10 17:14 UTC (permalink / raw)
To: linux-mtd
Hi,
I have a scenario where I need to deploy the same jffs2 image on two
flash memory parts, one with a 128KB sector size and the other with
256KB sector size.
I read from http://www.linux-mtd.infradead.org/doc/jffs2.html that
building the jffs2 image with smaller 'erase block size' should be
harmless even in the flash with 256KB sector size, although there might
be some warning messages at mount time. However, the warning messages
are not desired since this is a production image.
Can anyone tell me if there is any utility that can be used to alter the
erase block size on-the-fly? Or I would greatly appreciate if anyone has
some other solution to this problem.
Thanks
--
Rupesh
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Erase Block size
2008-09-10 17:14 Erase Block size Sugathan, Rupesh
@ 2008-09-11 7:41 ` Ricard Wanderlof
2008-09-11 8:09 ` michael
0 siblings, 1 reply; 4+ messages in thread
From: Ricard Wanderlof @ 2008-09-11 7:41 UTC (permalink / raw)
To: Sugathan, Rupesh; +Cc: linux-mtd@lists.infradead.org
On Wed, 10 Sep 2008, Sugathan, Rupesh wrote:
> I have a scenario where I need to deploy the same jffs2 image on two
> flash memory parts, one with a 128KB sector size and the other with
> 256KB sector size.
>
> I read from http://www.linux-mtd.infradead.org/doc/jffs2.html that
> building the jffs2 image with smaller 'erase block size' should be
> harmless even in the flash with 256KB sector size, although there might
> be some warning messages at mount time. However, the warning messages
> are not desired since this is a production image.
>
> Can anyone tell me if there is any utility that can be used to alter the
> erase block size on-the-fly? Or I would greatly appreciate if anyone has
> some other solution to this problem.
I'm not aware of any such utility.
You could always patch the kernel in your production image to avoid the
warnings.
We had a similar situation where we wanted to run the same image on
several NAND flash types with different block sizes. In the end we gave
up, because the issues with managing multiple block sizes, especially
regarding live firmware upgrades, made it not worth while. Instead, we
simply said that changing the flash so that the block/sector size changes
is considered a hardware change and must be handled accordingly (separate
firmware, etc).
/Ricard
--
Ricard Wolf Wanderlöf ricardw(at)axis.com
Axis Communications AB, Lund, Sweden www.axis.com
Phone +46 46 272 2016 Fax +46 46 13 61 30
"With Free Software you are employing the best programmers on the planet"
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Erase Block size
2008-09-11 7:41 ` Ricard Wanderlof
@ 2008-09-11 8:09 ` michael
0 siblings, 0 replies; 4+ messages in thread
From: michael @ 2008-09-11 8:09 UTC (permalink / raw)
To: Ricard Wanderlof; +Cc: linux-mtd@lists.infradead.org, Sugathan, Rupesh
Hi,
Ricard Wanderlof wrote:
> On Wed, 10 Sep 2008, Sugathan, Rupesh wrote:
>
>
>> I have a scenario where I need to deploy the same jffs2 image on two
>> flash memory parts, one with a 128KB sector size and the other with
>> 256KB sector size.
>>
>> I read from http://www.linux-mtd.infradead.org/doc/jffs2.html that
>> building the jffs2 image with smaller 'erase block size' should be
>> harmless even in the flash with 256KB sector size, although there might
>> be some warning messages at mount time. However, the warning messages
>> are not desired since this is a production image.
>>
>> Can anyone tell me if there is any utility that can be used to alter the
>> erase block size on-the-fly? Or I would greatly appreciate if anyone has
>> some other solution to this problem.
>>
You can use linux to flash image :). Erase the flash, mount it and
install file.
Regards Michael
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Erase Block size
[not found] <EE63F03D9E04774997AEBCD21FC77F253178CC@ccomm-ex1.ccomm.com>
@ 2008-09-15 9:14 ` Ricard Wanderlof
0 siblings, 0 replies; 4+ messages in thread
From: Ricard Wanderlof @ 2008-09-15 9:14 UTC (permalink / raw)
To: Sugathan, Rupesh; +Cc: linux-mtd@lists.infradead.org, Ricard Wanderlöf
On Thu, 11 Sep 2008, Sugathan, Rupesh wrote:
> Thanks for sharing your solution. Can you please comment if the below
> understanding correct.
> Cause of the warning messages are 'empty space' within the erase block.
> One of the problems of these empty spaces is a small waste of space in
> Flash. Is there any other problem in having these empty space on a
> write-able partition?
No, I don't think so.
/Ricard
--
Ricard Wolf Wanderlöf ricardw(at)axis.com
Axis Communications AB, Lund, Sweden www.axis.com
Phone +46 46 272 2016 Fax +46 46 13 61 30
"With Free Software you are employing the best programmers on the planet"
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-09-15 9:15 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-09-10 17:14 Erase Block size Sugathan, Rupesh
2008-09-11 7:41 ` Ricard Wanderlof
2008-09-11 8:09 ` michael
[not found] <EE63F03D9E04774997AEBCD21FC77F253178CC@ccomm-ex1.ccomm.com>
2008-09-15 9:14 ` Ricard Wanderlof
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox