diff options
author | Ard Biesheuvel <ardb@kernel.org> | 2020-02-12 14:18:17 +0300 |
---|---|---|
committer | Ard Biesheuvel <ardb@kernel.org> | 2020-02-23 23:59:42 +0300 |
commit | 97aa276579b28b86f4a3e235b50762c0191c2ac3 (patch) | |
tree | 3a596783c9cb995088e7d2b6c6c815150e0cfff9 /drivers/firmware/efi/fdtparams.c | |
parent | 17054f492dfd4d91e093ebb87013807812ec42a4 (diff) | |
download | linux-97aa276579b28b86f4a3e235b50762c0191c2ac3.tar.xz |
efi/x86: Add true mixed mode entry point into .compat section
Currently, mixed mode is closely tied to the EFI handover protocol
and relies on intimate knowledge of the bootparams structure, setup
header etc, all of which are rather byzantine and entirely specific
to x86.
Even though no other EFI supported architectures are currently known
that could support something like mixed mode, it still makes sense to
abstract a bit from this, and make it part of a generic Linux on EFI
boot protocol.
To that end, add a .compat section to the mixed mode binary, and populate
it with the PE machine type and entry point address, allowing firmware
implementations to match it to their native machine type, and invoke
non-native binaries using a secondary entry point.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'drivers/firmware/efi/fdtparams.c')
0 files changed, 0 insertions, 0 deletions