4 ms·

WSL2 and all these features don't have anything to do with open source either. It's basically a shim for communication of two proprietary bits of software on bo

by SXX 6y ago

WSL2 and all these features don't have anything to do with open source either. It's basically a shim for communication of two proprietary bits of software on both sides. Fortunately all these graphics and compute shims will never get merged into upstream kernel so they'll be second-class citizens like forever. Dave Airlie who is maintainer of Linux graphics subsystem will never allow to merge it since it's can only be used for proprietary software.

mycall 6y ago
Is this the wrong repository for what you are referring to, as this appear open source? https://github.com/microsoft/WSL2-Linux-Kernel https://github.com/microsoft/WSL2-Linux-Kernel
- SXX 6y ago
  This custom kernel only contain shim that needed to pass commands from proprietary component on Linux to proprietary drivers on Windows. When it's come to graphics drivers Linux upstream don't accept any code that can only be used for proprietary components. So all this Direct3D and CUDA shims never gonna be merged.
  - deleted 6y ago
    [deleted]
bzb3 6y ago
It's incredible that people like you are bitter because others are given a choice and they don't choose what you would want them to. And all in the name of freedom, no less.
- SXX 6y ago
  I have no bitterness here, just facts. It's important to understand that none of these WSL features has anything to do with open source. It's exactly your standard "extend" stage. See: proprietary hypervisor runs OS with a patched non-upstreamable Linux kernel and then there is proprietary userspace drivers and libraries that able to talk to their proprietary parts inside Windows. Can any of it be used with different hypervisor? No. Can it be used with open source drivers? Again, nope.
  - bzb3 6y ago
    Of course it could, it's an open API. Others could use it if they wanted to.
    - SXX 6y ago
      If Microsoft or Nvidia wanted to use open APIs they would just support technologies that already exist, e.g there is GPU virtualization with Virgil 3D. There also VirtIO which is standard for all kind of virtualized interfaces, but again Microsoft only interested in using their proprietary tech. Microsoft could also just use Vulkan instead of bringing proprietary Direct3D user pace to Linux. Or might be they could actually open source parts of their stack, but then it's will be against their vendor lock-in.
MikusR 6y ago
So Linux graphics subsystem has only support for MIAOW GPU?
- SXX 6y ago
  The only proprietary part in AMD and Intel graphics stack is GPU firmware. Both companies have few closed-source components that might work on top of the same open-source kernel drivers, but they all have open source alternatives.

by SXX 6y ago

mycall 6y ago

Is this the wrong repository for what you are referring to, as this appear open source? https://github.com/microsoft/WSL2-Linux-Kernel https://github.com/microsoft/WSL2-Linux-Kernel

SXX 6y ago
This custom kernel only contain shim that needed to pass commands from proprietary component on Linux to proprietary drivers on Windows. When it's come to graphics drivers Linux upstream don't accept any code that can only be used for proprietary components. So all this Direct3D and CUDA shims never gonna be merged.
- deleted 6y ago
  [deleted]

bzb3 6y ago

It's incredible that people like you are bitter because others are given a choice and they don't choose what you would want them to. And all in the name of freedom, no less.

SXX 6y ago
I have no bitterness here, just facts. It's important to understand that none of these WSL features has anything to do with open source. It's exactly your standard "extend" stage. See: proprietary hypervisor runs OS with a patched non-upstreamable Linux kernel and then there is proprietary userspace drivers and libraries that able to talk to their proprietary parts inside Windows. Can any of it be used with different hypervisor? No. Can it be used with open source drivers? Again, nope.
- bzb3 6y ago
  Of course it could, it's an open API. Others could use it if they wanted to.
  - SXX 6y ago
    If Microsoft or Nvidia wanted to use open APIs they would just support technologies that already exist, e.g there is GPU virtualization with Virgil 3D. There also VirtIO which is standard for all kind of virtualized interfaces, but again Microsoft only interested in using their proprietary tech. Microsoft could also just use Vulkan instead of bringing proprietary Direct3D user pace to Linux. Or might be they could actually open source parts of their stack, but then it's will be against their vendor lock-in.

MikusR 6y ago

So Linux graphics subsystem has only support for MIAOW GPU?

SXX 6y ago
The only proprietary part in AMD and Intel graphics stack is GPU firmware. Both companies have few closed-source components that might work on top of the same open-source kernel drivers, but they all have open source alternatives.