Announcement

Collapse
No announcement yet.

Mir Support Not Merged For Mesa 9.2

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

  • 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
    So they want everyone (DEs etc.) to embrace Mir without having any real upstream support? lol

    Comment


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

      Comment


      • #4
        Don't think Mesa (or pretty much anyone else) is interested in supporting Mir and pulling Mir code into their code base.

        Mir is Canonical's in-house developed Ubuntu-only software without community interaction, feedback or support.
        The community doesn't care for Mir, they want Wayland.

        Wayland is by the community for the community. It is by us, for us.
        Mir on the other hand is by Canonical for Canonical.

        Comment


        • #5
          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.

          Comment


          • #6
            They obviously should fork mesa! With this fork, they will have more control!
            A fork of the kernel should be a good idea too!

            Comment


            • #7
              Originally posted by gufide View Post
              They obviously should fork mesa! With this fork, they will have more control!
              A fork of the kernel should be a good idea too!
              I also don't get it why they wait for NVIDA and AMD to make new drivers. Why don't they write their own drivers? Just fork nouveau.

              Comment


              • #8
                I think Canoncial should drop 13.10. They should fully focus to give a good experience on Ubuntu 14.04 and for that improve Mir and the driver situations.

                Comment


                • #9
                  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, 11:12 AM.

                  Comment


                  • #10
                    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).

                    Comment


                    • #11
                      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"

                      Comment


                      • #12
                        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)

                        Comment


                        • #13
                          Originally posted by blackout23 View Post
                          I also don't get it why they wait for NVIDA and AMD to make new drivers. Why don't they write their own drivers? Just fork nouveau.
                          All of you are forgetting the most important part: spreading FUD to the projects they fork

                          Originally posted by dh04000 View Post
                          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.
                          There's a quite complex ecosystem. Collaborate is not only submitting code. If you do something that could easily fuck up all of the other projects, you are not collaborating, most likely you are predating, or at least trying to.
                          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.
                          Overforking, with the fragmentation it creates, is one of the most important problems on FOSS. Selective collaboration is a hackfix for that problem, and nothing else. Heck, if Ubuntu lovers can't stop saying "it's a free world, anybody can code what they want", well, any project is free to accept patches selectively, it's a free world, you can fork, the same you say about Mir. Also, it's still better to have GPL code. If a closed source app doesn't accept your patch (which I wonder how you did without the code anyway), that's it, end of the line. If a GPL one doesn't, you can fork. People might pay attention, or might not. It's not less a problem for fragmentation, but the harm is done already, and they should have seen it coming. Being free software doesn't mean they have to be liked, and they should have weighted that possibility. Also, keep in mind that the fact they screwed over Wayland isn't the most inspiring thing for collaborating with Canonical.

                          Originally posted by DanL View Post
                          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).
                          First point, yes, is news unworthy, and they will probably accept the patches.
                          However, everything you say is stated on the article, and points the problems: they are on their own, and most likely they don't know in depth the mesa code base.

                          About the haters, not everyone are Canonical haters. Some of us just have personal opinions about different things. If I'd hate Canonical, I wouldn't use any of their products, nor would I test their alphas and betas. This said, I think Mir is an awful choice. They didn't share their needs, and then they started blaming other projects for not fulfilling them, for a start. Then, this needs were actually fulfilled by the time they did their announcement. An open company that takes such a huge decision inside close doors is not really that open. I could keep all day. Then, they throw the testing on the end users. You see why I don't think this is going well? These are all bad choices, and I don't see how pointing this out turns me into a hater. I'm a user, and I will most likely be affected by their choices in one way or another.

                          Comment


                          • #14
                            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.

                            Comment


                            • #15
                              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

                              Comment

                              Working...
                              X