Managing device settings after flashing coreboot

Hi,
Does flashing coreboot/tianocore payload change the settings options
available in the BIOS setup of a device? I'm talking about the
device/hardware config options (e.g. enable/disable Secure Boot,
enable/disable hardware devices etc.) that can be accessed pre-boot by
pressing a dedicated key.  If it does make changes to this, is it
possible to know in advance which options will be available after flashing?

I looked around and couldn't find anything relating to this topic.
Perhaps flashing coreboot doesn't have any effect at all on BIOS setup
options, I'm not sure.

Thanks.

[awokd]

[e-mail]:
> Hi,
> Does flashing coreboot/tianocore payload change the settings options
> available in the BIOS setup of a device? I'm talking about the
> device/hardware config options (e.g. enable/disable Secure Boot,
> enable/disable hardware devices etc.) that can be accessed pre-boot by
> pressing a dedicated key.  If it does make changes to this, is it
> possible to know in advance which options will be available after flashing?

Most of those options are configured only when you build Coreboot. There
are a handful left you can configure if you include the nvramcui payload
that deal with low level things like memory speed, etc. It is difficult
to tell in advance exactly what they will be.

[Patrick Georgi]

Current UEFI based firmware stores its configuration data in the SPI flash
next to the firmware code. Since you're supposed to copy your firmware
image to somewhere safe to have a way to recover, that will also contain
the latest configuration.

Patrick

Am Fr., 6. Sept. 2019 um 09:35 Uhr schrieb :
> Hi,
> Does flashing coreboot/tianocore payload change the settings options
> available in the BIOS setup of a device? I'm talking about the
> device/hardware config options (e.g. enable/disable Secure Boot,
> enable/disable hardware devices etc.) that can be accessed pre-boot by
> pressing a dedicated key.  If it does make changes to this, is it
> possible to know in advance which options will be available after flashing?
>
> I looked around and couldn't find anything relating to this topic.
> Perhaps flashing coreboot doesn't have any effect at all on BIOS setup
> options, I'm not sure.
>
> Thanks.
> _______________________________________________
> coreboot mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

Hi,
So what I'm hearing is: some configuration settings must be hard-coded during compile, and others can be freely configured post-flash using a payload. Is that a fair way to look at it?

September 6, 2019 10:26 AM, "awokd via coreboot"  wrote:
> [e-mail]:
> > Hi,
> > Does flashing coreboot/tianocore payload change the settings options
> > available in the BIOS setup of a device? I'm talking about the
> > device/hardware config options (e.g. enable/disable Secure Boot,
> > enable/disable hardware devices etc.) that can be accessed pre-boot by
> > pressing a dedicated key. If it does make changes to this, is it
> > possible to know in advance which options will be available after flashing?
>
> Most of those options are configured only when you build Coreboot. There
> are a handful left you can configure if you include the nvramcui payload
> that deal with low level things like memory speed, etc. It is difficult
> to tell in advance exactly what they will be.
> _______________________________________________
> coreboot mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

Hi,
You make it sound as if there's no default hardware configuration interface at all. Also, it sounds like all the configuration gets wiped when Coreboot is flashed. So how do I, for example, enable and disable things like the Ethernet port or WLAN card at a firmware level with Coreboot? Is this something that can be freely configured/de-configured after flashing?

September 6, 2019 1:04 PM, "Patrick Georgi via coreboot" <[e-mail] (mailto:[e-mail]?to=%22Patrick%20Georgi%20via%20coreboot%22%20)> wrote:
Current UEFI based firmware stores its configuration data in the SPI flash next to the firmware code. Since you're supposed to copy your firmware image to somewhere safe to have a way to recover, that will also contain the latest configuration.
Patrick 
Am Fr., 6. Sept. 2019 um 09:35 Uhr schrieb <[e-mail] (mailto:[e-mail])>: Hi,
Does flashing coreboot/tianocore payload change the settings options
available in the BIOS setup of a device? I'm talking about the
device/hardware config options (e.g. enable/disable Secure Boot,
enable/disable hardware devices etc.) that can be accessed pre-boot by
pressing a dedicated key. If it does make changes to this, is it
possible to know in advance which options will be available after flashing?

I looked around and couldn't find anything relating to this topic.
Perhaps flashing coreboot doesn't have any effect at all on BIOS setup
options, I'm not sure.

Thanks.
_______________________________________________
coreboot mailing list -- [e-mail] (mailto:[e-mail])
To unsubscribe send an email to [e-mail] (mailto:[e-mail]) 
--Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

[awokd]

[e-mail]:
> Hi,
> So what I'm hearing is: some configuration settings must be hard-coded during compile, and others can be freely configured post-flash using a payload. Is that a fair way to look at it?
>
> September 6, 2019 10:26 AM, "awokd via coreboot"  wrote:
> > [e-mail]:
> > > Hi,
> > > Does flashing coreboot/tianocore payload change the settings options
> > > available in the BIOS setup of a device? I'm talking about the
> > > device/hardware config options (e.g. enable/disable Secure Boot,
> > > enable/disable hardware devices etc.) that can be accessed pre-boot by
> > > pressing a dedicated key. If it does make changes to this, is it
> > > possible to know in advance which options will be available after flashing?
> >
> > Most of those options are configured only when you build Coreboot. There
> > are a handful left you can configure if you include the nvramcui payload
> > that deal with low level things like memory speed, etc. It is difficult
> > to tell in advance exactly what they will be.

Yes, at least that's the case with Seabios payload. I should try out
Tianocore too, maybe it has more options.