AW: how to change size of MTD partitions at runtime

[Kuefmann Andreas ICM CP RD SD 1]

Hi Stephan,

thanks for your proposal. Unfortunately we have a very limited flash, so we
can't afford an additional partition for sw update purpose as you suggested.

If it should happen that future kernel/rootfs images would exceed the current
mtd partition sizes we'd have to shrink another mtd partition (user data)
accordingly in order to regain the missing space.

I don't think I'd have to re-mount/re-sync after the update, since it's OK
to reboot the machine after the update has completed.

regards,
- Andy

-----Ursprüngliche Nachricht-----
Von: Stephan Linke [mailto:Stephan.Linke at epygi.de] 
Gesendet: Donnerstag, 2. September 2004 15:20
An: Kuefmann Andreas ICM CP RD SD 1; linux-mtd at lists.infradead.org
Betreff: RE: how to change size of MTD partitions at runtime


Hi Andreas,

for the same purpose I am using an additional partition that covers the range of kernel and rootfs to update both of them at the same time. Ofcourse in this case after writing the images the device has to be rebooted. How do you handle remounting the rootfs and synchronization with current systems configuration so you don't have to reboot?

Regards, Stephan

> -----Original Message-----
> From: linux-mtd-bounces at lists.infradead.org
> [mailto:linux-mtd-bounces at lists.infradead.org]On Behalf Of Kuefmann 
> Andreas ICM CP RD SD 1
> Sent: Mittwoch, 1. September 2004 13:42
> To: 'linux-mtd at lists.infradead.org'
> Subject: how to change size of MTD partitions at runtime
>
>
> Hi all,
>
> I'm searching for a solution to dynamically change the size of MTD 
> partitions at runtime.
>
> This functionality is required for a flash update of kernel and/or 
> rootfs in the special case that the new kernel/rootfs is larger than 
> the old one. (in an embedded environment)
>
> 1.)
> there is no problem in erasing the flash, e.g eraseall /dev/mtd?, 
> (acting from a chrooted environment)
>
> 2.)
> However, reprogramming the flash with a larger image (now exceeding 
> the limits of the previous partition) isn't as easy as a cp 
> newimage.img /dev/mtd?.
>
> The MTD layer will still rely on the (old) partition sizes that were 
> valid during system startup. (taken over from a U-BOOT environment)
>
> My plans are as follows:
> - erase the flash partitions
> - adapt the u-boot environment to reflect the new mtd partition sizes
> - force the MTD subsystem to "re-read" the partition table in u-boot's
>   environment.
> - cp the new images to /dev/mtd? (which now reflect the changed
>   partition sizes)
>
> My question now is:
> - How can I manage to force a re-read of the partition table?
>
> Or can you think of another solution to change MTD partitions at 
> runtime?
>
> Thank you,
> regards,
> - Andy
>
> ______________________________________________________
> Linux MTD discussion mailing list 
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>