summaryrefslogtreecommitdiff
path: root/meta/classes/boot-directdisk.bbclass
diff options
context:
space:
mode:
authorJason Wessel <jason.wessel@windriver.com>2013-09-27 01:01:20 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-09-30 22:02:40 +0100
commit254899824900f2e8c6a34d2ad1b8cbea91acb4ae (patch)
treef3a2e50b6d0b61e93fbf4b77b3157a9656e37121 /meta/classes/boot-directdisk.bbclass
parent36faac868e086e9c23537b107cdd973d7fd980bd (diff)
downloadopenembedded-core-254899824900f2e8c6a34d2ad1b8cbea91acb4ae.tar.gz
openembedded-core-254899824900f2e8c6a34d2ad1b8cbea91acb4ae.tar.bz2
openembedded-core-254899824900f2e8c6a34d2ad1b8cbea91acb4ae.zip
mkefidisk.sh: Allow using a loopback mounted file
It should be possible to generate a disk to a file using a loopback device with mkefidisk.sh, which is useful for booting simulators. To make this possible the partitions for the loop back need to work similarly to the mmc devices. The mkfs.vfat also requires and additional argument to force it to write to something other then a real disk. Example: qemu-img create -f raw bigdisk 4G dev=`sudo losetup -f` sudo losetup $dev bigdisk mkefidisk.sh $dev tmp-eglibc/deploy/images/qemux86/core-image-minimal-qemux86.hddimg /dev/sda sudo losetup -d $dev Note: Also a bug was fixed in the mkefidisk.sh where if the disk you are writing to initially has an invalid label the size of the first partition will be computed incorrectly. For the simulator disk creation this is generally always the case, but this can happen with real hardware as well. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/boot-directdisk.bbclass')
0 files changed, 0 insertions, 0 deletions