All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] uki.bbclass: add class for building Unified Kernel Images (UKI)
Date: Wed, 4 Sep 2024 10:56:42 +0300	[thread overview]
Message-ID: <ZtgSunyGsn1gtMfF@nuoska> (raw)
In-Reply-To: <CANNYZj8rA+unjecEiofA3Ht94Y2mqBygLnBP-rWEeZPfEEq+Kw@mail.gmail.com>

Hi,

On Mon, Sep 02, 2024 at 04:30:53PM +0200, Alexander Kanavin wrote:
> On Mon, 2 Sept 2024 at 16:15, Mikko Rapeli <mikko.rapeli@linaro.org> wrote:
> 
> > So, this is a wic image format specific re-implementation of systemd ukify.py script.
> > Calling not systemd ukify.py but objcopy directly. No control over kernel command
> > line, but could possible be added with simple patch. I don't see how to hook uki
> > signing into the mix with custom keys. Maybe a post processing step to the .wic
> > image build.
> >
> > Since this version is merged I presume ukify.bbclass will be rejected.
> 
> Not rejected per se; I would suggest that the existing wic
> implementation is rewritten to use the class (and hopefully becomes
> radically simpler and shorter)!
> 
> It's fine to not be entirely backwards compatible; this is master, and
> we can break things.

Does the implementation have to be a wic plugin?

wic is another wrapper over bitbake and I'd need to teach openssl native
and python3native things to it which seems a bit too much. uki.bbclass
is much simpler and wic can process the produced .efi file when creating
the ESP boot partition. I can try to fix the tests to work with uki.bbclass.

Cheers,

-Mikko


  reply	other threads:[~2024-09-04  7:56 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
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 [this message]
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=ZtgSunyGsn1gtMfF@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=alex.kanavin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.