-
-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modules/coreboot: update rev to Dasharo v.0.7.0 release for RC Talos II #1452
Conversation
The diff between these two commits is literally a change in defconfig, so no actual change in terms of codebse from heads perspective, since heads is maintaining defconfig on it's now. Signed-off-by: Maciej Pijanowski <[email protected]>
I can merge this, but recommended release steps under Dasharo/coreboot#367 should be followed, otherwise SBOM is pretty invalid?
See here: |
… material backup as of now - Closes linuxboot#1452 - coreboot: Take Talos II 0.7 release coreboot config file that was inside of cbfs and use it as a base upstream. - linux: Readd sysctl and proc requirements for cbmem to work. - Adds extFAT requirements that were missing Signed-off-by: Thierry Laurion <[email protected]>
… material backup as of now - Closes linuxboot#1452 - coreboot: Take Talos II 0.7 release coreboot config file that was inside of cbfs and use it as a base upstream. - linux: Readd sysctl and proc requirements for cbmem to work. - Adds extFAT requirements that were missing Signed-off-by: Thierry Laurion <[email protected]>
… material backup as of now (dirmngr is used even if deactivated under gpg2) - Closes linuxboot#1452 - coreboot: Take Talos II 0.7 release coreboot config file that was inside of cbfs and use it as a base upstream. - linux: Readd sysctl and proc requirements for cbmem to work. - Adds extFAT requirements that were missing Signed-off-by: Thierry Laurion <[email protected]>
… material backup as of now TODO: dirmngr is called even if disabled on ppc64 when detach signing (but not built and deactivated per configure script) Will seek help for that, but that would probably mean a gnupg tollstack version bump - Closes linuxboot#1452 - coreboot: Take Talos II 0.7 release coreboot config file that was inside of cbfs and use it as a base upstream. - linux: Readd sysctl and proc requirements for cbmem to work. - Adds extFAT requirements that were missing Signed-off-by: Thierry Laurion <[email protected]>
… material backup as of now - Closes linuxboot#1452 - coreboot: Take Talos II 0.7 release coreboot config file that was inside of cbfs and use it as a base upstream. - linux: Readd sysctl and proc requirements for cbmem to work. - Adds extFAT requirements that were missing TODO: fix gpg2 module so that the following doesn't happen (a ppc64 thing. Can't figure out why): ``` Adding generated key to current firmware and re-flashing... Board talos-2 detected, continuing... 37281653053696daf2e40a8efe9451b557d9d6ab586830dc85f814bf2e03a05f /tmp/talos-2.rom Initializing Flash Programmer Reading old flash contents. Please wait... Flashing: [##################################################\] (100%) Verifying flash contents. Please wait... The flash contents were verified and the image was flashed correctly. Signing boot files and generating checksums... 180726119: 000E452213510000005A gpg: error running '//bin/dirmngr': probably not installed gpg: failed to start dirmngr '//bin/dirmngr': Configuration error gpg: can't connect to the dirmngr: Configuration error gpg: no default secret key: No dirmngr gpg: signing failed: No dirmngr ``` dirmngr is deactivated per configure statement --disable-dirmngr, and works as expected on x86 Signed-off-by: Thierry Laurion <[email protected]>
… material backup as of now - Closes linuxboot#1452 - coreboot: Take Talos II 0.7 release coreboot config file that was inside of cbfs and use it as a base upstream. - linux: Readd sysctl and proc requirements for cbmem to work. - Adds extFAT requirements that were missing TODO: fix gpg2 module so that the following doesn't happen (a ppc64 thing. Can't figure out why): ``` Adding generated key to current firmware and re-flashing... Board talos-2 detected, continuing... 37281653053696daf2e40a8efe9451b557d9d6ab586830dc85f814bf2e03a05f /tmp/talos-2.rom Initializing Flash Programmer Reading old flash contents. Please wait... Flashing: [##################################################\] (100%) Verifying flash contents. Please wait... The flash contents were verified and the image was flashed correctly. Signing boot files and generating checksums... 180726119: 000E452213510000005A gpg: error running '//bin/dirmngr': probably not installed gpg: failed to start dirmngr '//bin/dirmngr': Configuration error gpg: can't connect to the dirmngr: Configuration error gpg: no default secret key: No dirmngr gpg: signing failed: No dirmngr ``` dirmngr is deactivated per configure statement --disable-dirmngr, and works as expected on x86 Signed-off-by: Thierry Laurion <[email protected]>
… material backup as of now - Closes linuxboot#1452 - coreboot: Take Talos II 0.7 release coreboot config file that was inside of cbfs and use it as a base upstream. - linux: Readd sysctl and proc requirements for cbmem to work. TODO: fix gpg2 module so that the following doesn't happen (a ppc64 thing. Can't figure out why): ``` Adding generated key to current firmware and re-flashing... Board talos-2 detected, continuing... 37281653053696daf2e40a8efe9451b557d9d6ab586830dc85f814bf2e03a05f /tmp/talos-2.rom Initializing Flash Programmer Reading old flash contents. Please wait... Flashing: [##################################################\] (100%) Verifying flash contents. Please wait... The flash contents were verified and the image was flashed correctly. Signing boot files and generating checksums... 180726119: 000E452213510000005A gpg: error running '//bin/dirmngr': probably not installed gpg: failed to start dirmngr '//bin/dirmngr': Configuration error gpg: can't connect to the dirmngr: Configuration error gpg: no default secret key: No dirmngr gpg: signing failed: No dirmngr ``` dirmngr is deactivated per configure statement --disable-dirmngr, and works as expected on x86 Signed-off-by: Thierry Laurion <[email protected]>
… material backup as of now - Closes linuxboot#1452 - coreboot: Take Talos II 0.7 release coreboot config file that was inside of cbfs and use it as a base upstream. - linux: Readd sysctl and proc requirements for cbmem to work. TODO: fix gpg2 module so that the following doesn't happen (a ppc64 thing. Can't figure out why): ``` Adding generated key to current firmware and re-flashing... Board talos-2 detected, continuing... 37281653053696daf2e40a8efe9451b557d9d6ab586830dc85f814bf2e03a05f /tmp/talos-2.rom Initializing Flash Programmer Reading old flash contents. Please wait... Flashing: [##################################################\] (100%) Verifying flash contents. Please wait... The flash contents were verified and the image was flashed correctly. Signing boot files and generating checksums... 180726119: 000E452213510000005A gpg: error running '//bin/dirmngr': probably not installed gpg: failed to start dirmngr '//bin/dirmngr': Configuration error gpg: can't connect to the dirmngr: Configuration error gpg: no default secret key: No dirmngr gpg: signing failed: No dirmngr ``` dirmngr is deactivated per configure statement --disable-dirmngr, and works as expected on x86 Signed-off-by: Thierry Laurion <[email protected]>
@macpijan this change of commit was added per #1530. When those changes happen, which are important, they should be communicated otherwise guidelines provided for Heads to actually track those changes. Closing this. |
The diff between these two commits is literally a change in defconfig, so no actual change in terms of codebse from heads perspective, since heads is maintaining defconfig on it's now.