Page 1 of 3 123 LastLast
Results 1 to 10 of 33

Thread: Why Canonical Is Using Android Drivers For Ubuntu Mir

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,541

    Default Why Canonical Is Using Android Drivers For Ubuntu Mir

    Phoronix: Why Canonical Is Using Android Drivers For Ubuntu Mir

    With Canonical's Mir Display Server for future releases of Ubuntu Linux, they are supporting Android's graphics layer and drivers rather than inventing their own solution, trying to push X.Org drivers, or demanding mobile graphics drivers modelled after the desktop Linux graphics stack. Why did they do this? Here's an explanation...

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

  2. #2
    Join Date
    Jan 2011
    Posts
    457

    Default

    The only way it up.

  3. #3
    Join Date
    Sep 2010
    Posts
    76

    Default

    Quote Originally Posted by phoronix View Post
    Phoronix: Why Canonical Is Using Android Drivers For Ubuntu Mir

    With Canonical's Mir Display Server for future releases of Ubuntu Linux, they are supporting Android's graphics layer and drivers rather than inventing their own solution, trying to push X.Org drivers, or demanding mobile graphics drivers modelled after the desktop Linux graphics stack. Why did they do this? Here's an explanation...

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

    Did the "we are working with hardware vendor for Mir's support in drivers" just become "hardware vendors are not responding our calls let's just use Android drivers instead" ?

  4. #4

    Default

    I can't help but wonder if by the time Mir is stable that Intel Atom with HD graphics will be the "OMG gotta have it" of tablets.

  5. #5
    Join Date
    Oct 2008
    Posts
    3,076

    Default Why not just use SurfaceFlinger

    I mean, it's clear at this point the whole Ubuntu project is focused on phone/tablets. And their essentially trying to build as much off Android as possible with different systems and APIs.

    So what is it that SurfaceFlinger doesn't provide that Mir will?

  6. #6
    Join Date
    Jan 2012
    Posts
    57

    Default

    Quote Originally Posted by smitty3268 View Post
    So what is it that SurfaceFlinger doesn't provide that Mir will?
    Desktop support.

    Obviously if even Google couldn't force hardware vendors to provide open drivers, using the existing Android interfaces was the only sane choice for rapid release, but Ubuntu's NIH syndrome still disgusts me. I'm happy to see other, properly open, projects drag their heels merging Mir support.

    And, correct me if I'm wrong, but weren't nVidia/ATI just talking about implementing OpenGL ES support, rather than Mir support specifically?

  7. #7
    Join Date
    Oct 2008
    Posts
    3,076

    Default

    Quote Originally Posted by pdffs View Post
    And, correct me if I'm wrong, but weren't nVidia/ATI just talking about implementing OpenGL ES support, rather than Mir support specifically?
    They haven't said anything about Mir at all. NVidia has said they were part way along getting an EGL driver out, for Wayland. And Canonical has said they are in talks with both NVidia and AMD, but we've heard nothing from the other direction.

    I highly suspect whatever EGL driver comes out will support both Wayland and Mir, with minimal changes necessary. And if it doesn't, i highly suspect Mir will change until it does, because those drivers are going to target Wayland first and foremost because they are meant for the enterprise versions that end up in corporations, not tablets or desktops.
    Last edited by smitty3268; 04-09-2013 at 12:23 AM.

  8. #8
    Join Date
    Jan 2011
    Posts
    100

    Default

    Quote Originally Posted by pdffs View Post
    [...] but Ubuntu's NIH syndrome still disgusts me. [...]
    Why is it NIH if they reuse the android drivers? Isn't that like the antithesis of NIH?

  9. #9
    Join Date
    Jul 2008
    Posts
    773

    Default

    Quote Originally Posted by pdffs View Post
    Obviously if even Google couldn't force hardware vendors to provide open drivers,
    Could you please share the link to the source of that claim? I dont think they at least care even a bit about opensource drivers. If not the oposite.



    To the news, I found the title funny, because I did ask myself never that question, but I did not read here anything about that Mir will be compatible or uses android driver architecture.

    So I would have liked as title more something like: "Canonicals Mir is using Android drivers" or somethign like that.
    I need no Canonical dev say some marketing blabla about it, to know why they want that.
    If you as company care 0 about free software, free drivers and so on, of course you would like to be able to use all the arm non-free drivers.

    If you have not to sell your "product" because of openess or freeness, you just can switch from closedsource support drivers (too) into closedsource drivers only from now on, a complete closed plattform.
    From now on I think I call Ubuntu not anymore (GNU)Ubuntu/Linux, but Ubuntu/Android so Ubuntu is now a Android distribution, basicly.

    And they should not say some stupid about the architecture, its because they can use the closed source drivers, thats the reason the only reason for that move.

    So I am to lazy to scandalize that, I will make my desition based on that desitions and maybe some are able to guess what that is.
    Last edited by blackiwid; 04-09-2013 at 11:28 AM.

  10. #10
    Join Date
    Jul 2011
    Posts
    44

    Default

    Quote Originally Posted by phoronix View Post
    Phoronix: Why Canonical Is Using Android Drivers For Ubuntu Mir

    With Canonical's Mir Display Server for future releases of Ubuntu Linux, they are supporting Android's graphics layer and drivers rather than inventing their own solution.... Why did they do this?

    http://www.phoronix.com/vr.php?view=MTM0NjQ
    That article is a pretty long explanation of a simple reason: Mobile drivers are much more often than not closed source, especially GPU drivers. Canonical seems to try to come up with all kinds of technical reasons like "good power management" and "rock solid" and blabla, but the truth is, they simply just didn't have any other choice.

Posting Permissions

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