summaryrefslogtreecommitdiffstats
path: root/bitbake
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:20 +0000
commit1cabda965d0ec7c76f2fe57ce751154b9fc5e500 (patch)
tree7fb315646ad2d2084c636ab81b9550a4736b2b24 /bitbake
parent19247e44a388a58ea03cc91decb8b18e022efd52 (diff)
downloadast2050-yocto-poky-1cabda965d0ec7c76f2fe57ce751154b9fc5e500.zip
ast2050-yocto-poky-1cabda965d0ec7c76f2fe57ce751154b9fc5e500.tar.gz
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. (From OE-Core rev: 68aa18609c10a3ae2f738930c933fa2a95ce8959) Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud