Announcement

Collapse
No announcement yet.

OpenGL Overload: Implementing OpenGL Over Vulkan

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

  • OpenGL Overload: Implementing OpenGL Over Vulkan

    Phoronix: OpenGL Overload: Implementing OpenGL Over Vulkan

    While some have long talked about trying to implement OpenGL over Vulkan drivers, we're finally seeing real work in this direction with the "OpenGL Overload" project...

    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
    Sounds nice, but its not easier to port Mesa3D? A Vulkan Backend like Gallium3D .

    Comment


    • #3
      Originally posted by Nille View Post
      Sounds nice, but its not easier to port Mesa3D? A Vulkan Backend like Gallium3D .
      It's obviously intended to be used by more than linux on AMD/intel

      Comment


      • #4
        G-truc being behind it is very good news.

        Comment


        • #5
          Originally posted by Nille View Post
          Sounds nice, but its not easier to port Mesa3D? A Vulkan Backend like Gallium3D .
          I'm thinking of the same thing, but maybe the developer thinks it's easier to start from scratch instead of understanding the mesa code base.

          Comment


          • #6
            Originally posted by zxy_thf View Post

            I'm thinking of the same thing, but maybe the developer thinks it's easier to start from scratch instead of understanding the mesa code base.
            As was mentioned earlier, this will theoretically be targeted at multiple back-ends as well. So you might be able to use this to eventually run higher GL levels on Macs using the Metal back-end (since they don't support Vulkan yet). It's an interesting idea, at least, and may make it easier for the driver developers to shift from having to implement both GL and Vulkan to just supporting Vulkan at some point in the future (which could be less intensive in development hours for them).

            Comment


            • #7
              Why? What's the point? Why not just use OpenGL normally?

              Comment


              • #8
                Originally posted by rabcor View Post
                Why? What's the point? Why not just use OpenGL normally?
                'cause its much easier to write a usable Vulkan driver, than to write something that works well, for OpenGL.

                Comment


                • #9
                  I'm slightly confused about what this actually does. Is this basically just a compatibility layer so you can, for example, run a Vulkan application using a GPU that only supports OpenGL?

                  Comment


                  • #10
                    Originally posted by peppercats View Post
                    It's obviously intended to be used by more than linux on AMD/intel
                    Why should it limited to only 2 Vendors? Vulkan, D3D12 and Metal are Hardware Independet. So if Mesa3D can use this APIs as a Backend, why should it then Limited to Intel/AMD?

                    And you can use Mesa on more Systems as Linux.

                    Comment

                    Working...
                    X