Announcement

Collapse
No announcement yet.

Open-Source Radeon UVD Video Support On Fedora

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

  • #16
    Originally posted by agd5f View Post
    Legal, for the most part, is not that familiar with the hardware details and what risks they may pose. Once again, it's a technical risk review of releasing the IP. Is any of the information related to patent applications that may be in flight. Is any of the information licensed from 3rd parties where we may need some else's permission of release the information. Would the information put AMD at risk for with respect to contractual agreements with other companies. Would the information put our ability to sell into the windows market at risk, etc. Legal is involved to a certain extent, but it mostly comes down to software and hardware architects who are more familiar with the low level details of the hardware and software stacks across OSes and what risks they may pose. Unfortunately, those software and hardware architects are very busy and a complex technical risk review takes time.
    Okay so its a legal review but not by legal, so i was half right lol

    Comment


    • #17
      Originally posted by Awesomeness View Post
      How bad are these things? My laptop is 5 years old. Core2 Duo CPU. Software decoding of a 720p clip uses roughly 30% of the CPU.
      My original intention with my comment was that getting VDPAU to work seems too complicated that it would be worth the effort until the patch lands in Linux distributions. Living with 30% CPU usage for a few more months seemed OK but if AMD APUs are really this bad, I can understand why everybody is so eager to get this to work.
      Too bad compiling this stuff will take ages on those things…
      Try 1080p and see what the usage is. No matter the usage though your laptop is burning through more power to display that movie which is an issue when youre on battery power (plane ride, car ride, train ride, etc) Also if you are trying to do OTHER things while playing the movie (Say youre multitasking and the movie is more background noise) thats less CPU time for everything else. Which could be a big deal if you are say.... compiling software and watching a movie to kill time? With CPU + UVD, the CPU can compile while UVD decodes, without UVD the tasks are fighting over CPU time. OR If you are trying to rip a movie, the UVD could PROBABLY (read: im not 100% sure on this scenario) help in the decode process and possibly help in the re-encode process, thus improving rip times.

      Comment


      • #18
        Originally posted by agd5f View Post
        Once again, it's a technical risk review of releasing the IP. Is any of the information related to patent applications that may be in flight. Is any of the information licensed from 3rd parties where we may need some else's permission of release the information. Would the information put AMD at risk for with respect to contractual agreements with other companies. Would the information put our ability to sell into the windows market at risk, etc.
        That sounds like the very definition of a legal review. It doesn't matter what kind of college degree the reviewer has, that's what it is.

        Comment


        • #19
          Originally posted by chris200x9 View Post
          It's possible, it doesn't over heat with fglrx though so I'm assuming no.
          I thought the same at first. My laptop runs warm, but it is useable with radeon and the following tweaks:
          -linux-phc undervolting
          -profile low
          -"conservative" cpu frequency governor (ondemand is the oven governor, it seems)
          And I need to blow the fan out more often than with fglrx.
          Also, a fan control daemon is necessary if I have sustained high loads (Lenovo screwed up the default tables...)

          But on the other hand, I use the VTs so much that the text-gfx modesetting switch speed is more important than OpenGL.

          Comment


          • #20
            Originally posted by Awesomeness View Post
            How bad are these things? My laptop is 5 years old. Core2 Duo CPU. Software decoding of a 720p clip uses roughly 30% of the CPU.
            My original intention with my comment was that getting VDPAU to work seems too complicated that it would be worth the effort until the patch lands in Linux distributions. Living with 30% CPU usage for a few more months seemed OK but if AMD APUs are really this bad, I can understand why everybody is so eager to get this to work.
            Too bad compiling this stuff will take ages on those things…
            Just out of curiosity-are you sure it's CPU decoding, or do you have an odd setup?
            A Core2 Duo would usually be integrated Intel gfx or Nvidia, which would mean vaapi support or vdpau.
            But I don't know your hardware as well as you, I realize.

            On a 1.6 GHz dual-core Neo with make -j1 (thermal reasons), I get ~15 minute compiles for mesa:
            Code:
             ./configure --prefix=/opt/mesa9x --enable-texture-float --with-dri-driverdir=/opt/mesa9x/lib --without-dri-drivers --with-gallium-drivers=r600 --with-clang-libdir=/usr/lib/llvm-3.3/lib
            This is after installing the LLVM 3.3 snapshot from the appropriate repo.
            Kernel compiles I can't do all in one run, but it's less than a half-hour including time to cool down.
            And libdrm is at most five minutes.
            Due to the GPU version I'm stuck with the vdpau shader implementation at best.

            On Ubuntu, you can currently add two PPAs (Oibaf or xorg-edgers, and mainline), install the new kernel and mesa, reboot, and that should be enough to get it working.
            On Fedora or Debian it takes more work for lack of packages (does someone have OBS builds setup?).

            Comment


            • #21
              Originally posted by Awesomeness View Post
              How bad are these things? My laptop is 5 years old. Core2 Duo CPU. Software decoding of a 720p clip uses roughly 30% of the CPU. ... Living with 30% CPU usage for a few more months seemed OK but if AMD APUs are really this bad, I can understand why everybody is so eager to get this to work.
              The e-350: think Atom + 30%. Not even close to your core 2 duo (but something like 5% of the price and 30% of the wattage).

              Comment


              • #22
                Yep. Remember that we make "big APUs" (A series with 2-4 Stars or Piledriver cores) and "small APUs" (E series with 1-2 Bobcat cores), and the big ones have 2-3x the CPU and GPU power of the small ones.

                UVD is more helpful on the small APUs, since they have relatively lower CPU power available for software decoding.
                Last edited by bridgman; 05-06-2013, 06:54 AM.

                Comment


                • #23
                  Nvidia

                  I wish Nouvoue worked better with video acceleration too.
                  720p and 1080p on YouTube lags.

                  Comment


                  • #24
                    Originally posted by Ibidem View Post
                    Just out of curiosity-are you sure it's CPU decoding, or do you have an odd setup?
                    A Core2 Duo would usually be integrated Intel gfx or Nvidia, which would mean vaapi support or vdpau.
                    NVidia and I have working VDPAU but only MPlayer is using it. I prefer VLC, though, and VLC 2.0 only supports VAAPI (the VAAPI wrapper for NVidia never ever worked for me). VLC 2.1 will support VDPAU and according to https://trac.videolan.org/vlc/roadmap it's around the corner (due in 9 days).

                    Comment


                    • #25
                      Originally posted by chris200x9 View Post
                      If only laptop users could use the open source driver at all. Without power management my laptop overheats to shutdown even with low profile AND doing nothing graphically intensive.
                      That's really funny, because my laptop is running the open source drivers, and I exceed the advertised battery life by over an hour.

                      Comment


                      • #26
                        Originally posted by Awesomeness View Post
                        How bad are these things? My laptop is 5 years old. Core2 Duo CPU. Software decoding of a 720p clip uses roughly 30% of the CPU.
                        My original intention with my comment was that getting VDPAU to work seems too complicated that it would be worth the effort until the patch lands in Linux distributions. Living with 30% CPU usage for a few more months seemed OK but if AMD APUs are really this bad, I can understand why everybody is so eager to get this to work.
                        Too bad compiling this stuff will take ages on those things…
                        Some simple math:
                        1280x720=921,600
                        1920x1080=2,073,600
                        2,073,600/921,600=2.25
                        2.25x30%=67.5% <-- there is your ***AVERAGE*** CPU use for decoding a 1080p video at the same 30 fps.
                        Now, near 70% average means a number of things to you:
                        1) That the PEAK will be over 100%.
                        2) That 60 fps is totally out of reach.
                        3) That higher bitrate videos will be totally out of reach.
                        4) That your CPU fan will be running on full vacuum cleaner mode 100% of the time.

                        Have you ever tried watching a movie with frames dropping, A/V out of sync, and a vacuum cleaner running in the background?

                        My HTPC is a single core Sempron, selected for low power consumption and low NOISE. It is *able* to decode 720p with under 50% CPU use. It can more or less decode 1080p 30fps typical 1.5 hours per 10 GB stuff you find on the 'net.... but the vacuum cleaner mode is a bit distracting and counteracts the objectives.... which is why I installed a crystalhd 970015 in the unit. I would sure be happy to drop the crystalhd, but the chipset is an RS780, aka "not yet supported".
                        Last edited by droidhacker; 05-06-2013, 08:35 AM.

                        Comment


                        • #27
                          Originally posted by Awesomeness View Post
                          NVidia and I have working VDPAU but only MPlayer is using it. I prefer VLC, though, and VLC 2.0 only supports VAAPI (the VAAPI wrapper for NVidia never ever worked for me). VLC 2.1 will support VDPAU and according to https://trac.videolan.org/vlc/roadmap it's around the corner (due in 9 days).
                          nvidia is not= to nouveau.

                          Comment


                          • #28
                            Originally posted by droidhacker View Post
                            nvidia is not= to nouveau.
                            If you reply to one of my comments, do it in complete sentences.

                            Comment


                            • #29
                              Originally posted by Awesomeness View Post
                              If you reply to one of my comments, do it in complete sentences.
                              Go troll elsewhere.

                              Comment


                              • #30
                                Originally posted by droidhacker View Post
                                Go troll elsewhere.
                                Anybody here understanding what this retard meant by “nvidia is not= to nouveau”?

                                Comment

                                Working...
                                X