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

  • AMDGPU Changes Begin Queuing Ahead Of Linux 5.1 Kernel Cycle

    Phoronix: AMDGPU Changes Begin Queueing Ahead Of Linux 5.1 Kernel Cycle

    The drm-next-5.1-wip branch has been created by open-source AMD developers as they begin vetting the changes they plan to submit to DRM-Next for inclusion in the Linux 5.1 kernel cycle when it kicks off around the start of March...

    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

  • #2
    An interrupt handler (IH) overflow fix for Vega 10 that takes care of a random system lockup. The issue is most reproducible on Vega 10 but also may affect earlier generations too.
    This is quite a serious bug. Will it be backported to earlier kernels?

    Comment


    • #3
      where are the freesync2 HDR patches?

      Comment


      • #4
        Can't you just troll somewhere else?

        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.
        Last edited by juno; 16 January 2019, 05:53 AM.

        Comment


        • #5
          Originally posted by debianxfce View Post

          Back porting is a waste resources, why on earth someone wants use old and buggy software.
          Because if something is open so that even crazy troll like you could see it, that that does not mean it is ready for everybody

          Releases and particulary point releases are for general public

          General public defined by average Joe wanna point releases, capisco?
          Last edited by dungeon; 16 January 2019, 06:19 AM.

          Comment


          • #6
            Originally posted by phoronix View Post
            ... nothing really dramatic:
            and then:
            - Shader clocks and memory clocks are now exposed via hwmon interfaces.
            Fu**ing finally!

            Edit:
            And can we have this please backported?
            Last edited by faph; 16 January 2019, 09:58 AM.

            Comment


            • #7
              Originally posted by debianxfce View Post
              Can't you just troll somewhere else?
              Very few of them are Linux native.
              https://www.rockpapershotgun.com/201...-hdr-pc-games/

              By the way, shadow of the tomb raider is damn slow with wine-staging and dxvk. It is the slowest of tomb raider games. And not even freesync support in RADV.
              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.

              The rest of us see hope for the future and you're just peeing in our Cheerios.

              Comment


              • #8
                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


                • #9
                  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


                  • #10
                    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

                    Working...
                    X