summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/gdb
diff options
context:
space:
mode:
authorDarren Hart <dvhart@linux.intel.com>2012-01-31 08:41:13 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-02-01 15:11:39 +0000
commit634137704dd1a205e377a1131ef708f1c981f6b2 (patch)
treef6c1722c61822e4a887b3dfe6288d4d3d090d91c /meta/recipes-devtools/gdb
parent8330205eeb605354c139605618255940e3b312d4 (diff)
downloadopenembedded-core-634137704dd1a205e377a1131ef708f1c981f6b2.tar.gz
openembedded-core-634137704dd1a205e377a1131ef708f1c981f6b2.tar.bz2
openembedded-core-634137704dd1a205e377a1131ef708f1c981f6b2.tar.xz
openembedded-core-634137704dd1a205e377a1131ef708f1c981f6b2.zip
bootimg: Do not force FAT32 on all images, it violates the FAT specification
Fixes [YOCTO #1940] do_bootimg was performing the FAT overhead calculations assuming FAT32 and then forcing the use of FAT32 with "-F 32" to mkdosfs. The FAT specification is clear on cluster count being the determining factor for FAT size (even if the fs string is set to FAT32, go figure). Syslinux follows this spec, and rightly so, resulting in a failure on core-image-minimal: syslinux: zero FAT sectors (FAT12/16) Drop the "-F 32" from mkdosfs to allow it to select the appropriate FAT size based on cluster count. Leave the FAT overhead calculation in FAT32. This will result in a little extra padding for really small images, but not enough extra to justify recalculating for FAT12 and FAT16. Tested with a core-image-minimal build for atom-pc. do_bootimg completed successfully, and the resulting image was FAT16. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Diffstat (limited to 'meta/recipes-devtools/gdb')
0 files changed, 0 insertions, 0 deletions