Announcement

Collapse
No announcement yet.

German RadeonHD Hacker To Start R600 Gallium3D VDPAU

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

  • German RadeonHD Hacker To Start R600 Gallium3D VDPAU

    Phoronix: German RadeonHD Hacker To Start R600 Gallium3D VDPAU

    Christian König, the independent German developer who's known for being the first to provide open-source Radeon HDMI audio support back in the RadeonHD driver days and later to KMS, last October began working on R600 Gallium3D video acceleration. He quickly brought up XvMC R600g video acceleration when porting some of the earlier XvMC R300g work. While not yet merged to mainline, XvMC on R600 Gallium3D is usable, but now he's looking towards his next target: VDPAU support for the R600 Gallium3D driver...

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

  • #2
    "Video output of a 1920x1080 video now uses something around ~20% CPU time on my old test system, compared to ~50% with Xv, including all the nice features like overlay menu rendering for example (ok only working with mplayer right now, not xine)."
    That sounds great, and is more than I expected from XvMC. This would make most 1080p videos playable on a single core.

    Does anyone know how much work it is to enable this code? I lost track. It's in a separate branch, right?

    Comment


    • #3
      Is he going to work on r300g or r600g? What about ATI Avivo?

      Comment


      • #4
        He started on VDPAU a few weeks ago. He's not just starting now.

        Comment


        • #5
          Yeah I second that

          You can see his work here from over a month ago

          http://cgit.freedesktop.org/~deathsi.../?h=pipe-video

          Comment


          • #6
            Originally posted by NSLW View Post
            Is he going to work on r300g or r600g? What about ATI Avivo?
            He is working on r600g.

            -----------------

            I hope the xvmc code will get merged soon to master.

            Comment


            • #7
              Originally posted by Nille View Post
              He is working on r600g.

              -----------------

              I hope the xvmc code will get merged soon to master.
              afaik a state tracker is supposed to work on all G3D HW

              why is this supposed to be limited to R600??

              Comment


              • #8
                maybe because its only working on r600g currently? and you need some ddx changes.

                Comment


                • #9
                  And an state tracker does not mean all gallium drivers can use it. If an st require features that the hardware doesn't support it cant be working.

                  Comment


                  • #10
                    rejoice people....

                    ...who have a mythtv/xmbc media centre with a integrated r600g driven chip set )))))))))

                    just the news of progress will be welcome, even if it remains out of the main line mesa for a while - hopeully various major distro packers and bridge that gap.

                    Comment


                    • #11
                      In theory it should work on any gallium driver, however, I don't know if anyone has tried anything other than r600g yet. It shouldn't be too hard make it work on r300g if it's not already.

                      Comment


                      • #12
                        Originally posted by agd5f View Post
                        In theory it should work on any gallium driver, however, I don't know if anyone has tried anything other than r600g yet. It shouldn't be too hard make it work on r300g if it's not already.
                        It works with softpipe in addition to r600g.

                        I did some work to port it to the nv50 driver a few weeks ago. I got the motion compensation working perfectly, but never got the iDCT to work correctly. I still need to submit the patches for the MC support.

                        On nvfx with nv30, it reportedly fails to compile the vertex shader because it contains a conditional instruction. Not sure about nv40.

                        airlied tried to use pipe-video on r300g using an r500 card a few weeks ago, but not even the MC worked. He would have more details on that than I do.

                        Comment


                        • #13
                          Originally posted by NSLW View Post
                          What about ATI Avivo?
                          What are you asking?

                          Code is here, by the way.
                          http://cgit.freedesktop.org/mesa/mesa/log/?h=pipe-video

                          Comment


                          • #14
                            Originally posted by mattst88 View Post
                            What are you asking?

                            Code is here, by the way.
                            http://cgit.freedesktop.org/mesa/mesa/log/?h=pipe-video
                            Here is a snippet from Wikipedia about ATI Avivo
                            "In decoding, the GPU core supports hardware decoding of H.264, VC-1, WMV9, and MPEG-2 videos to lower CPU utilization (the bitstream processing/entropy decoding still requires CPU processing). ATI Avivo supports vector adaptive de-interlacing and video scaling to reduce jaggies, and spatial/temporal dithering, enabling 10-bit color quality on 8-bit and 6-bit displays during process stage."

                            I'm asking if anyone would take advantage of this features which are present in r500 hardware.

                            Comment


                            • #15
                              This is a shader-based approach to XvMC.

                              Originally posted by NSLW View Post
                              I'm asking if anyone would take advantage of this features which are present in r500 hardware.
                              The features you're talking about sound like UVD, which only fglrx supports right now. Which means that the answer to your question is "No".

                              Comment

                              Working...
                              X