Attention is currently required from: Martin Roth, Felix Held. Julius Werner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/52576 )
Change subject: Documentation: Add suggestion to document flag days ......................................................................
Patch Set 1:
(1 comment)
File Documentation/getting_started/gerrit_guidelines.md:
https://review.coreboot.org/c/coreboot/+/52576/comment/87e7c360_b908dc26 PS1, Line 332: requires a change in all mainboards using it) needs to be documented. I understand what this proposal is trying to get at, but as written this is completely impractical. While initial support for an SoC is added to coreboot (a process that often takes close to a year to fully finish), these changes happen all the time. If we wanted to require something like this we would need to introduce a differentiation between "in-development" SoCs and "stable maintenance-mode" SoCs that we currently do not (officially) have.
Also, to a lesser extent, I think a lot of SoCs in coreboot tend to only have mainboards added by the same party that also develops the SoC code. At least for the majority of Arm(64) SoCs that's true. So I think this would lead to a lot of cases of people writing change documentation that only they themselves care about. I think a lot of work would be saved if there was a list of "SoCs that a larger group of people actually cares about" (maybe that concept could be combined with the list of "stable" SoCs mentioned above... i.e. assume all SoCs are uninteresting by default and once there are enough independent parties interested in one, it can be added to the list of SoCs that need explicit change documentation).