diff options
| author | Mike Waychison <mikew@google.com> | 2011-04-30 02:39:19 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-04-30 03:09:34 +0200 |
| commit | 74c5b31c6618f01079212332b2e5f6c42f2d6307 (patch) | |
| tree | f821278fe44849cb10264031159b01c846c7ed9d /drivers/crypto | |
| parent | x86: Better comments for get_bios_ebda() (diff) | |
| download | linux-74c5b31c6618f01079212332b2e5f6c42f2d6307.tar.xz linux-74c5b31c6618f01079212332b2e5f6c42f2d6307.zip | |
driver: Google EFI SMI
The "gsmi" driver bridges userland with firmware specific routines for
accessing hardware.
Currently, this driver only supports NVRAM and eventlog information.
Deprecated functions have been removed from the driver, though their
op-codes are left in place so that they are not re-used.
This driver works by trampolining into the firmware via the smi_command
outlined in the FADT table. Three protocols are used due to various
limitations over time, but all are included herein.
This driver should only ever load on Google boards, identified by either
a "Google, Inc." board vendor string in DMI, or "GOOGLE" in the OEM
strings of the FADT ACPI table. This logic happens in
gsmi_system_valid().
Signed-off-by: Duncan Laurie <dlaurie@google.com>
Signed-off-by: Aaron Durbin <adurbin@google.com>
Signed-off-by: Mike Waychison <mikew@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/crypto')
0 files changed, 0 insertions, 0 deletions