somebody_amzn
My guess is that their camera supplier has a secret blob that they want to retain encrypted...
Hello,
Where did you get that from? The drivers for NVIDIA networking cards are in the upstream kernel. You have the option of using newer versions from DKMS if the built-in version for your kernel is too old.
You can see the release notes for each version as present on the upstream kernel at https://docs.mellanox.com/display/kernelupstreamv512/Linux+K... for Linux 5.12 for example.
But with it stuck on IE11...
So instead of including a custom runtime they just bailed out...
If I remember well, only 512KB is actually usable by OEM applications on that platform.
Microsoft didn't bother to fix it. (look at the WPInternals project, through which this is possible)
For the Surface RT, they didn't push firmware updates to fix the bugs allowing to unlock it either.
However, due to specific features of the Arm architecture, it was patchable without a significant performance hit.
(see this section: https://siguza.github.io/KTRR/#meltdownspectre-mitigations-1..., which made the need for actually doing a page table switch avoidable)
(and some newer ones too, rumours say that a TPM might be mandatory to have, finally)
Dumping support for HW and major UX changes without bumping the version number is a bad idea.
On Darwin, x18 is used as a scratch register in context switches on hardware where Meltdown mitigations are needed.
As such, it is cleaned on each ctx switch on that hardware.
On M1, it's currently usable by applications, but that is not part of the ABI contract and might change at any time without notice.
On Windows, x18 is the TEB (thread environment block) register. It must as such _not_ be touched by apps either.
What would be needed though is to have two copies of the system libraries in such a case, targeting different ABIs. That's of course very unlikely to happen.