Announcement

Collapse
No announcement yet.

AMD's Open-Source RadeonSI Driver Sees New Patches

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

  • AMD's Open-Source RadeonSI Driver Sees New Patches

    Phoronix: AMD's Open-Source RadeonSI Driver Sees New Patches

    It's been one year since AMD introduced their Radeon HD 7000 "Southern Islands" graphics cards, but the open-source RadeonSI Gallium3D driver for providing an open-source OpenGL driver for this latest-generation of AMD GPUs is still far from being in a readied state for AMD Linux customers...

    http://www.phoronix.com/vr.php?view=MTI3Njk

  • #2
    Originally posted by phoronix View Post
    Phoronix: AMD's Open-Source RadeonSI Driver Sees New Patches

    It's been one year since AMD introduced their Radeon HD 7000 "Southern Islands" graphics cards, but the open-source RadeonSI Gallium3D driver for providing an open-source OpenGL driver for this latest-generation of AMD GPUs is still far from being in a readied state for AMD Linux customers...

    http://www.phoronix.com/vr.php?view=MTI3Njk
    I thought that RadeonSI mostly worked (including 3d), and needed testing and bug hunting?

    Comment


    • #3
      Originally posted by pingufunkybeat View Post
      I thought that RadeonSI mostly worked (including 3d), and needed testing and bug hunting?
      It does mostly work already including 3D. The only requirement is a pre-1.13 xserver due to issues with glamor on newer xservers.

      Comment


      • #4
        http://lists.freedesktop.org/archive...ry/000290.html

        ;(

        Comment


        • #5
          From the above link:

          On 01/11/2013 09:53 PM, Michel Dänzer wrote:
          > On Don, 2012-11-29 at 11:19 +0800, Zhigang Gong wrote:
          >> Junyan has been working on that and got some progress. The major work is in
          >> Xserver side. We decide to use glx(xserver side) to create glamor's context
          >> and don't rely on egl thus we can avoid the conflict with glx's dri loader
          >> and the egl's. Junyan, do you have any update currently? When will you
          >> submit your patchset to xserver?
          agd5f, isnt that counter-productive with Wayland coming (hopefully) soon? GLX is X-specific isnt it? I was under the impression that to go from X + mesa to Wayland + mesa just needed a recompile with the appropriate configure flag (source: https://aur.archlinux.org/packages/m...yland/PKGBUILD)

          If the RadeonSI driver depends on GLX, wont it need to be patched to work on Wayland vs X respectively?

          Or am I reading too far into this and misunderstanding the message?

          Comment


          • #6
            Originally posted by agd5f View Post
            It does mostly work already including 3D.
            Are you still sharing the results from piglit runs? If I remember correctly, results for r600/r600g where available somewhere at some point.

            Comment


            • #7
              Originally posted by Ericg View Post
              From the above link:



              agd5f, isnt that counter-productive with Wayland coming (hopefully) soon? GLX is X-specific isnt it? I was under the impression that to go from X + mesa to Wayland + mesa just needed a recompile with the appropriate configure flag (source: https://aur.archlinux.org/packages/m...yland/PKGBUILD)

              If the RadeonSI driver depends on GLX, wont it need to be patched to work on Wayland vs X respectively?

              Or am I reading too far into this and misunderstanding the message?
              I think it's just the DDX driver which is using GLX. On Wayland, that won't even be used - it will just run straight off of Mesa.

              Comment


              • #8
                Originally posted by agd5f View Post
                It does mostly work already including 3D. The only requirement is a pre-1.13 xserver due to issues with glamor on newer xservers.
                So can it run Quake 3 and composited desktops then? Or is it just in the glxgears state right now?

                Comment


                • #9
                  Originally posted by Ericg View Post
                  If the RadeonSI driver depends on GLX, wont it need to be patched to work on Wayland vs X respectively?
                  I think this is saying that *glamor* depends on GLX. Wayland doesn't need X or glamor, so I think this should be OK.

                  Comment


                  • #10
                    Originally posted by bridgman View Post
                    I think this is saying that *glamor* depends on GLX. Wayland doesn't need X or glamor, so I think this should be OK.
                    That's my understanding as well.

                    From what I've learned by building the components myself (for r600), it's like this:
                    R600/SI depend on xf86-video-ati or xf86-video-modesetting as their DDX. xf86-video-ati depends on glamor. glamor depends on glx (or egl?).

                    If you're using wayland, you'll do:
                    R600/SI use Mesa to provide the EGL runtime. EGL is used by Wayland to render. No DDX/glamor required.

                    Comment


                    • #11
                      Originally posted by Ericg View Post
                      agd5f, isnt that counter-productive with Wayland coming (hopefully) soon? GLX is X-specific isnt it? I was under the impression that to go from X + mesa to Wayland + mesa just needed a recompile with the appropriate configure flag (source: https://aur.archlinux.org/packages/m...yland/PKGBUILD)

                      If the RadeonSI driver depends on GLX, wont it need to be patched to work on Wayland vs X respectively?
                      Wayland doesn't provide a native rendering API. Apps have to use an existing one, like GL ES for example, so in wayland all you would need is the 3D driver. glamor is only needed for acceleration when using X.

                      As to radeonsi, it runs most desktop compositors and a fair number of games just fine.

                      Comment


                      • #12
                        Originally posted by Ericg View Post
                        I was under the impression that to go from X + mesa to Wayland + mesa just needed a recompile with the appropriate configure flag (source: https://aur.archlinux.org/packages/m...yland/PKGBUILD)
                        For running wayland you need the bare wayland: git://anongit.freedesktop.org/wayland/wayland
                        Then you need mesa with wayland support, i.e. "--with-egl-platforms=wayland,[drm,x11,…]", this uses wayland at compile time.
                        If I understand it correctly this should be enough to run "wayland". Of course you probably want a compositor like weston for that.

                        But... What about xwayland? How will this work with radeonsi? The xwayland website tells you to checkout a branch named xwayland-1.12 so it probably isn't a problem yet anyway, but with 1.13 a proper xf86-video-ati with xwayland support would need glamor too, right? I haven't heard anything about the performance of xf86-video-wlshm. Can it use the the 3d acceleration wayland "has"?

                        Comment


                        • #13
                          Originally posted by smitty3268 View Post
                          So can it run Quake 3 and composited desktops then?
                          gnome-shell works perfectly. Not sure about Quake 3 specifically right now, but it's running similar games fine.

                          Or is it just in the glxgears state right now?
                          Hasn't been for quite a long time.

                          Comment


                          • #14
                            Originally posted by ChrisXY View Post
                            [...] a proper xf86-video-ati with xwayland support would need glamor too, right?
                            For accelerated GLX/X11 client rendering, yes.

                            I haven't heard anything about the performance of xf86-video-wlshm. Can it use the the 3d acceleration wayland "has"?
                            Wayland doesn't provide any rendering APIs. The compositing works the same way, but the X window contents are rendered in software with xf86-video-wlshm.

                            Comment


                            • #15
                              At this rate we'll get full featured open source driver by 2025, if ever.

                              Comment

                              Working...
                              X