Announcement

Collapse
No announcement yet.

AMDVLK Official Open-Source Radeon Vulkan Driver Updated

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

  • #11
    Originally posted by Michael View Post
    Extremely unlikely to happen.
    We have a lot extremists to wishlist utter hard to near impossible things

    Originally posted by KRiloshart View Post
    Now that important bits are open sourced I hope AMD makes radeonSI cross platform and replace their closed source GL driver with it. This would bring a lot symmetry between their pro and non pro driver stack and hopefully save lots of amd cash.
    Extreme hope must be extreme healty, with that in mind you could live 120 years minimum
    Last edited by dungeon; 22 January 2018, 01:47 PM.

    Comment


    • #12
      Remember that the main reason for keeping the closed source driver is that it supports compatibility profiles (including tested support for the combinations of deprecated and new functionality that real-world CAD apps actually use), while Mesa does not support compatibility profiles past 3.x.
      Test signature

      Comment


      • #13
        bridgman Any chance to get the info on the vendor specific part of the windows kernel interface of the AMD driver?

        Comment


        • #14
          Originally posted by bridgman View Post
          Remember that the main reason for keeping the closed source driver is that it supports compatibility profiles (including tested support for the combinations of deprecated and new functionality that real-world CAD apps actually use), while Mesa does not support compatibility profiles past 3.x.
          there was a patch by marek to get 3.1 compat support
          why it isn't mainline?

          Comment


          • #15
            Originally posted by geearf View Post

            You can easily have multiple Vulkan ICD on your computer and pick the one you want to use when starting an app, it's not a problem.
            How do you do that if you mind me asking?

            Comment


            • #16
              Originally posted by LinuxID10T View Post

              How do you do that if you mind me asking?

              Comment


              • #17
                Originally posted by LinuxID10T View Post

                How do you do that if you mind me asking?
                VK_ICD_FILENAMES=<pathtoICD> <program>

                The app itself could ask of course.

                Comment


                • #18
                  Originally posted by davidbepo View Post

                  there was a patch by marek to get 3.1 compat support
                  why it isn't mainline?
                  It's NOT ready, yet and Marek had some other things to do.

                  Comment


                  • #19
                    Originally posted by geearf View Post

                    You can easily have multiple Vulkan ICD on your computer and pick the one you want to use when starting an app, it's not a problem.
                    It is a major problem if you're a game engine developer that has only so much time to support one or the other.

                    Comment


                    • #20
                      Originally posted by Almindor View Post

                      It is a major problem if you're a game engine developer that has only so much time to support one or the other.
                      It is quite far from being a major problem.

                      And even then, since the 2 drivers can be installed side by side, nothing prevents you from only supporting one of them and telling your users to use that one.
                      That's pretty much what they do with distributions already.

                      Comment

                      Working...
                      X