Announcement

Collapse
No announcement yet.

Mesa Beginning To Need Application Workarounds

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

  • phoronix
    started a topic Mesa Beginning To Need Application Workarounds

    Mesa Beginning To Need Application Workarounds

    Phoronix: Mesa Beginning To Need Application Workarounds

    Now that Mesa is beginning to catch-up with support for newer versions of OpenGL and the OpenGL performance is slowly improving, with more games and applications beginning to work on this open-source graphics driver stack as a result, the need for application workarounds is becoming more prevalent...

    http://www.phoronix.com/vr.php?view=MTA0ODY

  • zerothis
    replied
    Originally posted by siride View Post
    You really want to make sure that nobody targets Linux, eh?
    You really want to make sure that Linux is as sloppy as Windows, eh?

    Leave a comment:


  • Ex-Cyber
    replied
    Originally posted by lopho View Post
    i think workarounds should be handled off-tree in a seperate package, maybe through api.
    that way its easy for users to choose if they want only specification compliance or compatibilty, maybe even easily switchable by configs files.
    Anholt's proposal already addresses that, I think. The idea is that although the workarounds are in the Mesa code base, they're individually enabled/disabled/mapped to applications via drirc. This is far better than a global "quirks mode / standards mode" switch.

    Leave a comment:


  • ssam
    replied
    i (half seriously) propose charity bug bounties.

    "I pledge to donate ?x to charity y when bug #z is fixed."

    This should help solve all the worlds problems.

    Leave a comment:


  • lopho
    replied
    i think workarounds should be handled off-tree in a seperate package, maybe through api.
    that way its easy for users to choose if they want only specification compliance or compatibilty, maybe even easily switchable by configs files.

    Leave a comment:


  • whizse
    replied
    Originally posted by curaga View Post
    Unigine folks already said these are fixed? Carry on on the general case though
    Depends if it just OilRush or if they are planning on releasing new versions of the benchmarks too.

    In other news, Super Meat Boy and Shank still doesn't run on Mesa out-of-the-box, because it is "asshole correct".

    Leave a comment:


  • curaga
    replied
    Unigine folks already said these are fixed? Carry on on the general case though

    Leave a comment:


  • DanL
    replied
    If it means bloating the code base and wasting precious dev hours on working around buggy programs, then I don't care if games target linux or not. Those games should be able to write good openGL-compliant code or they shouldn't bother.

    Leave a comment:


  • siride
    replied
    Originally posted by pingufunkybeat View Post
    It's not about perfection, it's about priorities.

    Closed drivers have more workarounds than the entire Mesa stack + all of the linux kernel tree. OpenGL compliance (and other things I mentioned) are not only more important IMHO, but also more realistic than duplicating all those workarounds.
    Well, if you don't want to duplicate the work of the closed source drivers, then we should just stop developing the Radeon and nVidia open source drivers, because the whole thing is a duplication. Do you want the Open Source drivers to work, or do you want to be able to claim some sort of moral high ground?

    If a couple of high-profile workarounds make it into the tree and don't cause an unmaintainable mess, I won't complain -- it's the developers' choice after all. I just don't think that Unigine demos are all that important compared to power saving, for example.
    True. Fixing every little bug is unnecessary (and wouldn't happen anyway because of lack of manpower).

    Leave a comment:


  • pingufunkybeat
    replied
    Originally posted by siride View Post
    I guess you miss the point. The point is that we can wait for perfection before we go on to fix these incompatibilities.
    It's not about perfection, it's about priorities.

    Closed drivers have more workarounds than the entire Mesa stack + all of the linux kernel tree. OpenGL compliance (and other things I mentioned) are not only more important IMHO, but also more realistic than duplicating all those workarounds.

    If a couple of high-profile workarounds make it into the tree and don't cause an unmaintainable mess, I won't complain -- it's the developers' choice after all. I just don't think that Unigine demos are all that important compared to power saving, for example.

    Leave a comment:

Working...
X