public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
	Florian Bezdeka <florian.bezdeka@siemens.com>
Subject: Re: [PATCH] bitbake: Update to 1.50.5 release
Date: Wed, 20 Apr 2022 18:24:42 +0200	[thread overview]
Message-ID: <eb81efd1-6015-c581-0f0b-9a6df48a5b7e@siemens.com> (raw)
In-Reply-To: <20220420175230.684c4382@md1za8fc.ad001.siemens.net>

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.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux

  reply	other threads:[~2022-04-20 16:24 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 [this message]
2022-04-21  8:02       ` Henning Schild
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=eb81efd1-6015-c581-0f0b-9a6df48a5b7e@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.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