The bootloader perspective.. The minimum set needed are for xloader, u-boot and the environment. xloader is very static. u-boot at 1.25m should be big enough environment is very static and should be big enough.. This is consistent with the bootloader. The rest can be done with mtdparts and the differences between ldp and zoom2 flash layout can be separated in their respective environment files. The bootloader flashing utility 'fastboot' depends on the kernel layout. There is a change pending to decouple using an mtdparts-like mechanism. See 'Runtime Partitions' toward the bottom of.. https://omapzoom.org/gf/project/omapzoom/wiki/?pagename=FAQ-8%3A+Zoom-II+Android%C2%A0fastboot Tom ________________________________________ From: Maxime Petazzoni [mpetazzoni@xxxxxxxxxx] Sent: Thursday, August 27, 2009 9:06 AM To: Pandita, Vikram Cc: Singh, Vimal; linux-omap@xxxxxxxxxxxxxxx; Rix, Tom Subject: Re: [PATCH] OMAP3: Zoom2: provide default MTD partitions Hi, * Pandita, Vikram <vikram.pandita@xxxxxx> [2009-08-27 19:16:27]: > Why? > > I know of an implementation by Vimal Singh that introduces a common > flash file for Zoom1 and Zoom2. > There is reuse of code there. Thanks for your comments. There are indeed other implentations around using a common flash file for Zoom1 and Zoom2 boards. I didn't know of this specific implementation by Vimal Singh, but we use something very similar internally. Since linux-omap didn't had any MTD partitions definitions for either boards, I decided to go for the smallest change: only partitions for Zoom2. > Please discuss and get a converged approach on handling NAND > partitions on Zoom1 and Zoom2. Agreed. We should use a common file for Zoom1 and Zoom2 flash, with Zoom2 specific partition sizes. But I'm not sure I deserve the right to propose Vimal Singh's patch (by the way, why hasn't it been merged in the linux-omap tree?). How should we proceed then? > Also the Systerm/User/Cache partition definitions are more from Android perspective. > > Given that each system may have a different NAND partition requirement, > have you looked at bootargs passing the MTD partition info: Eg: > > mtdparts=omap2-nand.0:512k@0(xloader),\ > 1536k@512k(bootloader),\ > 29m@2m(kernel),\ > 160m@32m(system),\ > 32m@192m(userdata),\ > 32m@224m(cache) Yes, I am aware of the mtdparts command line arguments, which works great. I think a "default", sensible partition layout for the Zoom2 would be nice though. - Maxime -- Maxime Petazzoni Linux kernel & software dev MontaVista Software, Inc -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
