Catalyst 10.1 "faster 2D"?

[rohcQaH]

March - Support for Ubuntu 9.10

nah, that's for october. *takes cover*

[Silverthorn]

I doubt it was intended to be that specific

Couldn't resist although I just noticed the following...

nah, that's for october. *takes cover*

Hey, I didn't notice the version number until I read your post. Ubuntu 9.10 is already out. So is OpenSUSE. I read it just as next Ubuntu version but that should have been 10.04!

Something tells me that this so called "document" might be pretty old.

[RealNC]

The linked article actually says "AMD has supplied us with a document giving information on the improvements that will be implemented over the course of the next months in Catalyst drivers:"

I don't think it mentions the Cat 10.1 release anywhere, does it ?

As if it wasn't bad enough. The list is embarrassingly short even if it were for 10.1.

[tball]

As if it wasn't bad enough. The list is embarrassingly short even if it were for 10.1.

Well thats NEW features. Actually the fglrx already include the most commonly needed features. They just need to mature alittle (like xvba).

[RealNC]

xvba is not intended to be used in the way you guys use it. It's not even supported by AMD. There's nothing to mature.

[gbeauche]

xvba is not intended to be used in the way you guys use it. It's not even supported by AMD. There's nothing to mature.

It is supported by AMD and it has to mature. There is no other secret XvBA run-time library. So, what you have in the Catalyst drivers is what others have too, embedded customers or not.

[RealNC]

If you think so.

[mirv]

xvba is supported by AMD - but not on a desktop pc. It's intended for their embedded market. This was made clear from the very first announcement of it - people seem to have assumed that it would also be released for a pc, but that was never stated by AMD.

[bridgman]

Just to be clear, XvBA was conceived and implemented for our embedded customers, but we understand there is interest in having similar capabilities on consumer PCs.

Making XvBA work well for our embedded customers is our first priority, however as gbeauche said there's only one XvBA so any improvements and fixes we make for embedded use will generally benefit everyone. The "embedded vs consumer PC" distinction really affects *which* issues get looked at first.