Preferred way to configure MTD physical mapping and partitioning

[Guillaume Autran]

Hi Laurent,

There is also the "RedBoot" approach that let you create and store your partition table in a reserved sector of your flash.
You can enable your kernel to parse and create your MTD partitions according. After that, all you need to do is make your boot loader write the table in flash. Have a look at the file "linux/drivers/mtd/redboot.c". 

Guillaume.



-----Original Message-----
From: linuxppc-embedded-bounces+gautran=mrv.com at ozlabs.org on behalf of Laurent Pinchart
Sent: Mon 5/22/2006 6:32 AM
To: linuxppc-embedded at ozlabs.org
Subject: Preferred way to configure MTD physical mapping and partitioning
 
Hi everybody,

while browsing the kernel sources to find out how other boards configure MTD 
physical mapping and partitioning, I noticed that a couple of different 
approaches were possible:

- adding a board specific "driver" in drivers/mtd/maps and handle all mapping 
manually
- adding board specific MTD configuration in arch/ppc/platforms with calls to 
physmap_set_partitions() and physmap_configure()
- adding board specific MTD configuration in arch/ppc/platforms with a call to 
physmap_set_partitions(), and using the CONFIG_MTD_PHYSMAP option with 
physical mapping values provided in the kernel configuration.

Could anyone comment on the preferred approach ?

Best regards,

Laurent Pinchart
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded at ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060522/7e0270ba/attachment.htm