On 11/7/2020 1:09 AM, Laszlo Ersek wrote:
On 11/05/20 05:30, Ying Fang wrote:
I see it in Qemu the *loader_start* is fixed at 1 GiB on the
physical address space which points to the DRAM base. In ArmVirtQemu.dsc
PcdDeviceTreeInitialBaseAddress is set 0x4000 with correspondence.
Here I
On 11/05/20 05:30, Ying Fang wrote:
> I see it in Qemu the *loader_start* is fixed at 1 GiB on the
> physical address space which points to the DRAM base. In ArmVirtQemu.dsc
> PcdDeviceTreeInitialBaseAddress is set 0x4000 with correspondence.
>
> Here I also see the discussion about DRAM
On 11/5/2020 5:46 AM, Laszlo Ersek wrote:
+Ard, +Drew
On 11/03/20 13:39, Igor Mammedov wrote:
On Fri, 30 Oct 2020 10:50:01 +0800
Ying Fang wrote:
Hi,
I have a question on UEFI/ACPI tables setup and probing on arm64 platform.
CCing Laszlo,
who might know how it's implemented.
On 11/4/20 10:46 PM, Laszlo Ersek wrote:
...
(9) (Ard, please correct the below if necessary; thanks.)
The UEFI stub of the guest kernel (which is a UEFI application) uses a
device tree as its main communication channel to the (later-started)
kernel entry point, AIUI.
The UEFI stub basically
+Ard, +Drew
On 11/03/20 13:39, Igor Mammedov wrote:
> On Fri, 30 Oct 2020 10:50:01 +0800
> Ying Fang wrote:
>
>> Hi,
>>
>> I have a question on UEFI/ACPI tables setup and probing on arm64 platform.
>
> CCing Laszlo,
> who might know how it's implemented.
>
>> Currently on arm64 platform
On Fri, 30 Oct 2020 10:50:01 +0800
Ying Fang wrote:
> Hi,
>
> I have a question on UEFI/ACPI tables setup and probing on arm64 platform.
CCing Laszlo,
who might know how it's implemented.
> Currently on arm64 platform guest can be booted with both fdt and ACPI
> supported. If ACPI is
Hi,
I have a question on UEFI/ACPI tables setup and probing on arm64 platform.
Currently on arm64 platform guest can be booted with both fdt and ACPI
supported. If ACPI is enabled, [1] says the only defined method for
passing ACPI tables to the kernel is via the UEFI system configuration
table.
