Announcement

Collapse
No announcement yet.

Wine-Staging 1.7.36 Has Threadpool, CUDA 7, NVENC

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

  • Wine-Staging 1.7.36 Has Threadpool, CUDA 7, NVENC

    Phoronix: Wine-Staging 1.7.36 Has Threadpool, CUDA 7, NVENC

    With Wine 1.7.36 having been released on Friday, the Wine-Staging crew released their respective updated version of Wine patched with experimental features...

    http://www.phoronix.com/scan.php?pag...ng-CUDA7-NVENC

  • #2
    mmm i do understand that nVidia is quite good for gaming and it has better catch up speed with changes than AMD BLOB but i'm starting to dislike their policy to reject Gallium integration because is "linux specific" when they basically are integrating every nVidia only Linux specific non compatible with anything else in the world in wine.

    so it seems to me, you can integrate anything you want in Wine as long is for nVidia BLOB, doesn't matter how specific it is, i mean is their project and they can do whatever the hell they want but there is no need to have this shameless double standards, the community will take better( i think) a clear answer like "We only support nVidia", at least this way you are clear of what to expect.

    Comment


    • #3
      Originally posted by jrch2k8 View Post
      mmm i do understand that nVidia is quite good for gaming and it has better catch up speed with changes than AMD BLOB but i'm starting to dislike their policy to reject Gallium integration because is "linux specific" when they basically are integrating every nVidia only Linux specific non compatible with anything else in the world in wine.

      so it seems to me, you can integrate anything you want in Wine as long is for nVidia BLOB, doesn't matter how specific it is, i mean is their project and they can do whatever the hell they want but there is no need to have this shameless double standards, the community will take better( i think) a clear answer like "We only support nVidia", at least this way you are clear of what to expect.
      Wine devs not have any interest in gallium because as your said is not supported other supported systems and other reason maybe could be gallium users are very few compared to wine users in all wine supported systems without forget them dont have any interest in support double dx9 implementation

      However gallium could have other options like make fork (this is good idea because wine development go in other direction) or improve actual opengl in gallium (however this must be improve with or without wine, if this improve native games improve)

      Comment


      • #4
        mmm i do understand that nVidia is quite good for gaming and it has better catch up speed with changes than AMD BLOB but i'm starting to dislike their policy to reject Gallium integration because is "linux specific" when they basically are integrating every nVidia only Linux specific non compatible with anything else in the world in wine.

        so it seems to me, you can integrate anything you want in Wine as long is for nVidia BLOB, doesn't matter how specific it is, i mean is their project and they can do whatever the hell they want but there is no need to have this shameless double standards, the community will take better( i think) a clear answer like "We only support nVidia", at least this way you are clear of what to expect.
        Nvidia drivers exist on FreeBSD and macOSX too, do we actually have gallium nine to mac osx?, this is just a dll export and dont change much lines of code in wine actually, but the patches to make wine gallium3d compatible is kinda more abusive on LOC size
        nine can coexist with wine, but it will make a lot of duplicated code and it wont be supported on non mesa systems. (just trashing manpower for a little bit more of performance on some cases)

        for me, it's a waste of time keep 2 d3d9 implementation but it's worse to remove macOSX support (or making the code less simpler.)
        but this is a matter of opinion

        Comment


        • #5
          Originally posted by pinguinpc View Post
          Wine devs not have any interest in gallium because as your said is not supported other supported systems and other reason maybe could be gallium users are very few compared to wine users in all wine supported systems without forget them dont have any interest in support double dx9 implementation

          However gallium could have other options like make fork (this is good idea because wine development go in other direction) or improve actual opengl in gallium (however this must be improve with or without wine, if this improve native games improve)

          I am from the Wine Staging team and I would like to comment on that. First of all, "Wine Staging" is not identical to "Wine". We have different maintainers, and also use different rules to decide what can go in and what not. Upstream Wine rejected the inclusion of Gallium 3D (and also didn't seem to have any interest to include CUDA support in the past for example), but Wine Staging will happily accept a cleaned up patchset to add this feature. When it is useful for at least a couple of people and is actively maintained, we have no problem with adding it to our version, even if it probably will never get upstream.

          The main reason why Gallium Nine is not added yet is because the corresponding Wine code is still very "hacky". I know that this argument is difficult understand from a user perspective, especially when it already works pretty well. But for our Wine Staging tree it is also very important that the code quality is at least so good, that in theory other unrelated people can understand and improve it. It doesn't make sense to add it for example, when the interface between Wine and Mesa could basically change at any time. For interested people, the bug report on wine-staging.com contains more information about the remaining TODOs: https://bugs.wine-staging.com/show_bug.cgi?id=40#c3

          Regards,
          Sebastian

          Comment


          • #6
            Originally posted by pinguinpc View Post
            Wine devs not have any interest in gallium because as your said is not supported other supported systems and other reason maybe could be gallium users are very few compared to wine users in all wine supported systems without forget them dont have any interest in support double dx9 implementation
            Does Mac have support for CUDA?

            Comment


            • #7
              Does Mac have support for CUDA?
              Yes, it has.
              http://docs.nvidia.com/cuda/cuda-get...-for-mac-os-x/

              Comment


              • #8
                Originally posted by pinguinpc View Post
                Wine devs not have any interest in gallium because as your said is not supported other supported systems and other reason maybe could be gallium users are very few compared to wine users in all wine supported systems without forget them dont have any interest in support double dx9 implementation
                The gallium faction won another user: me.
                Catalyst+wine performance was really bad, now i play with d3dstream.
                My favorite steam games work very well, too.

                Meanwhile catalyst is stuck at 14.12 which had a severe performance drop for me (especially with wine).
                Interstellar Marines was unplayable with catalyst. Works fine with gallium.
                Propably it is true, wine's bad performance with MESA/opengl and catalyst is not wine's fault but recently emerged wine-modifications (wine-csmt/wine-staging, wine-d3dstream) do show a strong desire for better wine performance not only for not-nvidia fans.

                By the way: 25000 lines only for d3dstream may sound impressive but honestly: How much effort can it be to maintain code which just wraps native d3d9 API?

                Comment


                • #9
                  Originally posted by Uramekus View Post
                  Nvidia drivers exist on FreeBSD and macOSX too, do we actually have gallium nine to mac osx?, this is just a dll export and dont change much lines of code in wine actually, but the patches to make wine gallium3d compatible is kinda more abusive on LOC size
                  nine can coexist with wine, but it will make a lot of duplicated code and it wont be supported on non mesa systems. (just trashing manpower for a little bit more of performance on some cases)

                  for me, it's a waste of time keep 2 d3d9 implementation but it's worse to remove macOSX support (or making the code less simpler.)
                  but this is a matter of opinion
                  I definitely think you 're looking at it from a twisted veiwpoint. Gallium Nine patchset for wine is just a wrapper for the native d3d9 implementation in nine. Where wines own d3d9 implementation is a translation from d3d9 to highly nvidia specific opengl. The only way wine will ever perform well on gallium is if nvidia decided to rewrite galliums opengl implementation, and that ain't gonna happen.

                  The only people at fault for wines terrible performance is wine. If they would get off their non-nvidia phobia, and implement functions that work according to specs, the whole thing would work better. As long as they continue translating d3d9 into opengl functions that only work on nvidia hardware, then wine will continue to be broken on non-nvidia hardware. That is entirely wines fault.

                  Comment


                  • #10
                    Originally posted by duby229 View Post
                    I definitely think you 're looking at it from a twisted veiwpoint. Gallium Nine patchset for wine is just a wrapper for the native d3d9 implementation in nine. Where wines own d3d9 implementation is a translation from d3d9 to highly nvidia specific opengl. The only way wine will ever perform well on gallium is if nvidia decided to rewrite galliums opengl implementation, and that ain't gonna happen.

                    The only people at fault for wines terrible performance is wine. If they would get off their non-nvidia phobia, and implement functions that work according to specs, the whole thing would work better. As long as they continue translating d3d9 into opengl functions that only work on nvidia hardware, then wine will continue to be broken on non-nvidia hardware. That is entirely wines fault.
                    I fully agree with you and I think that nine would be a good start to support something different from nvidia not only in words.
                    Gallium-nine is very close to the win8 catalyst performance, and even more effective than the win8 if used a slow processor(csmt lags very much without 4-8 cores 3 Ghz processor)
                    My test
                    CPU Core & frequency scaling: Wine(nine|csmt) vs Windows 8
                    Linux gallium-nine vs Windows 8.1 catalyst
                    The Talos Principle linux wine|nine vs windows

                    Comment

                    Working...
                    X