2019-11-20 13:49:27

by Patrick Rudolph

[permalink] [raw]
Subject: [PATCH 0/2] firmware: google: Expose coreboot tables and CBMEM

From: Patrick Rudolph <[email protected]>

As user land tools currently use /dev/mem to access coreboot tables and
CBMEM, provide a better way by using read-only sysfs attributes.

Unconditionally expose all tables and buffers making future changes in
coreboot possible without modifying a kernel driver.

Changes in v2:
- Add ABI documentation
- Add 0x prefix on hex values
- Remove wrong ioremap hint as found by CI

Patrick Rudolph (2):
firmware: google: Expose CBMEM over sysfs
firmware: google: Expose coreboot tables over sysfs

Documentation/ABI/stable/sysfs-bus-coreboot | 73 +++++++++
drivers/firmware/google/Kconfig | 9 ++
drivers/firmware/google/Makefile | 1 +
drivers/firmware/google/cbmem-coreboot.c | 162 ++++++++++++++++++++
drivers/firmware/google/coreboot_table.c | 60 ++++++++
drivers/firmware/google/coreboot_table.h | 13 ++
6 files changed, 318 insertions(+)
create mode 100644 Documentation/ABI/stable/sysfs-bus-coreboot
create mode 100644 drivers/firmware/google/cbmem-coreboot.c

--
2.21.0



2019-11-20 15:46:58

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 0/2] firmware: google: Expose coreboot tables and CBMEM

On Wed, Nov 20, 2019 at 02:39:45PM +0100, [email protected] wrote:
> From: Patrick Rudolph <[email protected]>
>
> As user land tools currently use /dev/mem to access coreboot tables and
> CBMEM, provide a better way by using read-only sysfs attributes.
>
> Unconditionally expose all tables and buffers making future changes in
> coreboot possible without modifying a kernel driver.
>
> Changes in v2:
> - Add ABI documentation
> - Add 0x prefix on hex values
> - Remove wrong ioremap hint as found by CI

I think you forgot to put "v2" in the [PATCH] area of the subject lines
:(

thanks,

greg k-h