Hi Heinrich,
On Sat, 18 Nov 2023 at 16:06, Heinrich Schuchardt
wrote:
>
> On 11/18/23 18:58, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Sat, 18 Nov 2023 at 10:34, Heinrich Schuchardt
> > wrote:
> >>
> >> On 11/18/23 18:10, Simon Glass wrote:
> >>> Hi Heinrich,
> >>>
> >>> On Thu, 16 Nov 2023
On 11/18/23 18:58, Simon Glass wrote:
Hi Heinrich,
On Sat, 18 Nov 2023 at 10:34, Heinrich Schuchardt
wrote:
On 11/18/23 18:10, Simon Glass wrote:
Hi Heinrich,
On Thu, 16 Nov 2023 at 02:29, Heinrich Schuchardt
wrote:
ACPI tables cannot convey memory reservations for least ARM and RISC-V.
Hi Heinrich,
On Sat, 18 Nov 2023 at 10:34, Heinrich Schuchardt
wrote:
>
> On 11/18/23 18:10, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Thu, 16 Nov 2023 at 02:29, Heinrich Schuchardt
> > wrote:
> >>
> >> ACPI tables cannot convey memory reservations for least ARM and RISC-V.
> >> x86 uses th
On 11/18/23 18:10, Simon Glass wrote:
Hi Heinrich,
On Thu, 16 Nov 2023 at 02:29, Heinrich Schuchardt
wrote:
ACPI tables cannot convey memory reservations for least ARM and RISC-V.
x86 uses the BIOS E820 table for this purpose. We cannot simply ignore the
device-tree when booting via ACPI.
W
Hi Heinrich,
On Thu, 16 Nov 2023 at 02:29, Heinrich Schuchardt
wrote:
>
> ACPI tables cannot convey memory reservations for least ARM and RISC-V.
> x86 uses the BIOS E820 table for this purpose. We cannot simply ignore the
> device-tree when booting via ACPI.
Why is that? I had thought that we h
ACPI tables cannot convey memory reservations for least ARM and RISC-V.
x86 uses the BIOS E820 table for this purpose. We cannot simply ignore the
device-tree when booting via ACPI. We have to assign EfiReservedMemory
according to the prior stage device-tree ($fdtaddr) or as fallback the
control de
6 matches
Mail list logo
