Searched hist:"3 e909599215456928e6b42a04f11c2517881570b" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | efi.h | diff 3e909599215456928e6b42a04f11c2517881570b Wed Jan 15 07:21:22 CST 2014 Matt Fleming <matt.fleming@intel.com> efi: Move facility flags to struct efi
As we grow support for more EFI architectures they're going to want the
ability to query which EFI features are available on the running system.
Instead of storing this information in an architecture-specific place,
stick it in the global 'struct efi', which is already the central
location for EFI state.
While we're at it, let's change the return value of efi_enabled() to be
bool and replace all references to 'facility' with 'feature', which is
the usual word used to describe the attributes of the running system.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
| /openbmc/linux/arch/x86/platform/efi/ |
| H A D | efi.c | diff 3e909599215456928e6b42a04f11c2517881570b Wed Jan 15 07:21:22 CST 2014 Matt Fleming <matt.fleming@intel.com> efi: Move facility flags to struct efi
As we grow support for more EFI architectures they're going to want the
ability to query which EFI features are available on the running system.
Instead of storing this information in an architecture-specific place,
stick it in the global 'struct efi', which is already the central
location for EFI state.
While we're at it, let's change the return value of efi_enabled() to be
bool and replace all references to 'facility' with 'feature', which is
the usual word used to describe the attributes of the running system.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
| /openbmc/linux/include/linux/ |
| H A D | efi.h | diff 3e909599215456928e6b42a04f11c2517881570b Wed Jan 15 07:21:22 CST 2014 Matt Fleming <matt.fleming@intel.com> efi: Move facility flags to struct efi
As we grow support for more EFI architectures they're going to want the
ability to query which EFI features are available on the running system.
Instead of storing this information in an architecture-specific place,
stick it in the global 'struct efi', which is already the central
location for EFI state.
While we're at it, let's change the return value of efi_enabled() to be
bool and replace all references to 'facility' with 'feature', which is
the usual word used to describe the attributes of the running system.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|
| /openbmc/linux/arch/x86/kernel/ |
| H A D | setup.c | diff 3e909599215456928e6b42a04f11c2517881570b Wed Jan 15 07:21:22 CST 2014 Matt Fleming <matt.fleming@intel.com> efi: Move facility flags to struct efi
As we grow support for more EFI architectures they're going to want the
ability to query which EFI features are available on the running system.
Instead of storing this information in an architecture-specific place,
stick it in the global 'struct efi', which is already the central
location for EFI state.
While we're at it, let's change the return value of efi_enabled() to be
bool and replace all references to 'facility' with 'feature', which is
the usual word used to describe the attributes of the running system.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
|