It can not share that much code with win because 10-7 can decode h264 l 5.1 with vlc now. Never saw that on linux.
I've bought the Athlon II X4 600e (still waiting for delivery) - sucky price/performance ratio but promises a low power consumption and a low temperature. We will see...
Originally Posted by Dandel
That said, I want to put on the HTPC some dev tools (like Mercurial or Redmine) so it would be nice to offload to the GPU as much as possible.
The code is shared, they clearly don't have the resources like Intel or NVIDIA to write another core implementation from scratch for Linux. The fact you don't see the expected results on Linux doesn't mean the capability is not there... Linux support is "just glue code". That glue code can:
Originally Posted by Kano
1. not be available to Linux
2. be available to Linux and
2.1.1. by default
2.1.2. through a specific configuration
2.1.3. partially (missing cases in the implementation)
2.2. not working (bugs)
You have no means to be certain which case applies here though. i.e. you just can't say (1) because you don't see the expected results in VLC... Your conclusion, as stated in your quote, is innerly broken. You just can't say that. You can't define a supposed and absolute truth simply from an example. This is illogical. No matter we are talking about XvBA or not.
Look for other features of the driver, there are many symbols that can suggest X or Y but we can't be certain that (1), (2.1.1), (2.1.2), (2.1.3) or (2.2) applies to each simply by testing a random application.