Announcement

Collapse
No announcement yet.

Porting Of Changes/Fixes From AMDVLK To RADV Vulkan Driver Begins

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

  • Porting Of Changes/Fixes From AMDVLK To RADV Vulkan Driver Begins

    Phoronix: Porting Of Changes/Fixes From AMDVLK To RADV Vulkan Driver Begins

    RADV Vulkan driver co-founder David Airlie has begun digging through AMD's newly-opened AMDVLK official Vulkan driver in order to gain some hindsight and port some fixes/changes to this unofficial Mesa-based open-source Vulkan driver...

    http://www.phoronix.com/scan.php?pag...Porting-Begins

  • #2
    XGL? How did you get that codename?

    Comment


    • #3
      Originally posted by tildearrow View Post
      XGL? How did you get that codename?
      https://github.com/GPUOpen-Drivers/xgl it's part of AMDVLK
      Michael Larabel
      http://www.michaellarabel.com/

      Comment


      • #4
        Originally posted by tildearrow View Post
        XGL? How did you get that codename?
        In June of 2014 AMD submitted the XGL proposal based on its work on Mantle. Once accepted by the OpenGL Next working group, AMD helped steward it through committee via its role as spec editors.
        http://www.eenewseurope.com/news/amd...ver-vulkan-api

        Comment


        • #5
          RADV might be developed by 2 people, but Dave and Bas put so much work into it. Thanks guys

          Comment


          • #6
            RADV works better except for a handful of games. There are also quite a few regressions in the AMD vulkan driver compared to when it was in their closed stack, did they strip some goodness from it?

            Comment


            • #7
              Originally posted by theriddick View Post
              RADV works better except for a handful of games. There are also quite a few regressions in the AMD vulkan driver compared to when it was in their closed stack, did they strip some goodness from it?
              They changed out the shader compiler back-end in the process.
              Michael Larabel
              http://www.michaellarabel.com/

              Comment


              • #8
                Originally posted by Michael View Post

                They changed out the shader compiler back-end in the process.
                Not likely, i think both vendors use a modified LLVM inside their closed drivers.

                Comment


                • #9
                  Originally posted by artivision View Post

                  Not likely, i think both vendors use a modified LLVM inside their closed drivers.
                  I was told by AMD that AMDVLK uses a "different shader compiler."
                  Michael Larabel
                  http://www.michaellarabel.com/

                  Comment


                  • #10
                    Originally posted by artivision View Post
                    Not likely, i think both vendors use a modified LLVM inside their closed drivers.
                    What does "both vendors" mean in this context - closed vs open versions ?

                    I believe both closed and open generate LLVM IR from SPIR-V, however the usage from that point on is different - the closed driver generates proprietary IR from LLVM IR then uses our proprietary shader compiler to generate HW instructions, while the open driver uses the LLVM IR direct-to-ISA back end also used in radeonsi and HCC/ROCm (and radv IIRC).

                    Comment

                    Working...
                    X