On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
> Using the latest mkisofs it is possible to generate 3 different types
> of ISO images, which can be used in various scenarios.
>
> 1) PCBIOS Only ISO
> - This option remains unchanged by this commit
> - Uses syslinux menus
> - Can be directly copied with dd to a USB device
> - Can be burned to optical media
>
> 2) EFI Only ISO
> - Uses grub 2 menus
> - Can be burned to optical media
> - If you want to use this image on a USB device
> extra steps must be taken in order to format the USB
> device with fat32, and copy an EFI loader which will
> in turn load the iso image
>
> 3) PCBIOS / EFI ISO
> - This is a hybrid image ISO that will work for case 1 or 2
> as above with the same restrictions and boot menu types
> depending on what type of firmware is installed on
> the hardware or depending on if EFI or "Legacy Boot" is
> enabled on some UEFI firmwares.
>
> [YOCTO #4100]
>
> Signed-off-by: Jason Wessel <jason.wes...@windriver.com>
> ---
> meta/classes/bootimg.bbclass | 37 ++++++++++++++++++++++++++++++++++---
> 1 file changed, 34 insertions(+), 3 deletions(-)
>
> diff --git a/meta/classes/bootimg.bbclass b/meta/classes/bootimg.bbclass
> index 2ed7017..b4301e8 100644
> --- a/meta/classes/bootimg.bbclass
> +++ b/meta/classes/bootimg.bbclass
> @@ -35,6 +35,7 @@ EXCLUDE_FROM_WORLD = "1"
>
> HDDDIR = "${S}/hddimg"
> ISODIR = "${S}/iso"
> +EFIIMGDIR = "${S}/efi_img"
> COMPACT_ISODIR = "${S}/iso.z"
>
> BOOTIMG_VOLUME_ID ?= "boot"
> @@ -109,19 +110,49 @@ build_iso() {
> mkisofs_opts="-R -z -D -l"
> fi
>
Am I missing a patch? I don't have this mkisofs_opts in my
bootimg.bbclass....
How are $mkisofs_opts and ${MKISOFS_OPTIONS} related? Do we need both?
> - if [ "${PCBIOS}" = "1" ]; then
> + if [ "${EFI}" = "1" ] ; then
> + # Build a EFI directory to create efi.img
> + mkdir -p ${EFIIMGDIR}/${EFIDIR}
> + cp ${ISODIR}/${EFIDIR}/* ${EFIIMGDIR}${EFIDIR}
> + cp ${ISODIR}/vmlinuz ${EFIIMGDIR}
> + GRUB_IMAGE="bootia32.efi"
> + if [ "${TARGET_ARCH}" = "x86_64" ]; then
> + GRUB_IMAGE="bootx64.efi"
> + fi
> + echo "EFI\\BOOT\\${GRUB_IMAGE}" > ${EFIIMGDIR}/startup.nsh
> + if [ -f "${ISODIR}/initrd" ] ; then
> + cp ${ISODIR}/initrd ${EFIIMGDIR}
> + fi
> + build_fat_img ${EFIIMGDIR} ${ISODIR}/efi.img
> + fi
> +
> + # Three ways to build the media
> + if [ "${PCBIOS}" = "1" -a "${EFI}" = "1" ]; then
Per the Dash as BinSh wiki, the -a syntax is discouraged, best practices
seem to be the use of && and || instead:
if ([ "${PCBIOS}" = "1" ] && [ "${EFI}" = "1" ]); then
> + # 1) Build EFI + PCBIOS hybrid
> + mkisofs -A ${BOOTIMG_VOLUME_ID} -V ${BOOTIMG_VOLUME_ID} \
> + -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.iso \
> + -b ${ISO_BOOTIMG} -c ${ISO_BOOTCAT} $mkisofs_opts \
> + ${MKISOFS_OPTIONS} \
> + -eltorito-alt-boot -eltorito-platform efi \
> + -b efi.img -no-emul-boot \
> + ${ISODIR}
Has this been verified on any 32 bit PCBIOS platforms?
It was my understanding the many 32 bit PCBIOS systems had very buggy
el-torito support and didn't deal well with multiple el-torito images on
the same disk. Although... looking at the command above, I'm not sure
you're doing this with mutliple images. Do you have the syslinux and the
efi image combined in the same efi.img?
Has this been verified to work on USB media?
It was explained to me that, at least for some implementations, if the
boot device selection code will not look for ISO9660 on anything that
doesn't have a block size of 2048, making it give up on a USB device
before even attempting to find the ISO9660 FS.
> + elif [ "${PCBIOS}" = "1" ] ; then
> + # 2) Build PCBIOS only media
> mkisofs -V ${BOOTIMG_VOLUME_ID} \
> -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.iso \
> -b ${ISO_BOOTIMG} -c ${ISO_BOOTCAT} $mkisofs_opts \
> ${MKISOFS_OPTIONS} ${ISODIR}
> else
This should also verify that we are building for EFI. !PCBIOS != EFI. If
none of these options eval to true, an error should be printed
> - bbnote "EFI-only ISO images are untested, please provide
> feedback."
> mkisofs -V ${BOOTIMG_VOLUME_ID} \
> -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.iso \
> + -eltorito-alt-boot -eltorito-platform efi \
> + -b efi.img -no-emul-boot \
> -r ${ISODIR}
> fi
>
> - isohybrid ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.iso
> + if [ "${PCBIOS}" = "1" ]; then
> + isohybrid ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.iso
> + fi
A comment would be good around the isohybrid block describing what it is
doing and why it only applies to PCBIOS.
>
> cd ${DEPLOY_DIR_IMAGE}
> rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.iso
Thanks Jason, this is long overdue. Your effort here is very much
appreciated.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
