summaryrefslogtreecommitdiff
path: root/drivers/ddr/imx/imx9/ddr_init.c
diff options
context:
space:
mode:
authorHeinrich Schuchardt <heinrich.schuchardt@canonical.com>2024-02-14 21:43:21 +0100
committerHeinrich Schuchardt <heinrich.schuchardt@canonical.com>2024-02-28 14:37:46 +0100
commitc9f368b597a02f9919cb0c1c03e6b231129e9262 (patch)
treedecb64beeaa7b3ffe7e2bb399d916f5bfa4e3767 /drivers/ddr/imx/imx9/ddr_init.c
parentd49fa3defa50c6d3f04acbb52fd486c13c14ab6a (diff)
efi_loader: set IMAGE_DLLCHARACTERISTICS_NX_COMPAT
The IMAGE_DLLCHARACTERISTICS_NX_COMPAT flag marks an EFI binary where the following conditions are met [1]: * Executable and writable sections are separated. * The application does not run self-modifying code. * The application uses the EFI_MEMORY_ATTRIBUTE_PROTOCOL when loading executable code. * The application does not assume that all memory ranges are usable. * The stack is not expected to be executable. The only EFI binaries U-Boot provides that do not fulfill these requirements are the EFI app and the EFI payload. Once we have implemented separation of writable and executable memory in U-Boot we can use the IMAGE_DLLCHARACTERISTICS_NX_COMPAT flag to decide if we will load an EFI binary. [1] New UEFI CA memory mitigation requirements for signing https://techcommunity.microsoft.com/t5/hardware-dev-center/new-uefi-ca-memory-mitigation-requirements-for-signing/ba-p/3608714 Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Diffstat (limited to 'drivers/ddr/imx/imx9/ddr_init.c')
0 files changed, 0 insertions, 0 deletions