OK, regarding the mtdparts, I was thinking that maybe we should emulate the official Google dev phones which should help as we try to more closely stick to AOSP. If we get a bootloader that supports it, we should be able to use fastboot with this layout, and we may even be able to add CWM/ROM Manager support
mtdparts=msm_nand:
0x00480000@0x01000000(recovery) - (4,608 KB)
0x00300000@0x01480000(boot) - (3,072 KB)
0x09100000@0x01780000(system) - (148,480 KB)
0x05F00000@0x0A880000(cache) - (97,280 KB)
0x0F7E0000@0x10780000(userdata) - (253,824 KB)
0x000A0000@0x1FF60000(misc) - (640 KB)
The cache size may seem large, but that data is going to be cached somewhere, and it would ultimately end up in the userdata section anyway. We can conform to AOSP by having its own partition, and we should move the dalvik cache to that if it is being enabled. I think the more "best practices" we can use, the better performance we are going to get from our phone. Plus, roughly 250 MB of space for applications and such should be sufficient since we can just use app2sd.
For system, that should be more than enough space even if we were putting modules into the system. The latest Cyanogenmod systems are roughly 110 MB fully extracted. Not sure of the size of the sense builds, but I really think that should be plenty for the chefs.
I will be trying this partition layout tomorrow to make sure it works (don't see any reason it shouldn't). I'll also try changing /cache to mount on the cache partition and make sure that is working OK.