From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: Rebecca Cran <rebecca@os.amperecomputing.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
Ard Biesheuvel <ardb@kernel.org>,
Leif Lindholm <quic_llindhol@quicinc.com>
Subject: Re: [edk2-devel] SbsaQemu: SIP_SVC_GET_CPU_TOPOLOGY call failed (need updated binaries in edk2-non-osi?)
Date: Mon, 2 Sep 2024 12:54:23 +0200 [thread overview]
Message-ID: <6e44c6d7-f188-4fcf-a6e5-5fecff7ca913@linaro.org> (raw)
In-Reply-To: <2d7019b1-52fa-4d5e-9a18-2be4510fd0d2@os.amperecomputing.com>
On 30.08.2024 16:36, Rebecca Cran wrote:
> 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.
Ops, forgot to update binaries. Sent patch for review.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120465): https://edk2.groups.io/g/devel/message/120465
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]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2024-09-02 10:54 UTC|newest]
Thread overview: 2+ 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 [this message]
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=6e44c6d7-f188-4fcf-a6e5-5fecff7ca913@linaro.org \
--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