Bug 10212 - Support to deploy non-bootloader-specific files in EFI partition when build hddimg image
Summary: Support to deploy non-bootloader-specific files in EFI partition when build h...
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-oe-core (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.3 M2
Assignee: Todor Minchev
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 10126
  Show dependency tree
 
Reported: 2016-09-02 19:45 UTC by Jianxun Zhang
Modified: 2017-01-13 08:54 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jianxun Zhang 2016-09-02 19:45:46 UTC
Currently only bootloader-specific artifacts (grub-efi or systemd-boot/gummiboot) can be deployed to EFI FAT partition when building a hddimg image. It meets usual requirements to boot an EFI system, but limits the support once we need to deploy files for other EFI application or document text files on installation media.

We need some way in some OE classes to achieve this. Note this task does't cover direct-boot with wic which should be a backend to consume whatever we deployed into hddimg dir (per my opinion). The later is tracked in:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10073

I mark this ticket to cause document change, assuming a new variable or syntax added for this feature.
Comment 1 Todor Minchev 2016-12-13 23:03:15 UTC
Patch sent to mailing list for review:
https://lists.yoctoproject.org/pipermail/yocto/2016-December/033537.html
Comment 2 Todor Minchev 2016-12-21 16:47:47 UTC
patch merged