On 11/8/23 02:06, Michael D Kinney wrote:
> Hi Jose,
>
>
>
> 1. This logic needs to move into an AARCH64 specific directory/file.
> Other architectures handle this in other ways.
> 2. There are many places throughout edk2 sources that perform PCI
> config write operations. You are
Hi Jose,
1. This logic needs to move into an AARCH64 specific directory/file. Other
architectures handle this in other ways.
2. There are many places throughout edk2 sources that perform PCI config
write operations. You are only fixing it in a single location. You may want
to look at
++ Laszlo and Michael
On Tue, Nov 7, 2023 at 10:54 AM Jose Lopez wrote:
> ++ CC'd
>
>
> On Mon, Nov 6, 2023 at 6:02 PM Joe Lopez wrote:
>
>> From: joelopez333
>>
>> REF:https://edk2.groups.io/g/devel/topic/102310377#110456
>>
>> Problem Report:
>>
>> On AARCH64, there is no
++ CC'd
On Mon, Nov 6, 2023 at 6:02 PM Joe Lopez wrote:
> From: joelopez333
>
> REF:https://edk2.groups.io/g/devel/topic/102310377#110456
>
> Problem Report:
>
> On AARCH64, there is no ordering guarantee between configuration
> space (ECAM) writes and memory space reads
From: joelopez333
REF:https://edk2.groups.io/g/devel/topic/102310377#110456
Problem Report:
On AARCH64, there is no ordering guarantee between configuration
space (ECAM) writes and memory space reads (MMIO). ARM AMBA CHI
only guarantees ordering for reads and writes within
