Announcement

Collapse
No announcement yet.

Windows-DRI Extension Added For X.Org Server 1.19

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows-DRI Extension Added For X.Org Server 1.19

    Phoronix: Windows-DRI Extension Added For X.Org Server 1.19

    In continuation of yesterday's article about Mesa Gets Improved For Running On Windows With Cygwin, the Windows-DRI extension has landed in the X.Org Server code-base...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Can this be used together with the POSIX thing in Windows 10 Anniversary Edition?

    Comment


    • #3
      Originally posted by uid313 View Post
      Can this be used together with the POSIX thing in Windows 10 Anniversary Edition?
      I would imagine it could. Perhaps that's even the motivation for it.

      Comment


      • #4
        opengl version on WSL on windows is 1.1, maybe this can help

        Comment


        • #5
          Originally posted by uid313 View Post
          Can this be used together with the POSIX thing in Windows 10 Anniversary Edition?
          If it's aimed at Cygwin, probably not. Cygwin sits on top of the Win32 subsystem, while WSL is a completely different subsystem and they can't interact AFAIK.

          Comment


          • #6
            Originally posted by adler187 View Post

            If it's aimed at Cygwin, probably not. Cygwin sits on top of the Win32 subsystem, while WSL is a completely different subsystem and they can't interact AFAIK.
            WSL and cygwin are similar and have similar issues. Specifically xorg-server doesnt start on windows 10. So this should probably fix that issue.

            Comment


            • #7
              Originally posted by cj.wijtmans View Post

              WSL and cygwin are similar and have similar issues. Specifically xorg-server doesnt start on windows 10. So this should probably fix that issue.
              Similar? No, they aren't similar.

              WSL is like Wine - it's compatibility layer that translate Linux system calls to NT system calls. You can run Linux binaries with WSL, as well as Windows binaries with Wine.

              Cygwin has nothing to do with Linux. It's library that implements POSIX functions, and which You can use it to compile POSIX applications. You can't run Linux binaries on Cygwin without recompile they from source to Windows binaries. If application use Linux specific functions you can't run it on Windows with Cygwin - because Cygwin isn't Linux 'emulator'.

              WSL and Cygwin are different things. They have only one similarity - You can use they to run POSIX applications on Windows, which You can't do without they, because actually Windows doesn't support POSIX out of the box.

              Comment


              • #8
                Originally posted by s_j_newbury View Post
                I would imagine it could. Perhaps that's even the motivation for it.
                Yup maybe finally a GFX output for Linux executables running under Windows.

                Originally posted by adler187 View Post
                If it's aimed at Cygwin, probably not. Cygwin sits on top of the Win32 subsystem, while WSL is a completely different subsystem and they can't interact AFAIK.
                Not quite exactly:
                - Although there's very little communication between the Win32/Win64 and the WSL worlds, there is still networking which is more or less functionning
                - WSL has *NO* graphical API supported at all.
                - Beinge Win32/Win64 Cygwin has full access to all Windows GFX APIs.

                Thus, the basic use would be :
                - run a Cygwin X Server on your windows box.
                - being Win32/Win64, this server can fully display applications on Windows
                - run "ssh -X" to you WSL box or "DISPLAY=address of the cygwin Xorg"
                - even WSL doesn't have any GUI by itself, it can remotely display on the Xorg server running on regular Windows

                And now thanks to Windows-DRI :
                - accelerated indirect graphics (AIGLX) can now happen. (i.e.: the Linux app under WSL sends its openGL command stream over the network connection)


                Originally posted by dragon321 View Post
                Similar? No, they aren't similar.
                WSL is like Wine - it's compatibility layer that translate Linux system calls to NT system calls. You can run Linux binaries with WSL, as well as Windows binaries with Wine.
                Yes but nope.
                Yes WSL and Cygwin are different. (WSL is an ABI compatibility, Cygwin is an API compatibility)
                Nope WSL isn't exactly like Wine.

                Wine is a separate userland software that has the ability to load and execute Windows .EXE files and does the necessary translation in userland, so said .EXE can run on an OS that has a POSIX-ish API. (e.g.: Linux, Mac OS X, etc.) it does everything by calling into POSIX API. It is limited to what is available in those POSIX APIs (though they aren't much limiting... but it can't do anything which doesn't exist in Linux's API)

                WSL is a different beast:

                WinNT kernel has a peculiarity. It DOES NOT expose it's internal API. Instead it features "Personnalities". A set of API that it exposes and that can be used by the software running on Windows.
                Win32 and Win64 are the APIs that everyone knows.
                But, until the switch to 64-bits OSes, there was also Win16, meaning you could run unmodified Win2.x/Win3.x software.
                At some point in the past, WinNT was also supposed to expose an OS/2 API, meaning to be compatible with OS2 executables.
                Also in the past, Microsoft has provided Unix Service for Windows, meaning some (portions of) POSIX layer was directly available in windows.
                Windows Service for Linux is one of those alternative API/ABI exposed.
                Means that the Windows kernel also a exposes a small subset of the Linux kernel's API/ABI. Meaning you get the bare minimum system calls to get some calculation executable running.
                You miss a lot of Linux API (no containers, extremely limited file-systems, etc.) but at least Windows has gained *NATIVE* capability to run some ELF executables, *whithout needing an extra translation layer*.

                Unlike other translation layers (Wine on Linux, or Cygwin on Windows), WSL has access to some internal of the WinNT kernel that aren't exposed in other sub-systems/API
                e.g.: Windows sucks badly at multi-processing. (It's not copy-on-write, meaning that "fork()"-in a new process is a very expensive operation that needs to duplicate the whole environment/context. That's why multiple threads - i.e. all sharign the same context - are prefered).
                Windows 10 also introduced a new capability in the kernel - pico-threads which, according to microsoft's docs about WSL, are much lighter and thus faster to execute (though they seem to be less good at isolating processes).
                I don't know if these pico-threads are even *exposed* in Win64 (thus Cygwin can't use them yet, and remains stuck to the suck-y multi-processing offered by Win64).
                Still these pico-threads are use to enable multi-processing for WSL software, enabling very fast fork()ing (a tiny bit faster than linux, at the cost of some stability).
                WSL is not limited by what is offered by the Win64 API, WSL *is* an extra API available.

                WSL and Cygwin are different things. They have only one similarity - You can use they to run POSIX applications on Windows, which You can't do without they, because actually Windows doesn't support POSIX out of the box.
                They key word is "anymore". There used to be an API for POSIX available in Windows "out-of-the-box"(-ish).
                WSL is the closest thing to that except it supports an even smaller subset of APIs. But it give the ability to the WinNT kernel to run some Linux software directly without any additionnal layer in user-land.



                Comment

                Working...
                X