UBI partitioning in embedded device?

[Ricard Wanderlof]

Are there any opinions here on the partitioning of a flash memory in an 
embedded device when using UBI?

Principially, one could let UBI manage the whole flash as one mtd 
partition, except possibly some boot area due to restriction in the boot 
ROM of the system in question. But is it wise to do so, assuming for 
instance there is data in part of the flash that you really want to avoid 
loosing, such as calibration data? Of course, theoretically, once the 
kernel has access to one part of the flash it could clobber anything, 
still, the mtd code has been proven for years whereas UBI is relatively 
young, so one idea would be to partition that flash into several mtd 
partitions (e.g. boot, running system, and calibration data), and let UBI 
handle these separately. That could minimize the risk of UBI clobbering 
the calibration data when operating on the running system, for instance.

Any thoughts?

/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