From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
Felix Moessbauer <felix.moessbauer@siemens.com>,
Florian Bezdeka <florian.bezdeka@siemens.com>
Subject: Re: [PATCH] bitbake: Update to 1.50.5 release
Date: Thu, 21 Apr 2022 10:02:38 +0200 [thread overview]
Message-ID: <20220421100238.6381ea51@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <eb81efd1-6015-c581-0f0b-9a6df48a5b7e@siemens.com>
Am Wed, 20 Apr 2022 18:24:42 +0200
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> On 20.04.22 17:52, Henning Schild wrote:
> > Am Wed, 20 Apr 2022 17:00:59 +0200
> > schrieb Henning Schild <henning.schild@siemens.com>:
> >
> >> While that kind of works, the next trouble with python 3.10 will
> >> be in wic.
> >
> > I am already looking into the wic version bump, it seems to be
> > rather easy. There was some merging around our forked plugins with
> > a new feature "create-unified-kernel-image" which might not work.
> > But that might even be left like it is until someone uses that.
>
> Where we are currently consuming unified kernels, this tends to happen
> in EFI Boot Guard context with the related wic plugin that already
> supports this. In addition, the unified kernel stub that systemd
> provides showed some limitations on ARM platforms with DTB replacement
> needs. That's why we are about deploy an own one (via EBG) with own
> integration process.
>
> Long story short: I don't expect an urgent need for OE's/systemd's
> unified-kernel-image.
Ok i will include the code because we inherit it, but will not test
that path, let alone enable it should it not work.
Henning
> Jan
>
next prev parent reply other threads:[~2022-04-21 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 14:35 Henning Schild
2022-04-20 15:00 ` Henning Schild
2022-04-20 15:52 ` Henning Schild
2022-04-20 16:24 ` Jan Kiszka
2022-04-21 8:02 ` Henning Schild [this message]
2022-04-21 8:40 ` Bezdeka, Florian
2022-04-21 8:55 ` Henning Schild
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=20220421100238.6381ea51@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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