From: Christopher Larson <kergoth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: [PATCH 0/3] Deploy startup.nsh for wic's bootimg-efi plugin
Date: Wed, 25 May 2016 13:31:40 -0700 [thread overview]
Message-ID: <cover.1464208170.git.chris_larson@mentor.com> (raw)
From: Christopher Larson <chris_larson@mentor.com>
Currently, wic EFI images don't 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.
Alter grub-efi.bbclass and gummiboot.bbclass to write it for the non-iso case,
not only iso, so wic can grab and use it, and alter wic's bootimg-efi plugin to
do so.
The following changes since commit bb4ead9b7b1400c37a72d148d9775bdf4210ec37:
linux-yocto/4.4: integrate v4.4.11 (2016-05-25 07:49:55 +0100)
are available in the git repository at:
git://github.com/kergoth/openembedded-core yocto-9556
https://github.com/kergoth/openembedded-core/tree/yocto-9556
Christopher Larson (3):
grub-efi.bbclass: also write startup.nsh for non-iso
gummiboot.bbclass: also write startup.nsh for non-iso
wic: bootimg-efi: include startup.nsh if it's available
meta/classes/grub-efi.bbclass | 2 ++
meta/classes/gummiboot.bbclass | 2 ++
scripts/lib/wic/plugins/source/bootimg-efi.py | 5 +++++
3 files changed, 9 insertions(+)
--
2.8.0
next reply other threads:[~2016-05-25 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 20:31 Christopher Larson [this message]
2016-05-25 20:31 ` [PATCH 1/3] grub-efi.bbclass: also write startup.nsh for non-iso Christopher Larson
2016-05-25 20:31 ` [PATCH 2/3] gummiboot.bbclass: " Christopher Larson
2016-05-25 20:31 ` [PATCH 3/3] wic: bootimg-efi: include startup.nsh if it's available Christopher Larson
2016-05-25 20:33 ` [PATCH 0/3] Deploy startup.nsh for wic's bootimg-efi plugin Christopher Larson
2016-05-25 20:35 ` Christopher Larson
2016-05-30 12:33 ` Ed Bartosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1464208170.git.chris_larson@mentor.com \
--to=kergoth@gmail.com \
--cc=chris_larson@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox