Tuesday, 28 December 2017 , 4:30:51 UTC+6 awokd wrote: > On Wed, December 27, 2017 6:05 pm, Taiidan [at] gmx [dot] com wrote: > > What version of coreboot are you using, they are removing AGESA from the > > latest versions due to some dumb choices by the leadership. > > I'm not sure that's accurate. From the thread on the Coreboot mailing list > a few months ago, it sounded to me like they had been considering it, but > someone did the work necessary to keep them alive. > > And Blooorp, you might want to try that mailing list too if you are still > stuck! Would be more there who'd know about Coreboot specific issues.
The complete "trying-to-kill-AGESA-boards" story: 1) At the end of 2015 some coreboot devs didn't like AGESA and its' "long" compilation times, and because of that + maybe some other personal/financial reasons : they wanted to quietly move AGESA boards from the main coreboot to some separate soon-to-be-abandoned-for-death branch, or even remove it completely! For example: https://mail.coreboot.org/pipermail/coreboot/2015-November/080578.html - "[coreboot] A case for branching AGESA" But, thanks to Vladimir Shipovalov raising the heated discussion threads like this - https://mail.coreboot.org/pipermail/coreboot/2015-November/080637.html - "[coreboot] Removal of AGESA - to be or NOT to be? A story of G505S" - and thanks to the kind developers who supported his side, we all dodged a 'rotting code' bullet ! 2) Second attempt has been made by the Google people, who want to set up the higher standards for coreboot sources - e.g. by removing all the boards which didn't support EARLY_CBMEM_INIT ---> which included AGESA boards like G505S: https://mail.coreboot.org/pipermail/coreboot/2017-May/084255.html - "[coreboot] Platform / Chip removals after upcoming releases" Huge thanks to Kyösti Mälkki and everyone who financially supported his work, he brought that EARLY_CBMEM_INIT feature to many boards and now the majority of AGESA boards - including G505S - are safe again. But we should never relax: Carefully watch the coreboot mailing lists - so that, when a threat of G505S removal appears again - we will be able to address this threat in a timely manner, not just by modifying the source code to fix the "not matching the standard" issues - but also starting the big discussions to show that a huge amount of people TRULY CARE about AGESA boards and wouldn't let a silent removal happen. And, if "introducing a standard" means dropping half of coreboot supported boards, maybe we could argue that this standard shouldn't be introduced? If you can't contribute by source, contribute by your support voice ;) The next potential danger is: * After the 4.8 release, and with every release after that, platforms that have not been updated in the board-status repository within the previous year will be removed You need to learn how to submit a board status, and also re-test coreboot building at least one-two months, so that - if some commit suddenly breaks coreboot - we'll be able to quickly find that commit and do something with that offending code before the other parts of repository started to really depend on it Best regards, Ivan Ivanov -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/18e65624-5fc7-43ae-8934-16625c55ac5b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
