Comment 3 for bug 907447

I don't have the gear to test Vexpress, and I've never played with boot monitor myself; I would like Linaro Image Tools to support larger / FAT32 Android images, but it's important not to regress a boot monitor based installation (I believe it's the only working one at the moment?).

So what I would propose is that you try testing Vexpress + boot monitor with FAT32 partitions, and if that works we just switch from FAT16 to FAT32 in the board config and hwpacks.

If that doesn't work, we introduce separate boarconfigs or hwpacks for Vexpress and VexpressFat32 or something like that; a better name than VexpressFat32 would be ideal of course.

The proposed branch does NOT seem ok to me because it forces FAT32 for all boards and hwpacks rather than changing Vexpress from FAT16 to FAT32. If FAT16 isn't needed anymore anywhere, then we should remove all mentions of FAT16 vs. FAT32 from the code rather than just this one.