4 ms·
> I'm talking about the firmware on the motherboard. Then that's what I thought, yeah. I don't see why you're explaining how your idea would be implemented; I
by LoganDark 4y ago
> I'm talking about the firmware on the motherboard.
Then that's what I thought, yeah.
I don't see why you're explaining how your idea would be implemented; I'm rather saying that implementing it in that way might be prohibitive if Intel or AMD still have customers that expect the CPU to act a certain way. And these customers aren't necessarily standard desktop/laptop motherboards.
In other words, changing "what mode the CPU starts in" would be a big and observable breaking change and not necessarily just an implementation detail that can be magically worked around by firmware updates like you describe.
- mjg59 4y agoYou usually can't take existing firmware and run it on a new CPU, because the new CPU requires different bringup code anyway. Take a look at https://github.com/coreboot/coreboot/tree/master/src/soc/intel https://github.com/coreboot/coreboot/tree/master/src/soc/int... to get some idea of how many different implementations there are for modern Intel alone (there's a bunch more for the pre-SoC style Intels). If you already have to port your firmware to a new CPU, you can deal with the CPU starting in a different mode - it is entirely an implementation detail that can be handled in the firmware.