Radeon UVD Support Going Through Code Review

[DeepDayze]

There needs to be better modularization of the driver components so as to make it easier to isolate encumbered 3rd party code to make it easier to remove such code from the driver codebase if it is to be ever released to the public. Even obfuscating the external proprietary function names as well should also be enough to pass legal muster.

[Adarion]

omg, too much Dopamine in my brain now.

Well, the thing is: Yes, BluRay Ripping and stuff is done. Of course it is done. Sly stuff is done. Yes. Because otherwise these things are sometimes unwatcheable.
So one could use that as an argument to say: c'mon just release specs and docs. (I would be happy if they did for sure.)
But then the content mafia could blame AMD which is a far better target than SlySoft which is located (officially) on some island somewhere between the deepest asian jungles and pacific ocean in a country that likely gives a shit about copyrights and stuff. AMD would be internationally open for attacks. AMD has enough troubles and doesn't need the MPAA or something on their ass. So I understand that they're careful with releasing this kind of code. Still, I would really embrace a real UVD/+/2/3/... functionality.

[Qaridarium]

in the end they release "Nothing" business as usual they also burn the open-source driver dev teams money in trying to implement a UVD solution.

in my point of view they just dream about a closed source DRM plugin for the open source driver so they can sell the open-source driver within android stapled pcs because the catalyst is shit.

google already dream about a copy-protection drm system in the official HTML5 standard to force all open-source people into a closed source world.

[fritsch]

While implementing xvba support for xbmc, we came to the following list about what is still missing:
http://ati.cchtml.com/show_bug.cgi?id=448

For long term xvid/mpeg-4 support would also be great, but - there is not so many features we miss in order to have a really good looking product for the htpc market.

[sylware]

Well... the only interest of UVD is the W saved for battery based systems.

We should not forget the hardware programing manual of the discret dma engines too, except if it's decided to remove them and use "shaders with the bus aperture" for good.

But right now... we need GCN support in open source drivers: I want to buy an eyefinity DCE5 and GCN chip based board with enough mini-displayport connectors to fool around (HDMI is sh** since it's royalty based)... and to play some native GNU/Linux 3D games... like oil rush (and run the unigine benchmark ).

I read somewhere that the DCE5 displayport support was vastely improved? Magic atombios command table for displayport link training? Displayport audio? ;-)

[agd5f]

I read somewhere that the DCE5 displayport support was vastely improved?

All the Northern Islands chips are DCE5. See the "Radeon Display Hardware" section of this page (http://wiki.x.org/wiki/RadeonFeature) for more on DCE5 features.

[sylware]

All the Northern Islands chips are DCE5...

oops... if I recall well, it was about the DCE of the southern islands chips. I cannot find the www page again!

[jonwil]

2 points:
1.Releasing the UVD as a binary blob or anything obfuscated wont happen because any blob that small would be too easy to reverse engineer
2.Its not about DRM as such, its about the fact that if AMD documents this hardware, Microsoft will revoke their "protected content can play on this hardware" approval (block the digital signatures of the drivers or whatever) because getting that approval means the hardware has to be undocumented to prevent hackers hacking it.

Anyone know what the situation is regarding Intel cards? Do they have dedicated silicon for decoding video? Is the driver support open source on Linux? If so, what has Intel done differently that makes it possible to open-source their support?

[bridgman]

....because getting that approval means the hardware has to be undocumented to prevent hackers hacking it.

Not really... it just means that hackers shouldn't be able to hack it, ie certification requires a certain level of robustness. Depending on the hardware specifics, that might allow documentation or might not.

[Qaridarium]

Not really... it just means that hackers shouldn't be able to hack it, ie certification requires a certain level of robustness. Depending on the hardware specifics, that might allow documentation or might not.

this point of view is complete Wong

the only purpose is to disadvantage other operating systems like Linux because they know that its incompatible with the open-source mentality.

All other purposes are just Lies and FUD !