Announcement

Collapse
No announcement yet.

"Kopper" Merged Into Mesa As A Big Win For Zink

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

  • "Kopper" Merged Into Mesa As A Big Win For Zink

    Phoronix: "Kopper" Merged Into Mesa As A Big Win For Zink

    Merged into Mesa 22.1-devel this morning is Kopper, a big improvement particularly for the Zink OpenGL-on-Vulkan driver code...

    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
    This is fantastic, and it unlocks the option for driver developers to make Vulkan-only drivers, with Zink handling the OpenGL ES used by desktop environments. I can't wait to test GNOME-on-Zink out to see if it's viable.

    Comment


    • #3
      A part of me is idly wondering if (portions of) this can be ported to Haiku OS, which will likely only ever support 3D acceleration via FLOSS Vulkan drivers -- presumably because it's too resource intensive for Haiku to implement native OpenGL drivers for the supported GPUs...

      Comment


      • #4
        I remember when Vulkan was released and the official statement was that it's not a replacement for OpenGL. Well yes, but actually no.

        Comment


        • #5
          Originally posted by novhack View Post
          I remember when Vulkan was released and the official statement was that it's not a replacement for OpenGL. Well yes, but actually no.
          What they meant by that is that Vulkan is more low level than OpenGL, so it is not a direct replacement. It does not mean that you can't substitute OpenGL usage with Vulkan usage if you want more low level control or map OpenGL to Vulcan underneath.

          Comment


          • #6
            This is great and definitly something I look forward to test in the next Mesa release! Wonder if Plasma Wayland will work on Zink then :-)

            Comment


            • #7
              What is the point of running existing drivers on Zink instead of the "native" opengl implementation by intel/nvidia/amd?

              Comment


              • #8
                Originally posted by RahulSundaram View Post

                What they meant by that is that Vulkan is more low level than OpenGL, so it is not a direct replacement. It does not mean that you can't substitute OpenGL usage with Vulkan usage if you want more low level control or map OpenGL to Vulcan underneath.
                I know. It was a joke.

                Comment


                • #9
                  Originally posted by novhack View Post

                  I know. It was a joke.
                  Ah, my bad. Hard to decipher humor with just text sometimes.

                  Comment


                  • #10
                    Originally posted by RahulSundaram View Post

                    What they meant by that is that Vulkan is more low level than OpenGL, so it is not a direct replacement. It does not mean that you can't substitute OpenGL usage with Vulkan usage if you want more low level control or map OpenGL to Vulcan underneath.
                    What lower level control are you talking about? - if you want low level control you'd use Vulkan, OpenGL is not a low level API.

                    Comment

                    Working...
                    X