Date:	Mon, 14 Mar 2011 23:58:39 -0700
From:	Mike Waychison <mikew@...gle.com>
To:	Greg KH <greg@...ah.com>, Matt Domsch <Matt_Domsch@...l.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Duncan Laurie <dlaurie@...gle.com>,
	Aaron Durbin <adurbin@...gle.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, Tim Hockin <thockin@...gle.com>,
	San Mehat <san@...gle.com>
Subject: [PATCH v3 0/5] google firmware support

This patchset applies to v2.6.38-rc8 with the efivars patches (1-7) from
v2 of this series already applied.  It also applies cleanly to gregkh's
driver-core-next branch.

The following series implements some support for interfaces exposed by
google's servers' firmware.  As in the previous send-out, only the gsmi
and memconsole driver are present.  I've dropped the efivars changes as
Greg has already queued them.

In order to address various concerns had with the previous patchset,
I've re-worked the drivers to declare (an admittedly simple)
dmi_device_id structure that only matches "Google, Inc." board vendor id
strings.

As well, I've fixed the gsmi driver up to be able to be built as a
module.  Both drivers also now are disabled by default in the Kconfigs.

I'd like to have these small drivers included as they are required for
proper use of the kernel in our infrastructure.  They may not seem like
much, but a lot of our health automation as well as our human debugging
efforts are dependent on the functionality herein.  Getting these in the
public Linux tree would bring us closer to being able to easily test
kernels as they are released.

Thanks,

Patchset summary
================

Patches [1] and [2] add sanity checking for accessing the EBDA.

Patch [3] introduces CONFIG_GOOGLE_FIRMWARE that is disabled by
default and which gates Google-specific drivers.

Patch [4] adds the "gsmi" driver that we use to make calls into our
firmware.

Patch [5] adds the "memconsole" driver that finds the firmware's logs
and exposes them on /sys/firmware/log.

Diffstat
========
 Documentation/ABI/testing/sysfs-firmware-gsmi |   58 +
 Documentation/ABI/testing/sysfs-firmware-log  |    7 
 arch/x86/include/asm/bios_ebda.h              |   28 
 drivers/firmware/Kconfig                      |    2 
 drivers/firmware/Makefile                     |    2 
 drivers/firmware/google/Kconfig               |   31 
 drivers/firmware/google/Makefile              |    3 
 drivers/firmware/google/gsmi.c                |  941 ++++++++++++++++++++++++++
 drivers/firmware/google/memconsole.c          |  166 ++++
 9 files changed, 1236 insertions(+), 2 deletions(-)

ChangeLog:
==========
- v3
   - Drivers now use dmi_system_id structures to identify matching DMI
     strings, and export these tables via MODULE_DEVICE_TABLE to aid
     autoloading.
   - gsmi can now be compiled as a module.
   - memconsole fixed to require matching DMI strings.
   - efivars patchset dropped from this series as it is now an assumed
     pre-requisite.
- v2
   - Efivars can now be used by other drivers.
   - Documentation added for /sys/firmware/efi/vars
   - Memory console no longer touches log_buf ring buffer.
   - The firmware log is exported to userland as /sys/firmware/log
   - Ioctls for accessing nvram variables in gsmi driver replaced with
     efivars at /sys/firmware/gsmi/vars.
   - die_notifier is used instead of adding new notifer_lists.
   - EBDA scrubbing for memconsole now checks that we aren't walking
     into 0xA0000.
   - Documentation added for /sys/firmware/log
   - Documentation added for /sys/firmware/gsmi
   - Use kernel fixed width types instead of C99 types.
- v1
   - Initial public send-out.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists