Announcement

Collapse
No announcement yet.

Radeon Gallium3D Still Long Shot From Catalyst

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Qaridarium
    replied
    Originally posted by droidhacker View Post
    Yeah, catalyst sure does have a long way to go before it has the utility and openness of radeon-g3d.
    LOL you always can buy a faster card but you can't buy a open catalyst

    Leave a comment:


  • droidhacker
    replied
    Yeah, catalyst sure does have a long way to go before it has the utility and openness of radeon-g3d.

    Leave a comment:


  • DanL
    replied
    Debian has glx-alternative packages for allowing binary/open-source GPU drivers to coexist.

    Leave a comment:


  • rohcQaH
    replied
    Originally posted by log0 View Post
    Can someone point me to a tutorial of some sort on how to get the latest mesa stuff running next to catalyst. Are phoronix test setups documented?
    Three choices:
    * Use a distribution like gentoo that actually allows several libGL implementations to exist on your system. You need to load modules manually, and switch between two xorg.conf (i.e. forget XDM), but it can work.
    * Just install a separate OS on a different partition. Maybe play around with UnionFS to save space.
    * Try to manually install both on an unsupported system, go crazy over the conflicts that arise, eventually bork your system and reinstall.

    Honestly, if you have to ask how to do it, go with option 2. It's safer.

    Leave a comment:


  • Drago
    replied
    Michael, where is the Doom3 test?
    I still consider this wide gap between r600g and Catalyst on higher res/quality to be due to still missing optimizing shader compiler.
    At lower res/quality GPU can keep with unoptimized shaders, but with lots of pixels the game changes. What happened with Vadim Girlin's initiative on that?

    nvidia had hardware scheduler so far, and that is the reason for better nouveau speed, event unsupported by nvidia, but now with kepler, they go AMD route, with software scheduler in the driver ( at least thats what anandtech says ).

    Leave a comment:


  • log0
    replied
    Thanks for the updated comparison Michael!

    I know I am maybe asking too much. But I think it would be quite interesting to see traces(apitrace supports CPU profiling) of the benchmarks for the very slow results at least, just to get a better idea where the binary drivers are faster.

    Btw I think one could actually use api traces of games as benchmarks. This would additionally ensure that the same call paths are executed, no fall-backs or workarounds for specific hardware taken.

    PS:
    Can someone point me to a tutorial of some sort on how to get the latest mesa stuff running next to catalyst. Are phoronix test setups documented?

    Leave a comment:


  • anarki2
    replied
    What a surprise...

    Leave a comment:

Working...
X