Change in coreboot[master]: drivers/fsp2_0: drop support for FSP-T

[Michael Niewöhner (Code Review)]

Michael Niewöhner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/36622 )

Change subject: drivers/fsp2_0: drop support for FSP-T
......................................................................

Patch Set 4:
> So, I think that getting CB:36682 boot-tested and merged in will be good for everyone. If so, what are we waiting for?

Even though I'm sure this is meant rhetorical, let me answer that question: We are waiting for Intel to a) test the CB or b) provide a way for us to test it.
> Since Bootguard requires firmware to be signed, and the signing key is kept secret, running a random coreboot image on a commercially available board with Bootguard is just not possible.

It's not impossible, as there are unfused boards available. I have one for example. The problem is, there is no way for non-Intel-NDAed people to get access to the required manifest generation tool....

Nico mentioned this discussion came up a year ago. Some people complained (just like this time) but could not bring up valid arguments to keep FSP-T. My feeling is they try to sit that out. My suggestion? Let's agree on a deadline (like Arthur already suggested). Then merge it. When there was no BG testing and nor reaction? Bad luck. They had a chance.