[coreboot] Re: Final calls for S3 suspend support on amdfam10-15
Hello Kyösti, Giving such a "credit" to give a little more time to bring the platform to release requirements sounds like a good idea. 3mdeb will surely approach to implement those changes based on family 14h apu1, as well as for binary PI familty 16h based on apu2 (postcar support already slowly landing to the binaryPI). Although these are AGESA and binaryPI types, will the same approach be applicable here? Best regards, Michał Żygowski On 8/21/19 5:50 AM, Kyösti Mälkki wrote: > On Wed, Aug 21, 2019 at 5:43 AM Matt B wrote: >> Is a lack of C bootblock support common to all family 15h platforms? >> (Including the G505s and any others?) >> In other words, would it only need to be implemented once for all of these >> systems? >> > It's not really a CPU family thing at all, but about the > implementation otherwise. It's one fix for all AGESA, one for all > binaryPI, and a third one for native amdfam10-15. > > My suggestion on moving forwards with amdfam10-15 is as follows: > > The next release is scheduled for Oct 2019 (?). Regardless of when > that happens, I would introduce a flag on the October 1st that > disables all amdfam10-15 boards from the automatic build. Then, if we > have anyone capable and willing to have this amdfam10-15 stay on > master branch, she/he would get to select one mainboard for which the > build would remain enabled. The platform code then needs to go through > the transitions of =>RELOCATABLE_RAMSTAGE, =>POSTCAR_STAGE, > =>C_ENVIRONMENT_BOOTBLOCK. During that process, any remaining #include > <*.c> are to be removed and regressions other amdfam10-15 boards > __are__ allowed and will be ignored as the builds are disabled, Once > the reference platform reaches a state where it fulfills the release > requirements, interested parties can port the necessary changes to > individual motherboards. Providing boot-logs is a necessity. At the > time of next release, boards that don't build will have their source > files removed. > > Regards, > Kyösti Mälkki > ___ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-le...@coreboot.org -- Michał Żygowski Firmware Engineer http://3mdeb.com | @3mdeb_com ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Final calls for S3 suspend support on amdfam10-15
On Wed, Aug 21, 2019 at 5:43 AM Matt B wrote: > > Is a lack of C bootblock support common to all family 15h platforms? > (Including the G505s and any others?) > In other words, would it only need to be implemented once for all of these > systems? > It's not really a CPU family thing at all, but about the implementation otherwise. It's one fix for all AGESA, one for all binaryPI, and a third one for native amdfam10-15. My suggestion on moving forwards with amdfam10-15 is as follows: The next release is scheduled for Oct 2019 (?). Regardless of when that happens, I would introduce a flag on the October 1st that disables all amdfam10-15 boards from the automatic build. Then, if we have anyone capable and willing to have this amdfam10-15 stay on master branch, she/he would get to select one mainboard for which the build would remain enabled. The platform code then needs to go through the transitions of =>RELOCATABLE_RAMSTAGE, =>POSTCAR_STAGE, =>C_ENVIRONMENT_BOOTBLOCK. During that process, any remaining #include <*.c> are to be removed and regressions other amdfam10-15 boards __are__ allowed and will be ignored as the builds are disabled, Once the reference platform reaches a state where it fulfills the release requirements, interested parties can port the necessary changes to individual motherboards. Providing boot-logs is a necessity. At the time of next release, boards that don't build will have their source files removed. Regards, Kyösti Mälkki ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Final calls for S3 suspend support on amdfam10-15
On Wed, Aug 21, 2019 at 5:57 AM Thierry Laurion - Insurgo Technologies Libres / Open Technologies wrote: > > I could provide such resume logs for kgpe-d16. > > How do I produce them? > Cold boot, enter OS, enter S3 suspsnd. Wake up (probably toggle power button, moving mouse or anykey might not do it), then run 'sudo cbmem -1; sudo cbmem -c' after OS resumes and you have commandline. Also 'dmesg' would be nice. Kyösti ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Final calls for S3 suspend support on amdfam10-15
I could provide such resume logs for kgpe-d16. How do I produce them? On August 21, 2019 2:43:44 AM UTC, Matt B wrote: >Is a lack of C bootblock support common to all family 15h platforms? >(Including the G505s and any others?) >In other words, would it only need to be implemented once for all of >these >systems? > >Sincerely, >-Matthew Bradley > >On Thu, Aug 15, 2019 at 11:50 AM Kyösti Mälkki > >wrote: > >> Hi >> >> The decisions are out on 4.11 release requirements. Unless anyone >acts >> on it, amdfam10-15 boards will hit deprecation due to: >> * RELOCATABLE_RAMSTAGE=n >> * CAR_GLOBAL_MIGRATION=y >> * C_ENVIRONMENT_BOOTBLOCK=n >> >> To smooth down the path, should anyone want to attempt on fixing >> these, I have pushed a patchset [1] that removes S3 suspend support >> from said platform. Depending of what the response is, I hope to have >> that submitted already before 4.11 release. >> >> The latest info [2] I have is asus/kcma-d8 not working and >> asus/kgpe-d16 working in 4.6 but very slowly, for S3 resume boot, >that >> is. No resume logs have been brought to my knowledge for 12 months. I >> also had some suspicions that tests results were mistakenly from >> suspend-to-disk (S4). >> >> Affected boards are asus/kcma-d8 and asus/kgpe-d16. >> >> [1] https://review.coreboot.org/c/coreboot/+/15474 >> [2] >https://mail.coreboot.org/pipermail/coreboot/2018-June/086906.html >> >> Kind regards, >> Kyösti >> ___ >> coreboot mailing list -- coreboot@coreboot.org >> To unsubscribe send an email to coreboot-le...@coreboot.org >> -- Sent from /e/ Mail___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Final calls for S3 suspend support on amdfam10-15
Is a lack of C bootblock support common to all family 15h platforms? (Including the G505s and any others?) In other words, would it only need to be implemented once for all of these systems? Sincerely, -Matthew Bradley On Thu, Aug 15, 2019 at 11:50 AM Kyösti Mälkki wrote: > Hi > > The decisions are out on 4.11 release requirements. Unless anyone acts > on it, amdfam10-15 boards will hit deprecation due to: > * RELOCATABLE_RAMSTAGE=n > * CAR_GLOBAL_MIGRATION=y > * C_ENVIRONMENT_BOOTBLOCK=n > > To smooth down the path, should anyone want to attempt on fixing > these, I have pushed a patchset [1] that removes S3 suspend support > from said platform. Depending of what the response is, I hope to have > that submitted already before 4.11 release. > > The latest info [2] I have is asus/kcma-d8 not working and > asus/kgpe-d16 working in 4.6 but very slowly, for S3 resume boot, that > is. No resume logs have been brought to my knowledge for 12 months. I > also had some suspicions that tests results were mistakenly from > suspend-to-disk (S4). > > Affected boards are asus/kcma-d8 and asus/kgpe-d16. > > [1] https://review.coreboot.org/c/coreboot/+/15474 > [2] https://mail.coreboot.org/pipermail/coreboot/2018-June/086906.html > > Kind regards, > Kyösti > ___ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-le...@coreboot.org > ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Deprecate Cavium ThunderX support
Hi folks, Currently there are only 2 boards using Cavium's ThunderX (CN81xx) and both aren't available on the free market. Cavium haven't upstreamed their Arm Trusted Firmware, so it's a bit of maintenance work to keep it alive. If nobody wants to take care of if, it will marked deprecated with he next release (4.11) and removed before the 4.12 release. Regards, Patrick Rudolph 9elements GmbH, Kortumstraße 19-21, 44787 Bochum, Germany Email: patrick.rudo...@9elements.com Phone: +49 234 / 68 94 188 Sitz der Gesellschaft: Bochum Handelsregister: Amtsgericht Bochum, HRB 13207 Geschäftsführung: Eray Basar, Sebastian Deutsch ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
