Announcement

Collapse
No announcement yet.

AMDVLK Updated With Fresh Batch Of Fixes

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    AMDVLK Updated With Fresh Batch Of Fixes

    Phoronix: AMDVLK Updated With Fresh Batch Of Fixes

    It's roughly weekly that AMD updates their external and public facing AMDVLK/PAL source tree for this open-source Radeon Vulkan driver while following last week's significant update with Wayland support and more, they have quickly issued another update to this RADV driver alternative...

    AMDVLK Updated With Fresh Batch Of Fixes - Phoronix
    http://www.phoronix.com/scan.php?page=news_item&px=AMDVLK-Fixes-Wolfenstein-2
    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
    Tags: None
  • #2
    Are Doom/Wolfenstein one of the rare cases where amdvlk is better than radv? I recently tried Doom with radv and it wasn't running very well.

    Comment

    • #3
      How did the situation concerning external contributions turn out? ATM it seems like the internal code is simply made public once a week.

      Comment

      • #4
        Did anyone manage to make it work with dxvk?

        Comment

        • #5
          Originally posted by aufkrawall View Post
          Are Doom/Wolfenstein one of the rare cases where amdvlk is better than radv? I recently tried Doom with radv and it wasn't running very well.
          There is a fix in git to improve doom performance. You'll need the latest kernel, libdrm, mesa and LLVM.

          Comment

          • #6
            Originally posted by GruenSein View Post
            How did the situation concerning external contributions turn out? ATM it seems like the internal code is simply made public once a week.
            We are happy to accept community contributions and we have received a few patches. We are still trying to work out how to expose our internal history more cleanly to the community while still being able to work on things like new asic support and other OSes within the same tree, but we wanted to get the code out sooner rather than later.
            • Likes 2

            Comment

            • #7
              Originally posted by agd5f View Post

              We are happy to accept community contributions and we have received a few patches. We are still trying to work out how to expose our internal history more cleanly to the community while still being able to work on things like new asic support and other OSes within the same tree, but we wanted to get the code out sooner rather than later.
              Do you know, is this a bug in amdvlk, or something dxvk not doing correctly? https://github.com/doitsujin/dxvk/issues/148

              Comment

              Previous template Next
              Working...
              X