Page 1 of 2 12 LastLast
Results 1 to 10 of 44

Thread: Mir Support Not Merged For Mesa 9.2

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    13,405

    Default Mir Support Not Merged For Mesa 9.2

    Phoronix: Mir Support Not Merged For Mesa 9.2

    While the very exciting Mesa 9.2 release is expected next month and its code will be branched soon, one feature that looks unlikely to be merged in time is any support for Canonical's Mir Display Server...

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

  2. #2
    Join Date
    Jul 2012
    Posts
    616

    Default

    So they want everyone (DEs etc.) to embrace Mir without having any real upstream support? lol

  3. #3
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    879

    Default

    Quote Originally Posted by blackout23 View Post
    So they want everyone (DEs etc.) to embrace Mir without having any real upstream support? lol
    I'm pretty sure Canonical will start pointing fingers at upstream soon, accusing them of not collaborating.

    It's their own fault, playing foul is not easily forgiven.

  4. #4
    Join Date
    Aug 2012
    Posts
    418

    Default

    Quote Originally Posted by entropy View Post
    I'm pretty sure Canonical will start pointing fingers at upstream soon, accusing them of not collaborating.

    It's their own fault, playing foul is not easily forgiven.

    Project A: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project X, so if we don't its their fault not us.

    Project B: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project A, so if we don't its their fault not us.

    Project C: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project B, so if we don't its their fault not us.

    Project D: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project C, so if we don't its their fault not us.

    Rince, Wash, Repeat.


    If you don't collaborate with others, you have no one to blame but yourself. Selectve collaboration is the death of FOSS. Looking down GPL code to your selected few poisions GPL code and makes it no better than non-GPL code.
    Last edited by dh04000; 07-11-2013 at 11:12 AM.

  5. #5
    Join Date
    Oct 2007
    Posts
    1,185

    Default

    Quote Originally Posted by dh04000 View Post
    Project A: Look Canonical doesn't collaborate with anyone. They submitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project X, so if we don't its their fault not us.
    It's not fair, but as they say, "Your reputation precedes you." Canonical got a bad reputation by deviating from Gnome and then making something very much like Gnome shell.

    As an old-school basketball fan, I'm reminded of Dennis Rodman and his "reputation" fouls (he never got the benefit of the doubt on close calls)

  6. #6
    Join Date
    Jul 2013
    Location
    USA
    Posts
    715

    Default

    Quote Originally Posted by entropy View Post
    I'm pretty sure Canonical will start pointing fingers at upstream soon, accusing them of not collaborating.

    It's their own fault, playing foul is not easily forgiven.
    Just Like they did to KDE Gnome Xfce LXDE Developers Etc?

    Mesa is being Developed for Wayland and for them wanting for it to be developed for Mir is Funny this is one of the Biggest Fails i seen in a long time "If you build it, they will come"


  7. #7
    Join Date
    Oct 2007
    Posts
    1,185

    Default

    Quote Originally Posted by LinuxGamer View Post
    Mir is Funny this is one of the Biggest Fails i seen in a long time]
    This isn't 4chan. Go back to your games.

  8. #8
    Join Date
    Jun 2009
    Posts
    1,020

    Default

    Quote Originally Posted by DanL View Post
    This isn't 4chan. Go back to your games.
    well to be honest i doubt this patches will be accepted and is probable canonical got the idea already and won't bother anymore in trying

    1.) Mir is a single distro solution that im not sure mesa dev be eager to upstream
    2.) Nobody except canonical uses Mir, so the review process will be hard since mesa devs won't install Mir to test the patches
    3.) Who is going to maintain it? if that is not well defined no one will step to it fix it if it gets broken
    4.) Canonical send a patches already to mesa mailing list and those went straight to /dev/null

    Btw Michael is been reported Mir/Xmir is broken in radeon and nouveau drivers, maybe you should check it out as far as i care to look it only works on intel

  9. #9
    Join Date
    Oct 2007
    Posts
    1,185

    Default

    Quote Originally Posted by blackout23 View Post
    So they want everyone (DE's etc.) to embrace Mir without having any real upstream support? lol
    Where do you people get this stuff? All the article says is that Mir will not be ready for the Mesa 9.2 release. Most likely, Canonical will use Mesa 9.2 + their Mir patches for Ubuntu 13.10. By the next Mesa release point, the API should be stable and the code will be well-tested and ready for merging.

    This "news" is not newsworthy IMO (just gets the Canoncial haters worked up).

  10. #10
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    879

    Default

    Not sure the Mesa devs are eager to merge this.
    AFAIK, Canonical didn't get a single reply back in March.

Posting Permissions

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