On Wed, Dec 21, 2011, Tixy (Jon Medhurst) wrote:
> On larger cards, creating Android images for vexpress fails because the
> sdcard partition will be >2GB and an attempt is made to format this as
> FAT16. This is because VexpressConfig() specifies fat_size = 16, so the
> boot partition is understandable by ARMs boot monitor.
>
> I propose to fix this by making setup_android_partitions() always use
> FAT32 for the sdcard partition. (The option for boards to specify
> fat_size only seems to exist for those with restrictions in boot
> partition format. I don't think it makes sense to also use this for the
> sdcard partition.)
FAT16 on Vexpress was suggested for compatibility with the boot
monitor; if it supports FAT32, then that would be ideal.
On Wed, Dec 21, 2011, Tixy (Jon Medhurst) wrote: partitions( ) always use
> On larger cards, creating Android images for vexpress fails because the
> sdcard partition will be >2GB and an attempt is made to format this as
> FAT16. This is because VexpressConfig() specifies fat_size = 16, so the
> boot partition is understandable by ARMs boot monitor.
>
> I propose to fix this by making setup_android_
> FAT32 for the sdcard partition. (The option for boards to specify
> fat_size only seems to exist for those with restrictions in boot
> partition format. I don't think it makes sense to also use this for the
> sdcard partition.)
FAT16 on Vexpress was suggested for compatibility with the boot
monitor; if it supports FAT32, then that would be ideal.
--
Loïc Minier