Page 7 of 10 FirstFirst ... 56789 ... LastLast
Results 61 to 70 of 95

Thread: Intel Mesa Gives Problems With KDE's KWin, Again

  1. #61
    Join Date
    Oct 2007
    Location
    Under the bridge
    Posts
    2,149

    Default

    Quote Originally Posted by mat69 View Post
    What kind of racist remark are you talking of?

    Imho his mail is indeed way too long and might apear arrogant instead of solution oriented. I doubt that devs who themselves have to cope with rare spare time they can invest in their projects are willing to read long rants in this regard.
    "We Germans are direct and speak the truth" etc. Such remarks have no place in (what should be) a technical discussion.

  2. #62
    Join Date
    Oct 2009
    Posts
    111

    Default

    Quote Originally Posted by BlackStar View Post
    "We Germans are direct and speak the truth" etc. Such remarks have no place in (what should be) a technical discussion.
    Well but it is not racism per se. Though the "speak the truth" is in fact crap.

  3. #63
    Join Date
    Feb 2011
    Posts
    1,298

    Default

    Quote Originally Posted by bridgman View Post
    This issue comes up every few months. The core problem here is that the KDE devs were writing new code which used OpenGL features that were just being implemented in the open drivers. Nothing wrong with that in principle but it requires fairly close communication between app and driver developers so everyone understands what should and should not work.
    Except that isn't what happened. The features that broke had been working for several releases by that point. They hadn't been significantly changed.

  4. #64
    Join Date
    Jul 2010
    Posts
    69

    Default

    Using Mesa renderer string for determining features is the same stupid thing as using UserAgent string in browsers. Just test functionality and performance experimentally at runtime if needed.

  5. #65
    Join Date
    Jun 2009
    Posts
    2,933

    Default

    Quote Originally Posted by baryluk View Post
    Using Mesa renderer string for determining features is the same stupid thing as using UserAgent string in browsers. Just test functionality and performance experimentally at runtime if needed.
    The functionality tests caused the system to crash. That's why drivers were blacklisted -- even testing functionality and performance caused them to crash.

  6. #66
    Join Date
    Jul 2008
    Posts
    1,731

    Default

    isn't it great? They do a stupid change (idiotic even) and when people (rightfully) complain, they shut them down.

    And people are surprised that there aren't more mesa/driver devs.

    Btw, which users are more important than the composite using window managers?
    Games? Surely not - since opensource drivers, especially intel's suck way to much for that. CAD? Don't try to be funny. There is a reason workstation drivers (from amd and nvidia) are seldomly updated and certified to run workstation applications.
    So what is left - xmms ogl analyzer plugin?

  7. #67

    Default

    Quote Originally Posted by energyman View Post
    isn't it great? They do a stupid change (idiotic even) and when people (rightfully) complain, they shut them down.

    And people are surprised that there aren't more mesa/driver devs.

    Btw, which users are more important than the composite using window managers?
    Games? Surely not - since opensource drivers, especially intel's suck way to much for that. CAD? Don't try to be funny. There is a reason workstation drivers (from amd and nvidia) are seldomly updated and certified to run workstation applications.
    So what is left - xmms ogl analyzer plugin?
    It seems they care only what Red Hat does, my friend. Some of them were saying they're testing drivers to work with gnome shell well. Since gnome shell sucks and even Ubuntu won't ship it, it doesn't even matter if OS drivers works well with it or not. Others have to suffer, because of idiocy.

  8. #68
    Join Date
    Oct 2007
    Location
    Under the bridge
    Posts
    2,149

    Default

    Quote Originally Posted by mat69 View Post
    Well but it is not racism per se. Though the "speak the truth" is in fact crap.
    Positive racism is still racism.

  9. #69
    Join Date
    Jan 2008
    Location
    Have a good day.
    Posts
    678

    Default

    Quote Originally Posted by BlackStar View Post
    Plus, his racist remark was very ill-conceived.

    Thumbs up for spotting it.


    Quote Originally Posted by energyman
    Btw, which users are more important than the composite using window managers?
    Games? Surely not - since opensource drivers, especially intel's suck way to much for that. CAD? Don't try to be funny. There is a reason workstation drivers (from amd and nvidia) are seldomly updated and certified to run workstation applications.
    So what is left - xmms ogl analyzer plugin?
    If I look at my use case, window managers are pretty low down the list of stuff that needs care from mesa, because I don't use a composite desktop. Though to be fair, this is a chicken and egg problem, I would probably use kwin's compositor if it performed well enough with my hardware/drivers...But yeah, I asked myself the same question, who are the most important users of mesa?

  10. #70
    Join Date
    Feb 2011
    Posts
    1,298

    Default

    Quote Originally Posted by kraftman View Post
    It seems they care only what Red Hat does, my friend. Some of them were saying they're testing drivers to work with gnome shell well. Since gnome shell sucks and even Ubuntu won't ship it, it doesn't even matter if OS drivers works well with it or not. Others have to suffer, because of idiocy.
    Are you serious? They are perfectly willing to test Gnome but flat-out refuse to test KDE? So they work hard to make sure Firefox works, work hard to make sure Gnome works, but knowingly break KDE?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •