zephyr/tests/arch
Andy Ross 41e885947e arch/x86: Correct multiboot interpretation when building for EFI
When loaded via EFI, we obviously don't have a multiboot info pointer
available (we might have an EFI system table, but zefi doesn't pass
that through yet).  Don't try to parse the "whatever garbage was in
%rbp" as a multiboot table.

The configuration is a little clumsy, as strictly our EFI kconfig just
says we're "building for" EFI but not that we'll boot that way.  And
tests like arch/x86/info are trying to set CONFIG_MULTIBOOT=n
unconditionally, when it really should be something they detect from
devicetree or wherever.

Fixes #33545

Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2021-05-15 15:30:02 -04:00
..
arm modules: tf-m: do not expose TF-M NS interface include directories publicly 2021-05-09 09:59:22 -05:00
arm64/arm64_psci test: arm_psci: Move test to arm64_psci directory 2021-03-23 17:02:58 -04:00
x86 arch/x86: Correct multiboot interpretation when building for EFI 2021-05-15 15:30:02 -04:00
xtensa_asm2 xtensa: add support for thread local storage 2020-10-24 10:52:00 -07:00