> On 1. Aug 2025, at 21:42, Pierrick Bouvier <pierrick.bouv...@linaro.org>
> wrote:
>
> On 8/1/25 12:31 PM, Mohamed Mediouni wrote:
>>>> I didn’t test anything on the stable branch for now but only on Canary so
>>>> far.
>>>> Just cursorily tested (EDK2 only) an X Elite device on prod (26100.4652)
>>>> and this issue doesn’t appear.
>>>> I have 8cx Gen 3 and 8cx Gen 1 (SQ1) devices around, will test on those
>>>> older SoCs later and see.
>>>> Random idea for testing: what if you put -M highmem=off, does that change
>>>> anything?
>>>>
>>>
>>> Good guess, it solves the problem with edk2, and direct boots linux kernel
>>> successfully now.
>>>
>> If you don’t mind, could you please test the latest commit I just put on the
>> Git repo (whpx branch)? It should address this properly.
>
> Sure.
> Without highmem=off, I get a new error:
> Physical address width: 36
> C:\msys64\home\tcwg\qemu\build\qemu-system-aarch64.exe: VCPU supports less PA
> bits (36) than requested by the memory map (40)
>
Oh this confirms what I thought, just pushed a new commit which should be a
complete fix. :)
And accessorily is also a good thing for Snapdragon X too, as 40 VA bits were
used there despite the hardware having 39.
Thank you,
-Mohamed
