From: "Rebecca Cran via groups.io" <rebecca=os.amperecomputing.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Ard Biesheuvel <ardb@kernel.org>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
Leif Lindholm <quic_llindhol@quicinc.com>
Subject: [edk2-devel] SbsaQemu: SIP_SVC_GET_CPU_TOPOLOGY call failed (need updated binaries in edk2-non-osi?)
Date: Fri, 30 Aug 2024 08:36:27 -0600 [thread overview]
Message-ID: <2d7019b1-52fa-4d5e-9a18-2be4510fd0d2@os.amperecomputing.com> (raw)
Do the TF-A binaries in edk2-non-osi need updated for SbsaQemu?
With the binaries in Platform/Qemu/Sbsa I get the following error during
boot:
GetCpuCount: We have 4 cpus.
GetMpidr: MPIDR for CPU0: = 0
GetMpidr: MPIDR for CPU1: = 1
GetMpidr: MPIDR for CPU2: = 2
GetMpidr: MPIDR for CPU3: = 3
GetCpuCount: We have 4 cpus.
ERROR: sbsa_sip_smc_handler: unhandled SMC (0xc20000ca) (function id: 202)
GetCpuTopology: SIP_SVC_GET_CPU_TOPOLOGY call failed. We have no cpu
topology information.
If I update the binaries with a fresh set built from TF-A commit
8e9bdc5b1d65f49546afbe97943d263a1332e67e it successfully boots to the
UEFI Shell.
--
Rebecca
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120481): https://edk2.groups.io/g/devel/message/120481
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]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2024-09-03 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 14:36 Rebecca Cran via groups.io [this message]
2024-09-02 10:54 ` [edk2-devel] SbsaQemu: SIP_SVC_GET_CPU_TOPOLOGY call failed (need updated binaries in edk2-non-osi?) Marcin Juszkiewicz
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=2d7019b1-52fa-4d5e-9a18-2be4510fd0d2@os.amperecomputing.com \
--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