summaryrefslogtreecommitdiff
path: root/meta/classes/gnomebase.bbclass
diff options
context:
space:
mode:
authorDarren Hart <dvhart@linux.intel.com>2012-01-11 15:04:24 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-01-17 14:53:00 +0000
commit68aa18609c10a3ae2f738930c933fa2a95ce8959 (patch)
treec3eb5fcf231dd6acce3c25e9c1dcabf7e81086d9 /meta/classes/gnomebase.bbclass
parentcace9ddc0edd654877d968643960fa4343472b58 (diff)
downloadopenembedded-core-68aa18609c10a3ae2f738930c933fa2a95ce8959.tar.gz
openembedded-core-68aa18609c10a3ae2f738930c933fa2a95ce8959.tar.bz2
openembedded-core-68aa18609c10a3ae2f738930c933fa2a95ce8959.tar.xz
openembedded-core-68aa18609c10a3ae2f738930c933fa2a95ce8959.zip
bootimg: Account for FAT filesystem overhead in image size
Fixes [YOCTO #1852] The bootimg class wasn't accounting for non-trivial amount of space required by the directory entries and FATs for the FAT filesystem. This patch attempts to make an accurate prediction of FAT overhead and adjusts the image size accordingly. It assumes no more than 16 directory entries per directory (which fit in a single sector). It also assumes 8.3 filenames. With the ceiling functions rounding up to full sectors and tracks, these assumptions seem reasonable. In order to ensure the calculations are accurate, this patch forces the FAT size to 32, rather than allowing mkdosfs to automatically select 12, 16, or 32 depending on the image being built. Tested by setting BOOTIMG_EXTRA_SPACE=0 and building core-image-minimal and core-image-sato for fri2-noemgd from meta-intel. Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'meta/classes/gnomebase.bbclass')
0 files changed, 0 insertions, 0 deletions