Announcement

Collapse
No announcement yet.

AMD Lands Mostly Fixes In Latest Batch Of AMDVLK/XGL/PAL Code Updates

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

  • AMD Lands Mostly Fixes In Latest Batch Of AMDVLK/XGL/PAL Code Updates

    Phoronix: AMD Lands Mostly Fixes In Latest Batch Of AMDVLK/XGL/PAL Code Updates

    The AMD developers maintaining their "AMDVLK" Vulkan driver have pushed out their latest batch of code comprising this driver including the PAL abstraction layer, XGL Vulkan bits, and LLPC LLVM-based compiler pipeline...

    http://www.phoronix.com/scan.php?pag...September-2018

  • #2
    The Vulkan driver is the last weak link of the AMD opensource drivers, the only place where Nvidia still have a strong lead (if you not count OpenCL/CUDA).

    Comment


    • #3
      Originally posted by [email protected] View Post
      The Vulkan driver is the last weak link of the AMD opensource drivers, the only place where Nvidia still have a strong lead (if you not count OpenCL/CUDA).
      yes, ironic considering how AMD dominates Nvidia on windows in Vulkan applications. This was one area where AMD was not expected to fall behind (modern graphics APIs)... and for so long, now it's over 2.5 years since Vulkan was released. Very disappointing. But kudos to Nvidia.

      Two glaring issues seem to be that the open source shader compiler is not as good, and that the development talent is split on Vulkan work with AMD working on amdvlk but Red Hat, Valve etc working on RadV.

      Comment


      • #4
        Originally posted by [email protected] View Post
        The Vulkan driver is the last weak link of the AMD opensource drivers, the only place where Nvidia still have a strong lead (if you not count OpenCL/CUDA).
        Nvidia also does have a strong lead in having more bugs than radv.

        Comment


        • #5
          Originally posted by humbug View Post
          Two glaring issues seem to be that the open source shader compiler is not as good, and that the development talent is split on Vulkan work with AMD working on amdvlk but Red Hat, Valve etc working on RadV.
          The "going it alone" route offers them more flexibility, but more doing it themselves. and as with all their open source projects, I am sure it will keep getting better with age

          Comment


          • #6
            What happened to the plan to get this running off standard LLVM?

            Comment

            Working...
            X