From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [OE-core] [PATCH v2] u-boot: disable CONFIG_BLOBLIST on genericarm64 and qemuarm64
Date: Thu, 22 May 2025 13:57:24 +0300 [thread overview]
Message-ID: <aC8DFDTWfC_xGQ8s@nuoska> (raw)
In-Reply-To: <CANNYZj-8WFy0CWocfy911Gqc4nKYOfyZt4cPKx8PizOZxPNc+Q@mail.gmail.com>
Hi,
On Thu, May 22, 2025 at 12:51:25PM +0200, Alexander Kanavin wrote:
> On Wed, 21 May 2025 at 20:49, Mikko Rapeli via lists.openembedded.org
> <mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
> > +# workaround for aarch64 kvm qemu boot regression
> > +SRC_URI:append:qemuarm64 = " file://disable-CONFIG_BLOBLIST.cfg"
> > +SRC_URI:append:genericarm64 = " file://disable-CONFIG_BLOBLIST.cfg"
>
> What steps are going to be taken to get to the root cause of this?
> Does this workaround have to be kept forever?
We're following this up with u-boot upstream maintainers.
Then I'd like to add a selftest to oe-core for this usecase of
booting qemuarm64 and genericarm64 target images and u-boot
with qemu under kvm on native aarch64 build machine.
Sorting out some qemuarm64 runqemu details currently.
Cheers,
-Mikko
next prev parent reply other threads:[~2025-05-22 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 18:49 [PATCH v2] u-boot: disable CONFIG_BLOBLIST on genericarm64 and qemuarm64 Mikko Rapeli
2025-05-22 6:51 ` Ilias Apalodimas
2025-05-22 10:51 ` [OE-core] " Alexander Kanavin
2025-05-22 10:57 ` Mikko Rapeli [this message]
2025-05-22 11:08 ` Alexander Kanavin
2025-05-22 11:15 ` 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=aC8DFDTWfC_xGQ8s@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=alex.kanavin@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--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