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.
Announcement
Collapse
No announcement yet.
Open-Source Radeon UVD Video Support On Fedora
Collapse
X
-
Originally posted by Awesomeness View PostHow 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.
Leave a comment:
-
Originally posted by Awesomeness View PostHow 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?
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
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?).
Leave a comment:
-
Originally posted by chris200x9 View PostIt's possible, it doesn't over heat with fglrx though so I'm assuming no.
-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.
Leave a comment:
-
Originally posted by agd5f View PostOnce 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.
Leave a comment:
-
Originally posted by Awesomeness View PostHow 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?
Leave a comment:
-
Originally posted by agd5f View PostLegal, 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.
Leave a comment:
-
Originally posted by smitty3268 View PostWhy would an engineer care if info is released publicly? That makes no sense. Even if it's an engineer doing the work, it's obviously a legal review.
Leave a comment:
-
Originally posted by bridgman View PostFor the lebenty-millionth time, it's primarily a technical review not a legal review.
Leave a comment:
Leave a comment: