Originally Posted by CityK
I've only skimmed through, but I don't believe any one made any differentiation between which drivers (for AMD graphics adapter hardware) they were using i.e. the prop. (catalyst/fglrx) stack or the OSS stack? I imagine the bulwark is in regards to the former. For that matter, I imagine that most people are still unaware that the modern OSS stack is very good for r600 class hardware (SI catching up, and Sea Islands/CIK will probably be in pretty good shape upon release). In brief:
- 3.10 - brought about UVD support for a large swath of hardware ... used inconjunction with VPDAU ... besides the kernel, you will need appropriate user space supprt (i.e. update your Mesa version etc.)
- 3.11 - brought about DPM support for a large swath of hardware (i.e. no more thermo nuclear reactors) ... further UVD support refinements
- 3.12 - will bring about even further UVD and DPM support fixes and extension of support
I'll revisit this again after working with an AMD APU (6400K) for the last several days.
First, I'll start with acceleration is finally working, and generally usable with AMD GPUs now. XvBA, and VA-API are working, and generally pretty good. You can even use VDPAU now, which is a recent development (July I think). This gives you acceleration with Adobe Flash, which is something that has been severely lacking with AMD GPUs.
The Catalyst (proprietary) driver is actually quite good, and only getting better, for video. More on that in a bit. The Catalyst suite can be complicated to get set up though. Using both Linux Mint and Arch Linux, I had some issues getting it to load properly. The driver packaged with the distribution will give you fits in Mint. Arch Linux I had a hell of a time getting the driver to properly load. In Arch I had to use the Catalyst-Hook package to get everything resolved properly. You'll have to Google the latest information for your distribution.
The open source driver is good. It's well supported, and easy to load. However, any GPU 7000 series or higher (I was using a 8470) you'll have no audio over HDMI. Here's the feature matrix for the open-source drivers pertaining to each series of GPU.
So, I was able to get graphic acceleration in VLC and Mplayer. Running Netflix via Pipelight was good enough. However, I've found that it's dicey on the quality you can expect with any GPU when using Pipelight or Netflix-Desktop. Tweaking will be necessary, and finding a sweet spot can be challenging. It's no different than a virtual machine where I had to allocate over 3 GB of RAM to the virtual machine to get good enough Netflix playback.
With the open-source driver I couldn't get audio over HDMI due to my series of GPU. It's coming, but it's not here yet. The proprietary driver had audio over HDMI, but it wasn't good. Anything that ran Flash had a lot of static.
MythTV, which is the heart of the system I am using this APU for, is another story.
MythTV still doesn't like the AMD stuff. Granted, I got decent playback with stock settings. However, the VA-API acceleration was unusable. It created all kinds of problems. Stock settings for a computer monitor would probably be okay, but a 50"+ TV will have noticeable problems. MythTV really relies on acceleration to get things done. Without it, you can get by, but it's not the quality you'd like.
So, I rebuilt my old machine with my Nvidia GT440. It's a big box, my wife wants it smaller. But realistically, AMD is close, but not fully there yet. Not fully there yet puts my project on the backburner for a bit.
I'm going to futz around with XBMC a bit and see what I can accomplish there. MythTV is pretty demanding when it comes to resources.