summaryrefslogtreecommitdiffstats
path: root/include/linux/efi.h
diff options
context:
space:
mode:
authorMatt Fleming <matt.fleming@intel.com>2014-01-15 13:49:51 +0000
committerMatt Fleming <matt.fleming@intel.com>2014-03-04 16:17:20 +0000
commit092063808c498eccac8e891973bf143e7b60d723 (patch)
treefd07996db565ebe33beb787c524b877ddd73577a /include/linux/efi.h
parentfabb37c736f9f688fe3eec98550a5c032a07cfaa (diff)
downloadtalos-obmc-linux-092063808c498eccac8e891973bf143e7b60d723.tar.gz
talos-obmc-linux-092063808c498eccac8e891973bf143e7b60d723.zip
ia64/efi: Implement efi_enabled()
There's no good reason to keep efi_enabled() under CONFIG_X86 anymore, since nothing about the implementation is specific to x86. Set EFI feature flags in the ia64 boot path instead of claiming to support all features. The old behaviour was actually buggy since efi.memmap never points to a valid memory map, so we shouldn't be claiming to support EFI_MEMMAP. Fortunately, this bug was never triggered because EFI_MEMMAP isn't used outside of arch/x86 currently, but that may not always be the case. Reviewed-and-tested-by: Tony Luck <tony.luck@intel.com> Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Diffstat (limited to 'include/linux/efi.h')
-rw-r--r--include/linux/efi.h8
1 files changed, 0 insertions, 8 deletions
diff --git a/include/linux/efi.h b/include/linux/efi.h
index 214833b4a97d..64d532ca890a 100644
--- a/include/linux/efi.h
+++ b/include/linux/efi.h
@@ -660,8 +660,6 @@ extern int __init efi_setup_pcdp_console(char *);
#define EFI_ARCH_1 6 /* First arch-specific bit */
#ifdef CONFIG_EFI
-# ifdef CONFIG_X86
-
/*
* Test whether the above EFI_* bits are enabled.
*/
@@ -669,12 +667,6 @@ static inline bool efi_enabled(int feature)
{
return test_bit(feature, &efi.flags) != 0;
}
-# else
-static inline bool efi_enabled(int feature)
-{
- return true;
-}
-# endif
#else
static inline bool efi_enabled(int feature)
{
OpenPOWER on IntegriCloud