From: Matt Fleming
Some machines have an EFI variable interface that does not conform to
the UEFI specification, e.g. CONFIG_GOOGLE_SMI. Add the necessary code
so that it's only possible to use one implementation of EFI variable
operations at runtime. This allows us to keep a single (file-scope)
On 09/04/13 23:07, Mike Waychison wrote:
>> +config EFI_VARS_GENERIC_OPS
>> + bool
>> + depends on EFI
>> + depends on !GOOGLE_SMI
>> + default y
>> +
>
> So while we have no need to support both the gsmi and real efi
> entrypoints on any given machine, we still need to be
On Thu, Apr 4, 2013 at 5:18 AM, Matt Fleming wrote:
> From: Matt Fleming
>
> Some machines have an EFI variable interface that does not conform to the UEFI
> specification, e.g. CONFIG_GOOGLE_SMI. Add the necessary code and Kconfig glue
> so that it's only possible to select one implementation of
From: Matt Fleming
Some machines have an EFI variable interface that does not conform to the UEFI
specification, e.g. CONFIG_GOOGLE_SMI. Add the necessary code and Kconfig glue
so that it's only possible to select one implementation of EFI variable
operations. This allows us to keep a single (fil
4 matches
Mail list logo