[PATCH v3 14/30] efi_loader: Allocate and write ACPI tables

Tom Rini trini at konsulko.com
Fri Sep 20 00:52:08 CEST 2024


On Thu, Sep 19, 2024 at 02:45:30PM +0200, Patrick Rudolph wrote:
> On Thu, Sep 19, 2024 at 2:39 PM Heinrich Schuchardt <xypron.glpk at gmx.de> wrote:
> >
> > On 11.09.24 08:24, Patrick Rudolph wrote:
> > > Allocate memory for ACPI tables inside the efi_loader and write out
> > > the tables similar to SMBIOS tables. When ACPI is enabled and wasn't
> > > installed in other places, install the ACPI table in EFI. Since EFI
> > > is necessary to pass the ACPI table location when FDT isn't used,
> > > there's no need to install it separately.
> > >
> > > When CONFIG_BLOBLIST_TABLES is set the tables will be stored in a
> > > bloblist. The tables are still passed to the OS using EFI.
> > >
> > > This allows non x86 platforms to boot using ACPI only in case the
> > > EFI loader is being used.
> > >
> > > TEST: Booted QEMU SBSA (no QFW) using EFI and ACPI only.
> > >
> > > Signed-off-by: Patrick Rudolph <patrick.rudolph at 9elements.com>
> > > Cc: Simon Glass <sjg at chromium.org>
> > > Cc: Tom Rini <trini at konsulko.com>
> >
> > Could you, please, describe how QEMU SBSA is passing the ACPI table to
> > U-Boot and where you convert this to a bloblist. I could not find this
> > in patches 1-13.
> 
> I doesn't. All ACPI tables are generated within U-Boot.
> 
> >
> > Please, provide a test that we can run on our CI.
> How would such a test look like?

Similar to the existing QEMU ones found in .gitlab-ci.yml and
.azure-pipelines.yml

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20240919/97d5e1b0/attachment.sig>


More information about the U-Boot mailing list