Bug 9556 - The EFI bootloaders should deploy startup.nsh for wic
Summary: The EFI bootloaders should deploy startup.nsh for wic
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 2.2 M2
Assignee: Christopher Larson
QA Contact: David Rodriguez
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-04-28 16:25 UTC by Christopher Larson
Modified: 2016-05-31 18:58 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Larson 2016-04-28 16:25:36 UTC
Currently, wic EFI images dont' end up with startup.nsh, so the user has to type in the correct bits into the EFI command-line, which isn't very user-friendly. mkefidisk.sh in oe-core writes it for us, but we don't get it for wic images. Rather than hardcoding it into wic, lets deploy it and let wic grab it from there and drop it into the boot partition.
Comment 1 Christopher Larson 2016-05-25 19:28:44 UTC
Initially, I had thought to do this in the recipes, but bootimg-efi doesn't pull IMAGE_BOOT_FILES from DEPLOY_DIR_IMAGE, it pulls from HDDDIR, so the bbclasses will have to do it instead. IMO we should divorce bootimg-efi from image-live/bootimg entirely and have it just pull from DEPLOY_DIR_IMAGE. It already duplicates the bootloader config file generation, so it should just do the rest as well, but we can improve that as a subsequent task. For now I'm altering the grub-efi and gummiboot classes to write startup.nsh to hdddir for non-iso for wic to use, and patching bootimg-efi to grab it if it's available.
Comment 2 Christopher Larson 2016-05-25 20:35:35 UTC
Sent to the oe-core list for review.