3 ms·
Two groups in L4 family used driver VM's that had just enough of Linux to use the drivers. Depending on compatibility vs isolation, you could put your driver-de
by nickpsecurity 9y ago
Two groups in L4 family used driver VM's that had just enough of Linux to use the drivers. Depending on compatibility vs isolation, you could put your driver-dependent code in that VM, use it via a virtual driver from another partition, or use a native driver on microkernel. I believe OK Labs used that mix for their OKL4 platform for mobile virtualization. It got deployed in what they said was a billion phones mainly for baseband isolation.
So, it's doable. There was also a project a long time ago that combined virtualization with Windows to use its drivers. Stuff like that seems best solution for now where we can incrementally build native drivers over time. At least until cross-platform synthesis is built and takes off. ;)
- sanxiyn 9y agoThere's also NDISWrapper which lets you use Windows drivers on Linux.
- AnIdiotOnTheNet 9y agoOnly WindowsXP network drivers, which makes it pretty well useless nowadays.
- snvzz 9y agoA wrapper around Netbsd's RUMP kernels would be my first choice for a transition solution.