4 ms·
Even if you were to overcome the massive hurdle of porting a driver between two completely different kernel architectures, you would not be able to load it with
by fluoridation 3y ago
Even if you were to overcome the massive hurdle of porting a driver between two completely different kernel architectures, you would not be able to load it without enabling driver testing mode at boot time, or without buying a code signing certificate.
- yomlica8 3y agoIts the wrong priority anyway. Windows is utterly infested with far worse telemetry at this point so it would be like fixing pinhole hull leaks in the titanic after the ship had snapped in half.
- fluoridation 3y agoSomeone might be comfortable with Microsoft telemetry but not with Intel telemetry. That's not wrong. Weird, sure, but not wrong.
- JohnFen 3y ago> Even if you were to overcome the massive hurdle of porting a driver between two completely different kernel architectures Hmm, would that be a massive hurdle? I haven't looked at that driver code, but I have done a lot of driver development for both Windows and Linux, and have ported a number of drivers between the two. Sight unseen, it's not obvious to me that this would be a huge hurdle. The code signing is an issue, but that's a manageable one.
- fluoridation 3y agoI can't imagine it's easy, but if you say you've done it I'll have to defer to you.
- JohnFen 3y agoDon't defer to me. As I said, I've not looked at the code, so I don't actually know. I'm speculating based on my experience with other drivers.