Announcement

Collapse
No announcement yet.

Canonical Posts 15 Mesa Patches To Support Mir

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

  • Canonical Posts 15 Mesa Patches To Support Mir

    Phoronix: Canonical Posts 15 Mesa Patches To Support Mir

    Canonical is back to trying to get upstream Mesa/Gallium3D to support their Mir Display Server. In their current form, the support comes across 15 patches for bringing up the Mir EGL platform...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    I hope the Mesa team rejects the patches.

    Canonical gave a big fuck you to the Linux community for going with their own inhouse display server which causes fragmentation.

    Mesa should give a big fuck you to Canonical by rejecting their Mir patches.


    Sorry Canonical, but Wayland is the future.

    Comment


    • #3
      I think they'll accept the patches, i don't know why. Call it a sensation.

      Comment


      • #4
        Originally posted by synaptix View Post
        I hope the Mesa team rejects the patches.

        Canonical gave a big fuck you to the Linux community for going with their own inhouse display server which causes fragmentation.

        Mesa should give a big fuck you to Canonical by rejecting their Mir patches.


        Sorry Canonical, but Wayland is the future.
        Whatever happened to Linux being about choice? If a company wants to create their own display server, what's wrong with that? We should start putting restrictions on what display server you can use in Linux? That surely sounds pretty restrictive.

        Mir and Wayland are both the future.

        Should we start hating on Google now for not using Xorg or Wayland for Android and instead making their own?
        Last edited by Britoid; 20 July 2013, 09:46 AM.

        Comment


        • #5
          Originally posted by synaptix View Post
          Canonical gave a big fuck you to the Linux community for going with their own inhouse display server which causes fragmentation..
          While it's true, that Canonical started all this, the same could be said vice versa about the Linux Community ever since Ubuntu started. If we really get fragmentation it's the fault of both not being able to work with each other, but instead blaming and rejecting (although most of the blame and rejections don't come from Canonical).

          Comment


          • #6
            Originally posted by synaptix View Post
            I hope the Mesa team rejects the patches.

            Canonical gave a big fuck you to the Linux community for going with their own inhouse display server which causes fragmentation.

            Mesa should give a big fuck you to Canonical by rejecting their Mir patches.


            Sorry Canonical, but Wayland is the future.
            Their choices don't effect you in the slightest, so why all the vitriol?

            And you should stop the swearing, this is a SFW forum after all.

            Comment


            • #7
              Originally posted by alexThunder View Post
              While it's true, that Canonical started all this, the same could be said vice versa about the Linux Community ever since Ubuntu started. If we really get fragmentation it's the fault of both not being able to work with each other, but instead blaming and rejecting (although most of the blame and rejections don't come from Canonical).
              The problem is Canonical does not communicate with the community and its only getting worse they stated at the end of last year they will no longer dicuss future projects publicly.
              The reason people are so mad at Canonical about Mir is they said they were going to use Wayland then started development of Mir behind closed doors and then suddenly announced it while saying they needed to use it because Wayland couldnt do certain things, however not once did they talk to the Wayland devs about these missing futures and as it turns out they were not missing at all.

              So not I dont think the same could be said about the Linux community. Canonical has no interest working with others, just look at how much they contribute to upstream projects diddly squat.

              Comment


              • #8
                As an active radeon developer my first question is why the heck they want to change our kernel driver?

                The command submission and buffer sharing interfaces are quite well defined and work perfectly for both X and Wayland.

                Well we will probably see,
                Christian.

                Comment


                • #9
                  Android is developed behind closed doors too...

                  Comment


                  • #10
                    Originally posted by timothyja View Post
                    The problem is Canonical does not communicate with the community and its only getting worse they stated at the end of last year they will no longer dicuss future projects publicly.
                    The reason people are so mad at Canonical about Mir is they said they were going to use Wayland then started development of Mir behind closed doors and then suddenly announced it while saying they needed to use it because Wayland couldnt do certain things, however not once did they talk to the Wayland devs about these missing futures and as it turns out they were not missing at all.

                    So not I dont think the same could be said about the Linux community. Canonical has no interest working with others, just look at how much they contribute to upstream projects diddly squat.
                    Canonical say to upstream you will do are bidding upstream Say's LOL you dont pay us

                    Comment

                    Working...
                    X