Announcement

Collapse
No announcement yet.

ARB_copy_image Support Lands For AMD RadeonSI

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

  • ARB_copy_image Support Lands For AMD RadeonSI

    Phoronix: ARB_copy_image Support Lands For AMD RadeonSI

    Marek Olš?k has landed support for OpenGL 4.3's ARB_copy_image extension, which is used by several modern Steam Linux games...

    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
    "I wonder if the craziness was worth it."

    Perhaps

    Comment


    • #3
      Hurray! Finally RadeonSI is in the lead over Nvidia

      Comment


      • #4
        Originally posted by Azpegath View Post
        Hurray! Finally RadeonSI is in the lead over Nvidia
        Nice catch!

        Comment


        • #5
          And also nice job Marek and Brian (for the review)! You can be sure that my next card going to be an AMD (as for my current one actually).

          Is there a reason why amdgpu doesn't appear in GL3.txt? I thought it would appear when it arrived in the Linux kernel, but apparently not. Or maybe it's because it's not activated yet?

          Comment


          • #6
            Originally posted by Creak View Post
            And also nice job Marek and Brian (for the review)! You can be sure that my next card going to be an AMD (as for my current one actually).

            Is there a reason why amdgpu doesn't appear in GL3.txt? I thought it would appear when it arrived in the Linux kernel, but apparently not. Or maybe it's because it's not activated yet?
            amdgpu is a kernel driver not a mesa driver. It provides hardware support not GL support. radeonsi will be used for both kernel drivers to provide OpenGL.

            Comment


            • #7
              Originally posted by Creak View Post
              And also nice job Marek and Brian (for the review)! You can be sure that my next card going to be an AMD (as for my current one actually).

              Is there a reason why amdgpu doesn't appear in GL3.txt? I thought it would appear when it arrived in the Linux kernel, but apparently not. Or maybe it's because it's not activated yet?
              Yeah, thanks Marek and Brian fpr that "craziness" :-)

              amdgpu only exists on the kernel side, for mesa there is no such thing. Mesa's radeonsi driver will use either the old radeon kernel backend (for cards up to Hawaii / R9 290) or the new amdgpu one (for 3xx cards, at least if they're really new ones and not just renamed). That's why it doesn't make sense to have amdgpu in GL3.txt :-)

              Comment


              • #8
                Originally posted by Creak View Post

                Is there a reason why amdgpu doesn't appear in GL3.txt? I thought it would appear when it arrived in the Linux kernel, but apparently not. Or maybe it's because it's not activated yet?
                You are probably the reason i discussed with Bridgman name changing in mesa ... Because from amdgpu driver user POV, only mesa part has different name... everything else (kernel driver, drm, ddx, llvm) is called amdgpu.

                Reason? Maybe userspace blob UMD will be amdgpu something, but dunno
                Last edited by dungeon; 28 October 2015, 09:30 AM.

                Comment


                • #9
                  If you ask why we don't list amdgpu in GL3.txt, you should also ask why we don't list radeon there. Yes, radeon is not a gallium driver. radeonsi is.

                  ARB_copy_image was implemented because Bioshock requires it.

                  Comment


                  • #10
                    Originally posted by marek View Post
                    ARB_copy_image was implemented because Bioshock requires it.
                    Actually Bioshock doesn't require it, it can be disabled with game switch... but yeah it preferably wants it for eON's so called DX11 mode it think, while game can work in DX10 mode also by a switch.

                    Not sure in what mode it runs on opensource drivers, on nVidia it runs in DX11 mode by default, while with Catalyst in DX10 so not until someone disable workarunds by a switch or maybe dx10 switch is DiRT only hmm? anyway maybe switches to try:

                    --eon_disable_catalyst_workarounds
                    --eon_disable_arb_copy_image
                    --eon_force_dx10
                    Last edited by dungeon; 28 October 2015, 11:04 AM.

                    Comment

                    Working...
                    X