public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Johnny Lin/WYHQ/Wiwynn via groups.io" <johnny_lin=wiwynn.com@groups.io>
To: "Marcin Juszkiewicz" <marcin@juszkiewicz.com.pl>, devel@edk2.groups.io
Subject: Re: [edk2-devel] SbsaQemu: SIP_SVC_GET_CPU_TOPOLOGY call failed (need updated binaries in edk2-non-osi?)
Date: Sun, 23 Mar 2025 00:34:30 -0700	[thread overview]
Message-ID: <15989.1742715270038644235@groups.io> (raw)
In-Reply-To: <6e44c6d7-f188-4fcf-a6e5-5fecff7ca913@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 767 bytes --]

Has this been fixed? I am seeing the same issue with QEMU emulator version 8.0.93.
I just cloned edk2 (commit b279ac9f36) and edk2-platform (commit 276d8bca71) yesterday on March 23, 2025.

I also tried to checkout 8e9bdc5b1d65f49546 and build arm-trusted-firmware mentioned by Rebecca, but still seeing the same issue.
Not sure if my x86 QEMU version is also contributing to the issue.
Thanks!


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121227): https://edk2.groups.io/g/devel/message/121227
Mute This Topic: https://groups.io/mt/108224493/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 3359 bytes --]

  reply	other threads:[~2025-03-27  4:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30 14:36 [edk2-devel] SbsaQemu: SIP_SVC_GET_CPU_TOPOLOGY call failed (need updated binaries in edk2-non-osi?) Rebecca Cran via groups.io
2024-09-02 10:54 ` Marcin Juszkiewicz
2025-03-23  7:34   ` Johnny Lin/WYHQ/Wiwynn via groups.io [this message]
2025-03-23 12:50     ` Marcin Juszkiewicz via groups.io

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-list 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=15989.1742715270038644235@groups.io \
    --to=devel@edk2.groups.io \
    /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