On Mon, Mar 14, 2011 at 12:05 PM, Paul Larson <paul.larson@linaro.org> wrote:

1. with the current way we do things, we typically either do:
mmcblk0p1 - boot (for master image)
mmcblk0p2 - root (for master imge)
then either p3, p4 for testboot, testrootfs, or an extended partition, with 2 or more logical partitions labeled testboot, testrootfs.
We could adjust this slightly and do:
mmcblk0p1 - boot
mmcblk0p2 - root
mmcblk0p3 - androidsystem
mmcblk0p4 [extended]
  mmcblk0p5 - androidcache
  mmcblk0p6 - androiddata
  mmcblk0p7 - androidsdcard / testrootfs (this could be the bulk of remaining space used by both, depending on which image type we are booting)
  mmcblk0p8 - testboot

We would need to try it, but it might make a good solution for the short term.
I see one thing that could cause a problem here.  I tried actually creating an SD card with this partitioning scheme and it seems to choke on the last partition.  Looking at the mmc block driver, it seems the default value for MMC_BLOCK_MINORS is 8, so we only see the first 7 (one is for the whole disk) partitions under /dev.  Even if we change this default in the kernel, I'm not sure if uboot would still have a problem with it or not.

Thanks,
Paul Larson