[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5dcf255d.1c69fb81.e4c8b.0c06@mx.google.com>
Date: Fri, 15 Nov 2019 14:23:24 -0800
From: Stephen Boyd <swboyd@...omium.org>
To: linux-kernel@...r.kernel.org, patrick.rudolph@...ements.com
Cc: coreboot@...eboot.org,
Patrick Rudolph <patrick.rudolph@...ements.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Allison Randal <allison@...utok.net>,
Alexios Zavras <alexios.zavras@...el.com>,
Julius Werner <jwerner@...omium.org>,
Samuel Holland <samuel@...lland.org>
Subject: Re: [PATCH 0/2] firmware: google: Expose coreboot tables and CBMEM
Quoting patrick.rudolph@...ements.com (2019-11-15 08:15:14)
> From: Patrick Rudolph <patrick.rudolph@...ements.com>
>
> As user land tools currently use /dev/mem to access coreboot tables and
> CBMEM, provide a better way by using sysfs attributes.
>
> Unconditionally expose all tables and buffers making future changes in
> coreboot possible without modifying a kernel driver.
>
> Patrick Rudolph (2):
> firmware: google: Expose CBMEM over sysfs
> firmware: google: Expose coreboot tables over sysfs
>
> drivers/firmware/google/Kconfig | 6 +
> drivers/firmware/google/Makefile | 1 +
> drivers/firmware/google/cbmem-coreboot.c | 164 +++++++++++++++++++++++
> drivers/firmware/google/coreboot_table.c | 59 ++++++++
> drivers/firmware/google/coreboot_table.h | 13 ++
There should be some Documentation/ABI updates here too so we know how
the sysfs files work.
Powered by blists - more mailing lists