Planning coreboot 4.11
Hi everybody, I'm planning to release coreboot 4.11 two weeks from today, Nov 18th. As usual, it's a snapshot release, not aligned with any specific feature or development. coreboot releases exist to provide synchronization points with downstream projects, and simply to keep version numbers (which we derive automatically from git history) meaningful: coreboot-4.0-26987 provides less information at a glance (e.g. about the approximate year it's from) than coreboot-4.10-1355. We'll also use it as an opportunity to remove[0] a number of unmaintained platforms, MIPS and AMD Fam12h, directly after the release. Finally the releases give us the opportunity to issue a call for testing, encouraging folks to test the hardware they have at least twice every year on latest master. Of course, don't test random master revisions if you don't have the means to recover from a bad flash! So here's how you can help (I'll do the same, but the more, the merrier): - Test current master branch on the hardware you have around to make sure it's looking reasonable. - Ideally, prepare for testing in the days before the release when things have settled a bit, and report a recent status to the list, IRC or to me directly, so I don't pick a dud as release revision. - Fix issues you notice, or at least report them (the mailing list is a fine place for such reports) - Report the test results to the board-status repository (using the tools in util/board_status/) - Fill in any notable developments since 4.10 in Documentation/releases/coreboot-4.11-relnotes.md - Maybe wait with merging riskier changes until after the release Thanks, Patrick [0] https://review.coreboot.org/c/coreboot/+/34919 for MIPS, https://review.coreboot.org/c/coreboot/+/36187 for AMD Fam12h -- 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
Thank you, I've sent the reports for Lenovo G505S (AMD Fam15h) and ASUS AM1I-A (AMD Fam16h). Hope this helps, especially AM1I-A since its' previous report was from early 2018. Best regards, Mike Banon On Mon, Nov 4, 2019 at 5:31 PM Patrick Georgi via coreboot <coreboot@coreboot.org> wrote:
Hi everybody,
I'm planning to release coreboot 4.11 two weeks from today, Nov 18th.
As usual, it's a snapshot release, not aligned with any specific feature or development. coreboot releases exist to provide synchronization points with downstream projects, and simply to keep version numbers (which we derive automatically from git history) meaningful: coreboot-4.0-26987 provides less information at a glance (e.g. about the approximate year it's from) than coreboot-4.10-1355.
We'll also use it as an opportunity to remove[0] a number of unmaintained platforms, MIPS and AMD Fam12h, directly after the release.
Finally the releases give us the opportunity to issue a call for testing, encouraging folks to test the hardware they have at least twice every year on latest master.
Of course, don't test random master revisions if you don't have the means to recover from a bad flash!
So here's how you can help (I'll do the same, but the more, the merrier):
- Test current master branch on the hardware you have around to make sure it's looking reasonable.
- Ideally, prepare for testing in the days before the release when things have settled a bit, and report a recent status to the list, IRC or to me directly, so I don't pick a dud as release revision.
- Fix issues you notice, or at least report them (the mailing list is a fine place for such reports)
- Report the test results to the board-status repository (using the tools in util/board_status/)
- Fill in any notable developments since 4.10 in Documentation/releases/coreboot-4.11-relnotes.md
- Maybe wait with merging riskier changes until after the release
Thanks, Patrick
[0] https://review.coreboot.org/c/coreboot/+/34919 for MIPS, https://review.coreboot.org/c/coreboot/+/36187 for AMD Fam12h -- 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 _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
On Sun, Nov 10, 2019 at 12:35 PM Mike Banon <mikebdp2@gmail.com> wrote:
Thank you, I've sent the reports for Lenovo G505S (AMD Fam15h) and ASUS AM1I-A (AMD Fam16h). Hope this helps, especially AM1I-A since its' previous report was from early 2018.
I do not plan to volunteer for C_ENVIRONMENT_BOOTBLOCK=y conversion for AGESA/PI platforms, so it is currently uncertain if some or any of them will remain on master branch after 4.11 release. Kyösti
On 10.11.2019 17:13, Kyösti Mälkki wrote:
On Sun, Nov 10, 2019 at 12:35 PM Mike Banon <mikebdp2@gmail.com> wrote:
Thank you, I've sent the reports for Lenovo G505S (AMD Fam15h) and ASUS AM1I-A (AMD Fam16h). Hope this helps, especially AM1I-A since its' previous report was from early 2018.
I do not plan to volunteer for C_ENVIRONMENT_BOOTBLOCK=y conversion for AGESA/PI platforms, so it is currently uncertain if some or any of them will remain on master branch after 4.11 release. I will soon update my patches with C_ENVIRONMENT_BOOTBLOCK for binaryPI which will be rebased on top of postcar patches (easier for CAR teardown).
Kyösti I would appreciate if you could look at https://review.coreboot.org/c/coreboot/+/32363 Nobody tells you to volunteer, but review very welcome, since nobody seems to be interested to even take look at it. Michał
Kyösti _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
-- Michał Żygowski Firmware Engineer http://3mdeb.com | @3mdeb_com
On Tue, Nov 12, 2019 at 12:07 PM Michal Zygowski <michal.zygowski@3mdeb.com> wrote:
On 10.11.2019 17:13, Kyösti Mälkki wrote:
On Sun, Nov 10, 2019 at 12:35 PM Mike Banon <mikebdp2@gmail.com> wrote:
Thank you, I've sent the reports for Lenovo G505S (AMD Fam15h) and ASUS AM1I-A (AMD Fam16h). Hope this helps, especially AM1I-A since its' previous report was from early 2018.
I do not plan to volunteer for C_ENVIRONMENT_BOOTBLOCK=y conversion for AGESA/PI platforms, so it is currently uncertain if some or any of them will remain on master branch after 4.11 release. I will soon update my patches with C_ENVIRONMENT_BOOTBLOCK for binaryPI which will be rebased on top of postcar patches (easier for CAR teardown).
Kyösti I would appreciate if you could look at https://review.coreboot.org/c/coreboot/+/32363 Nobody tells you to volunteer, but review very welcome, since nobody seems to be interested to even take look at it.
At the moment there is too much bad blood for me to touch anything remotely related to AGESA, you have seen some of the private email exchange. And most notably, the lack of response. Looks like when AMD is not stabbing you in the back, they are shooting themselves in the leg instead. Kyösti
Michal Zygowski:
I will soon update my patches with C_ENVIRONMENT_BOOTBLOCK for binaryPI which will be rebased on top of postcar patches (easier for CAR teardown).
Does https://review.coreboot.org/c/coreboot/+/36914 also address C_ENVIRONMENT_BOOTBLOCK for classic AGESA? Besides Coverity issues, is that the only objection to keeping them in the tree? Thanks for your work on this; I can test on a Fam15h if it helps. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots
On 20.11.2019 16:38, awokd via coreboot wrote:
Michal Zygowski:
I will soon update my patches with C_ENVIRONMENT_BOOTBLOCK for binaryPI which will be rebased on top of postcar patches (easier for CAR teardown). Does https://review.coreboot.org/c/coreboot/+/36914 also address C_ENVIRONMENT_BOOTBLOCK for classic AGESA? Besides Coverity issues, is that the only objection to keeping them in the tree? Thanks for your work on this; I can test on a Fam15h if it helps.
Got C bootblock working on apu2 (fam16h) just few moments ago. Aiming to cover all possible families (fam14h-fam16h) both AGESA and binaryPI. Will need testing for mainboards. have binaryPI fam16h (apu2) and AGESA fam14h (apu1) at hand, so these will be tested and robust. However I will need some testing for other families. Your help will be appreciated. I will also announce the ready patches on mailing list when I finish the work and call for testing the mainboards. -- Michał Żygowski Firmware Engineer http://3mdeb.com | @3mdeb_com
On Mon, Nov 04, 2019 at 09:30:34AM -0500, Patrick Georgi wrote:
I'm planning to release coreboot 4.11 two weeks from today, Nov 18th. This has been deferred to tomorrow, Nov 19th.
My basic functionality tests with current master are looking good, but there are two issues for which I'm trying to get fixes in. While we don't guarantee anything for our releases, experience shows that people use them nonetheless as golden master, so let's get the tree as stable as possible before tagging. To reiterate, 4.11 will be master as of now + a few commits that are yet to land. I'd appreciate if we could keep the tree stable for the next 20-ish hours :-)
- Fill in any notable developments since 4.10 in Documentation/releases/coreboot-4.11-relnotes.md This call to action worked really well. Thanks everybody for filling in various blanks.
Patrick -- 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
participants (5)
-
awokd -
Kyösti Mälkki -
Michal Zygowski -
Mike Banon -
Patrick Georgi