[PATCH 2/6] efivars: Keep a private global pointer to efivars

2013-04-17 Thread Matt Fleming
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)

Re: [PATCH 2/6] efivars: Keep a private global pointer to efivars

2013-04-11 Thread Matt Fleming
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

Re: [PATCH 2/6] efivars: Keep a private global pointer to efivars

2013-04-09 Thread Mike Waychison
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

[PATCH 2/6] efivars: Keep a private global pointer to efivars

2013-04-04 Thread Matt Fleming
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