Announcement

Collapse
No announcement yet.

DirectX 10/11 Coming Atop Gallium3D

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

  • DirectX 10/11 Coming Atop Gallium3D

    Phoronix: DirectX 10/11 Coming Atop Gallium3D

    With state trackers emerging for the Gallium3D driver architecture to provide acceleration for a range of APIs from OpenGL ES and OpenVG to OpenGL and OpenCL, we knew it was likely that at some point there would be support for Microsoft's DirectX API. There was even a rumor of Tungsten Graphics already having a working DirectX state tracker...

    http://www.phoronix.com/vr.php?view=Nzk2OQ

  • #2
    Boring... vmware+msdonkey=uselessness.

    Comment


    • #3
      Maybe not so boring for the wine developers?

      Comment


      • #4
        It won't help the Wine devs, they still need to support closed source drivers like FGLRX and Nvidia...

        However, looking long term, this is very interesting. If the open source drivers support D3D 10/11 (and I'm sure D3D9 at some point) that means there will be a standardized API for creating a D3D context under X.

        At a guess, I'd say in 2 years time we'll have these state trackers, also by that time nouveau and the open source radeon drivers will be used by people that don't need the extra performance that the closed drivers give, I'd say that was a large majority of people.

        So, if all that happens, DX will gain popularity as a graphics API on Linux, and it would be relatively trivial for ATI/Nvidia to implement the X-D3D API (if as they say they share most of the code with Windows).

        If that happens, Wine won't need their WineD3D layer, as both open and closed drivers would support D3D on Linux. Cool eh

        Comment


        • #5
          Michael, first, i really enjoy the services Phoronix provides me (both news and discussion-wise), and I know that as a non-subscriber leech I can't possibly make any demands, but could you please stop using "atop" in every second sentence? Reading this word is actually making me cringe by now.

          Comment


          • #6
            Hey guys, you don't really believe VMWare will release source code of their D3D state trackers, do you? That would be like saying "come VirtualBox and take some of our market share, you're welcome".

            What Zack says and what will FOSS community get are two entirely different things.

            Comment


            • #7
              Originally posted by Kazade View Post
              So, if all that happens, DX will gain popularity as a graphics API on Linux
              And this is a TERRIBLE TERRIBLE thing that should be avoided at ALL COSTS.

              Comment


              • #8
                Originally posted by droidhacker View Post
                And this is a TERRIBLE TERRIBLE thing that should be avoided at ALL COSTS.
                I agree, but if we get native D3D I think it's quite likely to happen.

                Comment


                • #9
                  The first thing I thought about when I first read about Gallium3D was DirectX and Glide.

                  Any change of a Glide state tracker being usefull? I'd love to play an old Glide game in under Wine

                  Or is this totally unrealistic? In other words; would it work just as much as DirectX does as a state tracker under Wine?

                  Comment


                  • #10
                    Originally posted by droidhacker View Post
                    And this is a TERRIBLE TERRIBLE thing that should be avoided at ALL COSTS.
                    [Throwing oil to the fire]

                    Why? D3D is a pretty nice API.

                    Not to mention that the people who design D3D are mostly the people who design OpenGL (that is, AMD, Nvidia, Intel and the rest).

                    Comment


                    • #11
                      So at least in theory this would mean that someone could write a single driver and ship it for both Linux and Windows (at least when/if earlier versions of Direct3D is supported)?

                      Focusing your resources on a single driver for all platforms could be a big win, at least for companies like Intel, where the Linux driver isn't a port from the Windows side?

                      Comment


                      • #12
                        You forget the other beast that is OSX. It is a supported platform for Wine.

                        Comment


                        • #13
                          Originally posted by whizse View Post
                          So at least in theory this would mean that someone could write a single driver and ship it for both Linux and Windows (at least when/if earlier versions of Direct3D is supported)?

                          Focusing your resources on a single driver for all platforms could be a big win, at least for companies like Intel, where the Linux driver isn't a port from the Windows side?
                          The two drivers could share a significant amount of their code base, but would still need unique code for interacting with Linux/Windows (which is nicely separated as I understand).

                          What is less clear is how well they could protect licensed intellectual property currently embedded in their Windows drivers [which I can see being a concern for them]

                          Comment


                          • #14
                            Originally posted by Kazade
                            So, if all that happens, DX will gain popularity as a graphics API on Linux
                            Originally posted by droidhacker View Post
                            And this is a TERRIBLE TERRIBLE thing that should be avoided at ALL COSTS.
                            Why? I can appreciate that many don't want an API controlled by MS in Linux, but if we look at it from other angles to see if there are opportunities (without turning it into a flame war)

                            1) less code re-write to support multiple platforms for applications originally written to support D3D [ie, lower overhead for games/toolkit developers to target platforms such as Linux.]
                            2) possibly contribute to more momentum (resources) behind Gallium3D to get it ported to more platforms and/or improve the drivers quickly (or take them to a higher state of polish/performance)
                            3) more pressure on OpenGL to continue advance their API to remain competitive
                            4) perhaps an opportunity to move D3D to a consortium

                            Not saying any of this will happen, we don't even know if the D3D state trackers will be open source, but it seems like a more productive response than reacting with fear and panic [which is certainly not productive]

                            Comment


                            • #15
                              Originally posted by Craig73 View Post
                              Why? I can appreciate that many don't want an API controlled by MS in Linux, but if we look at it from other angles to see if there are opportunities (without turning it into a flame war)

                              1) less code re-write to support multiple platforms for applications originally written to support D3D [ie, lower overhead for games/toolkit developers to target platforms such as Linux.]
                              2) possibly contribute to more momentum (resources) behind Gallium3D to get it ported to more platforms and/or improve the drivers quickly (or take them to a higher state of polish/performance)
                              3) more pressure on OpenGL to continue advance their API to remain competitive
                              4) perhaps an opportunity to move D3D to a consortium

                              Not saying any of this will happen, we don't even know if the D3D state trackers will be open source, but it seems like a more productive response than reacting with fear and panic [which is certainly not productive]
                              The only thing that it does is it gives MS more control over Linux by allowing developers to be LAZY.

                              1) This doesn't help -- the developer can make a more intelligent choice in APIs to start their project, resulting in less duplicated work.
                              2) Waste resources in bad areas that could be used in more universally useful areas, like GPU-independent video decode acceleration.
                              3) There would be more pressure on OpenGL to be better if more people were actually interested in it, this goes back to #1.
                              4) Interesting, but when has MS ever relinquished control over anything in favor of open source? In fact, as a counter argument, MS has a tendency to break things that they DO NOT control in THEIR implementation in order to STEAL control.... i.e. their creative interpretation of HTML in their dysfunctional web browser. Because MS renders it WRONGLY, some developers conform to that broken renderer, resulting in web pages that render correctly only when incorrectly rendered by MS.

                              Comment

                              Working...
                              X