[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z0TGS+EA8JlO3WXq@e129823.arm.com>
Date: Mon, 25 Nov 2024 18:47:39 +0000
From: Levi Yun <yeoreum.yun@....com>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: broonie@...nel.org, sami.mujawar@....com, sudeep.holla@....com,
pierre.gondois@....com, hagarhem@...zon.com,
catalin.marinas@....com, will@...nel.org, guohanjun@...wei.com,
Jonathan.Cameron@...wei.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org
Subject: Re: [PATCH v2 2/2] efi/fdt: ignore dtb when acpi option is used with
force
Hi Ard,
> Thanks for explaining the issue in more detail. Juno is a development
> platform with a highly unusual boot stack so I don't think we need to
> accommodate its quirks in the upstream kernel.
>
> And I still don't think this is something worth fixing in general.
> Even if the machine description should be taken from ACPI tables only,
> the DT /chosen node is always used as a conduit by the EFI stub, and
> there are cases, e.g., for initrd info or the kaslr seed, where this
> information might come from the bootloader, such as older GRUB builds.
But suppose the DT loaded is corrupted (i.e.) no property for
"#size-cells" in root node.
In this case, uefi properties in chosen node will be installed in
"corrupted" root node.
my suggetion is not to check "acpi=force" option but verify dt which
loaded via dtb= command line option or
via configuration table in efi-stub code before updating
fdt with uefi properties in chosen node so that prevent generating error
message.
Am I missing?
Thanks
Powered by blists - more mailing lists