Dear coreboot folks,
Am Mittwoch, den 20.09.2017, 08:17 +0200 schrieb Paul Menzel:
I’d like to propose the following goal for the upcoming coreboot 4.7 release.
All boards have to build with GCC 7.2 [1] and IASL 20170831 [2].
For the latter, several Intel boards fail to build [3]. It’d be great if the maintainers looked into it.
Unfortunately, there was no reply yet. Patrick already blocked the change-set, and commented that it’ll only go in after the coreboot 4.7 release, which is fine. But the boards should still build in my opinion.
The boards below are affected by the IASL update.
``` $ git grep TEVT src/ec/google/chromeec/acpi/ec.asl:External (_SB.DPTF.TEVT, MethodObj) src/ec/google/chromeec/acpi/ec.asl: If (CondRefOf (_SB.DPTF.TEVT)) { src/ec/google/chromeec/acpi/ec.asl: _SB.DPTF.TEVT (Local0) src/mainboard/google/cyan/variants/terra/include/variant/acpi/thermal.asl:Method (TEVT, 1, NotSerialized) src/soc/intel/baytrail/acpi/dptf/thermal.asl:Method (TEVT, 1, NotSerialized) src/soc/intel/braswell/acpi/dptf/thermal.asl:Method (TEVT, 1, NotSerialized) src/soc/intel/common/acpi/dptf/thermal.asl:Method (TEVT, 1, NotSerialized) src/soc/intel/skylake/acpi/dptf/thermal.asl:Method (TEVT, 1, NotSerialized) ```
What is the process for this? Are the maintainers of the board that fail to build subscribed on this mailing list?
Kind regards,
Paul
[1] https://review.coreboot.org/20809/ [2] https://review.coreboot.org/21156/ [3] https://ticket.coreboot.org/issues/138