From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: devel@edk2.groups.io, quic_llindhol@quicinc.com
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Graeme Gregory <graeme@xora.org.uk>,
Radoslaw Biernacki <rad@semihalf.com>
Subject: Re: [edk2-devel] [PATCH edk2-platforms 0/2] SbsaQemu: make GIC base address Pcds dynamic
Date: Tue, 30 May 2023 18:43:17 +0200 [thread overview]
Message-ID: <3484a465-3f0a-80ab-8f52-f427da59ef9d@linaro.org> (raw)
In-Reply-To: <20230512175753.13318-1-quic_llindhol@quicinc.com>
W dniu 12.05.2023 o 19:57, Leif Lindholm pisze:
> Currently, the GIC and redistributors base addresses are defined using
> FixedPcds.
>
> In order to enable the QEMU platform to evolve to provide ITS frames,
> as well as newer versions of the GIC, convert these accesses to Dynamic.
>
> Firtsly, this requires fixing the bug of the addresses being read as 32-bit
> Pcds, and then moving the declarations and calls to the dynamic form.
>
> Cc: Ard Biesheuvel<ardb+tianocore@kernel.org>
> Cc: Graeme Gregory<graeme@xora.org.uk>
> Cc: Radoslaw Biernacki<rad@semihalf.com>
> Cc: Marcin Juszkiewicz<marcin.juszkiewicz@linaro.org>
>
> Leif Lindholm (2):
> Silicon/Qemu: use 64-bit Pcds for SbsaQemu GIC addresses
> Silicon/Qemu: use dynamic Pcds for SbsaQemu GIC addresses
Tested-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
prev parent reply other threads:[~2023-05-30 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 17:57 [PATCH edk2-platforms 0/2] SbsaQemu: make GIC base address Pcds dynamic Leif Lindholm
2023-05-12 17:57 ` [PATCH edk2-platforms 1/2] Silicon/Qemu: use 64-bit Pcds for SbsaQemu GIC addresses Leif Lindholm
2023-05-16 10:45 ` [edk2-devel] " Sami Mujawar
2023-05-12 17:57 ` [PATCH edk2-platforms 2/2] Silicon/Qemu: use dynamic " Leif Lindholm
2023-05-16 10:45 ` [edk2-devel] " Sami Mujawar
2023-05-16 10:18 ` [edk2-devel] [PATCH edk2-platforms 0/2] SbsaQemu: make GIC base address Pcds dynamic Graeme Gregory
2023-06-01 18:34 ` Leif Lindholm
2023-05-30 16:43 ` 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=3484a465-3f0a-80ab-8f52-f427da59ef9d@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