From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Michelle Lin <michelle.linto91@gmail.com>,
Erik Schilling <erik.schilling@linaro.org>
Subject: Re: [OE-core] [PATCH 2/2] uki.bbclass: add class for building Unified Kernel Images (UKI)
Date: Mon, 2 Sep 2024 14:23:40 +0300 [thread overview]
Message-ID: <ZtWgPF0JN4uyjU1u@nuoska> (raw)
In-Reply-To: <CANNYZj-cgTaKagNxx2mxTkPsp4U-JNNGrruUDUSPbn_cFz6+nw@mail.gmail.com>
Hi,
On Mon, Sep 02, 2024 at 01:11:27PM +0200, Alexander Kanavin wrote:
> Should this also have a wic based selftest or some other way to ensure it
> works?
Yes, but that depends on the UEFI / Arm System Ready compatible firmware.
For qemu, this can be setup using meta-arm and qemuarm64-secureboot machine
config. The patches for UEFI secure boot are currently in review and if approved
I will switch those to boot uki binaries, patches are ready but not submitted
yet.
I don't know if poky alone can provide UEFI firmware to boot with.
Cheers,
-Mikko
next prev parent reply other threads:[~2024-09-02 11:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 10:58 [PATCH 0/3] systemd uki support Mikko Rapeli
2024-09-02 10:58 ` [PATCH 1/2] systemd-boot-native: add runtime dependency to python3-pefile-native Mikko Rapeli
2024-09-02 10:58 ` [PATCH 2/2] uki.bbclass: add class for building Unified Kernel Images (UKI) Mikko Rapeli
2024-09-02 11:11 ` [OE-core] " Alexander Kanavin
2024-09-02 11:23 ` Mikko Rapeli [this message]
2024-09-02 12:01 ` Alexander Kanavin
2024-09-02 12:25 ` Mikko Rapeli
2024-09-02 13:03 ` Alexander Kanavin
2024-09-02 13:15 ` Mikko Rapeli
[not found] ` <17F16FAE8869E0F4.11433@lists.openembedded.org>
2024-09-02 14:14 ` Mikko Rapeli
2024-09-02 14:30 ` Alexander Kanavin
2024-09-04 7:56 ` Mikko Rapeli
2024-09-04 9:17 ` Alexander Kanavin
2024-09-04 10:04 ` Mikko Rapeli
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=ZtWgPF0JN4uyjU1u@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=alex.kanavin@gmail.com \
--cc=erik.schilling@linaro.org \
--cc=michelle.linto91@gmail.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