Bug#947179: linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware drivers

[Salvatore Bonaccorso <carnil@debian.org>]

Hi Tobias,

On Thu, Dec 30, 2021 at 11:50:18PM +0100, Tobias Gruetzmacher wrote:
> Hi,
> 
> On Mon, Dec 13, 2021 at 10:14:22PM +0100, Uwe Kleine-König wrote:
> > > it would be nice if the Debian kernel would provide drivers to interact
> > > with CoreBoot. As far as I can see, those are "hidden" behind
> > > CONFIG_GOOGLE_FIRMWARE ...
> > 
> > The helptext for GOOGLE_FIRMWARE reads:
> > 
> >           These firmware drivers are used by Google's servers.  They are
> >           only useful if you are working directly on one of their
> >           proprietary servers.  If in doubt, say "N".
> 
> Yes, that is a very unfortunate help text...
> 
> > Is this text wrong, or are you working on Google's servers? In case
> > you're not on Google's servers: Did you verify these settings are
> > beneficial on your machine?
> 
> I'm not working on Google servers, but on a "generic" CoreBoot-device. I
> can confirm that when using linux-image-5.16.0-rc7-amd64-unsigned, I can
> load memconsole-coreboot, which in turn gives me access to CoreBoot logs
> in /sys/firmware/log, so the feature is working as intended!
> 
> (As an aside: The file /sys/firmware/log is world-readable after the
> module is loaded, this might leak some information about the hardware to
> users)

Can you report this to upstream?

Regards,
Salvatore