Announcement

Collapse
No announcement yet.

AMDGPU Changes Begin Queuing Ahead Of Linux 5.1 Kernel Cycle

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

  • #11
    Originally posted by debianxfce View Post

    Where are reasonable priced freesync2 HDR monitors? Do you really need techniques like HDR and ray tracing that slows down fps. The rc-2 kernel has more patches for the nvme driver so avoid the rc-1 kernel that is partially implemented and unstable.
    I wasn't aware of an AMD based GPU that had ray tracing...

    To give you an answer: Yes, we do need those techniques.

    Why do we need them? Because having options is nice.

    Don't want it, don't enable it. Simple as that.

    Comment


    • #12
      Originally posted by debianxfce View Post

      Back porting is a waste resources, why on earth someone wants use old and buggy software.
      Stop trolling indeed. Is there ignore button here?

      Comment


      • #13
        Originally posted by skeevy420 View Post
        So what? Most games aren't Linux native. At least if all the bits and pieces are in place for the driver, Wine, and DXVK then we might get HDR/Freesync for non-native games eventually.
        It took years to have Open GL freesync support in open source drivers and still freesync stuff is missing from the mainline Mesa. It is the RADV driver where you have freesync and hdr code to make current and future vulkan games have freesync support. No plans for RADV to have freesync support.

        Comment


        • #14
          Originally posted by shmerl View Post
          This is quite a serious bug. Will it be backported to earlier kernels?
          Originally posted by faph View Post
          And can we have this please backported?
          ...and everyone else asking for backports.

          See guys? This is one area where proprietary drivers are better than in-kernel drivers, Nvidia's blob included. They are independent and can be updated independently no need for a fucking backport or updating the entire god damn kernel.

          But no, people will keep on and on about nonsense in other threads about it.

          Comment


          • #15
            Originally posted by Weasel View Post
            ...and everyone else asking for backports.

            See guys? This is one area where proprietary drivers are better than in-kernel drivers, Nvidia's blob included. They are independent and can be updated independently no need for a fucking backport or updating the entire god damn kernel.
            Sorry, but they are not better. Being proprietary just forces them to make it as a kernel module, but they also can lag behind supporting newer kernels and it surely doesn't guarantee them to work with older ones. dkms isn't infallible even if it offers some temporary flexibility. Besides, nothing stops AMD from offering amdgpu changes as a dkms option.

            Comment


            • #16
              Originally posted by debianxfce View Post

              Back porting is a waste resources, why on earth someone wants use old and buggy software.
              People work in HDR mainly for 3D Modeling and film, not video games, so having HDR enabled on hardware that guarantees it but never delivers is annoying.

              Comment


              • #17
                Originally posted by juno View Post
                And to add at least a little sense to my own post: HDR doesn't "slow down FPS" because every modern game is running a HDR pipeline already.
                Not only that, but the "compression" of colors to SDR is a processing step that can be saved. So in fact, native HDR would increase performance when hooked up to a monitor with native color support as written in the game code. (at least in theory)

                Comment


                • #18
                  Originally posted by Weasel View Post
                  See guys? This is one area where proprietary drivers are better than in-kernel drivers, Nvidia's blob included. They are independent and can be updated independently no need for a fucking backport or updating the entire god damn kernel.
                  You don't need proprietary drivers - AMD open source drivers are available both upstream and packaged with DKMS/KCL "so that they are independent and can be updated independently".
                  Last edited by bridgman; 01-16-2019, 03:26 PM.

                  Comment


                  • #19
                    Originally posted by bridgman View Post

                    You don't need proprietary drivers - AMD open source drivers are available both upstream and packaged with DKMS/KCL "so that they are independent and can be updated independently".
                    Where exactly are amdpgpu dkms packages available though? Wasn't there some plan to make a Debian (and some other distros) repos for them? Would be useful to test latest amdgpu updates without recompiling the whole kernel, but at the same time that's all I need, I don't want to install the whole PRO bundle to get it.

                    Comment


                    • #20
                      Originally posted by faph View Post
                      and then:
                      - Shader clocks and memory clocks are now exposed via hwmon interfaces.
                      Fu**ing finally!
                      What does this mean exactly? Is it just a readback or can I easily change the clocks with that patch?

                      Comment

                      Working...
                      X