Julius Werner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/31766 )
Change subject: Documentation: Explain FMAP and FMD ......................................................................
Patch Set 5:
- What if someday we want multiple sections being write-protected?
The hardware write-protect mechanism doesn't support that anyway.
- For people that wants to use Coreboot but not ChromeOS, they can use whatever names they like, and enable AREA_RO in their process.
I think it would make sense for other coreboot users to follow the example we set in that case. Consistency is good.
Somehow I feel we should remove the logic of hard-coded 'WP_RO' name in CrOS factory, and always looking at AREA_RO flag to decide which section to apply WP. Unfortunately there's too much legacy that we can't drop it.
We could do that if you want to. I don't really think it would be any better than a well-known section name, but it wouldn't be worse. You'd have to change the factory code to follow that and to correctly detect and abort if more than one unoverlapping section is marked like that, though.
But if we're not doing that, I don't think we should advertise an "RO" flag anywhere either. People may think it works and has an effect when it actually doesn't. I'm not saying that we should never have a flag like that, but I don't think we should have it before we actually have code using it.