Am Mi., 13. Okt. 2021 um 20:51 Uhr schrieb Peter Stuge peter@stuge.se:
Linux is expecting more and more to use EFI supplied interfaces (UEFI Boot Services in particular, even if many are stubbed out) so like it or not, we’re going to need to support these interfaces.
LOL!
The fun part about this segment was that all we could go by was hear-say and unfounded rumors that went around. I attended that meeting but from what I've heard there, no such expectation might actually exist, and it might just have been a weird game of telephone.
This is super embarrassing for Linux and Linux Foundation, but of
course also 100% to be expected. Linux plods along towards absolute uselessness.
Remember that LF is a trade organization (501(c)(6)), not a charitable organization (501(c)(3)). This difference in target audience compared to most open source organizations informs their strategic decisions, and keeping that in mind minimizes surprises and heartburn.
- The coreboot repo will host an EDK2 fork for use as a coreboot payload.
I think the planned tighter integration is a significant first step towards coreboot becoming UEFI.
This isn't about a "tighter" integration: we already have that payload, and we had Tianocore-as-a-payload integration since 2013 (commit cc5b3446624cf85e13a8130a524e81360c5f4239)
It minimizes the time each individual, who for one reason or another works on edk2, needs to spend on edk2. OTOH I haven't found a better way to make developers fervent edk2 opponents than simply showing them the source, so there's that.
- Definitely no one-size fits all solution here
The challenge is great. The coreboot community must be strong and vigilant to not allow coreboot to get locked into EDK2/UEFI like has already happened with vboot. The vboot case arguably hurts coreboot a lot less, but unfortunately all incentives are wrong for quality!
I'm not sure why vboot makes this sudden appearance here.
I don't expect this to go at all well for coreboot, but fingers crossed!
Want peanuts?
Patrick