I was in the non-profit shop of a local charity. They accept donations of used computers then resell them to the public. The profit goes to charity. I asked for their oldest machine. It had an AMD chip from the 16h family. Thus, a spychip.
So their oldest machine was still too new for me. I asked why don’t you have anything older? They said the general public would not accept anything older, and so the shop also does not accept anything older. When machines are rejected, they go to a factory that destroys them and recovers the raw metals.
It’s sad to see that pre-spychip machines are being destroyed and that even 2nd-hand customers are being limited to anti-consumer spychip hardware.
What’s being dismissed is irrelevant facts. You continue (for a 3rd time) to still fail to grasp the fact that Meltdown was not found to affect AMD chips. It’s wholly irrelevant.
Those are two different things. There was a firmware patch. And separately there was a kernel mitigation. You don’t need both.
You mean AMD’s f/w patch was not made. Yet you’ve been told about the 15h.org project. If you absorbed that, then citation needed that Coreboot fails to mitigate. In the absence of Coreboot, the os mitigation was implemented in linux. So you’re pushing a bullshit problem.
I’m aware of coreboot. I was not aware that the project managed to increase support to include configurations for all chips that predate IME and PSP. Last I recall when I looked at coreboot, there were chips that they didn’t think could ever be supported, even without nannyware. I wasn’t pushing a bullshit problem, I was raising legitimate concerns for problems that I didn’t know had solutions. If you don’t want people to raise honest, good faith concerns to you then you better be extremely vigilant that you don’t step in shit.