Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #73940 > unrolled thread

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

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#947179: linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware drivers Uwe Kleine-König <u.kleine-koenig@pengutronix.de> - 2021-12-13 22:50 +0100
    Bug#947179: linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware drivers Tobias Gruetzmacher <tobias@23.gs> - 2021-12-31 00:00 +0100
      Bug#947179: linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware drivers Salvatore Bonaccorso <carnil@debian.org> - 2021-12-31 12:00 +0100

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

[Multipart message — attachments visible in raw view] — view raw

Hello Tobias,

On Sun, Dec 22, 2019 at 04:45:12PM +0100, Tobias Gruetzmacher wrote:
> Package: src:linux
> Version: 5.3.15-1
> Severity: wishlist
> 
> 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 ...
> 
> These seem to be all available as modules, so it won't hurt to switch
> them on, right? (If I understand drivers/firmware/google/Makefile
> correctly)
> 
> For reference:
> 
> CONFIG_GOOGLE_FIRMWARE=y
> CONFIG_GOOGLE_SMI=m
> CONFIG_GOOGLE_COREBOOT_TABLE=m
> CONFIG_GOOGLE_MEMCONSOLE=m
> CONFIG_GOOGLE_MEMCONSOLE_X86_LEGACY=m
> CONFIG_GOOGLE_FRAMEBUFFER_COREBOOT=m
> CONFIG_GOOGLE_MEMCONSOLE_COREBOOT=m
> CONFIG_GOOGLE_VPD=m

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".

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?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[toc] | [next] | [standalone]

#74083

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)

Regards, Tobias

[toc] | [prev] | [next] | [standalone]

#74086

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web