[coreboot] Can we get rid of SMMSTORE_IN_CBFS?

As I'm trying to port all existing CBFS uses to the new APIs that support verification, the CONFIG_SMMSTORE_IN_CBFS option is a bit of a problem: It's the only CBFS use case where coreboot is actually trying to write back into CBFS, and thus needs access to the raw flash offsets of files (which is

[coreboot] Re: Can we get rid of SMMSTORE_IN_CBFS?

Am Mi., 14. Apr. 2021 um 04:06 Uhr schrieb Julius Werner : > Does anyone still need this? As far as I know it was just a hack > invented to backport SMMSTORE onto a Chromebook that couldn't make > FMAP changes anymore, and we never ended up using it after all. Anyone > still using SMMSTORE today s

[coreboot] Re: Can we get rid of SMMSTORE_IN_CBFS?

On Wed, Apr 14, 2021 at 6:49 AM Julius Werner via coreboot wrote: > > As I'm trying to port all existing CBFS uses to the new APIs that > support verification, the CONFIG_SMMSTORE_IN_CBFS option is a bit of a > problem: It's the only CBFS use case where coreboot is actually trying > to write back

[coreboot] Chrome OS altfw questions (was: Can we get rid of SMMSTORE_IN_CBFS?)

> Unrelated -- who can I talk to about fixing the state of launching > something other than u-boot from the Alternative Bootloader Menu? > Tianocore has only ever worked on a handful of devices, and the lack > of console output on release firmware makes it difficult to debug. I can try answering t

[coreboot] Re: Chrome OS altfw questions (was: Can we get rid of SMMSTORE_IN_CBFS?)

I don't have much more to add. We do want to continue supporting the alternative bootloader feature on Chrome OS devices to make it easy for folks to use their own bootloaders/OSes. However, maintaining a set of alternative bootloaders is currently out of our product scope. Thanks, Dossym On Wed

[coreboot] Re: Chrome OS altfw questions (was: Can we get rid of SMMSTORE_IN_CBFS?)

The issue is that Tianocore fails to execute (hangs the system) when used as a legacy boot/alternative bootloader entry on 90% of CrOS devices which support the alternative bootloader feature, and since coreboot disables console output via the CPU UART, I don't have a good way to debug the issue (i

[coreboot] Re: Chrome OS altfw questions (was: Can we get rid of SMMSTORE_IN_CBFS?)

> The issue is that Tianocore fails to execute (hangs the system) when > used as a legacy boot/alternative bootloader entry on 90% of CrOS > devices which support the alternative bootloader feature, and since > coreboot disables console output via the CPU UART, I don't have a good > way to debug th