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

Thread: Ubuntu Touch/Tablet Is Using SurfaceFlinger

Hybrid View

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

    Default Ubuntu Touch/Tablet Is Using SurfaceFlinger

    Phoronix: Ubuntu Touch/Tablet Is Using SurfaceFlinger

    One of the first things I wanted to check when installing the Ubuntu Touch/Tablet Developer Preview is seeing what display server / compositor was in use by this newest Ubuntu Linux variant. Wayland? Compiz on X?..

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

  2. #2
    Join Date
    Dec 2009
    Posts
    321

    Default

    Disappointing, since it means they won't put any effort in advancing Wayland on mobile.

  3. #3
    Join Date
    Jun 2009
    Posts
    519

    Default

    Quote Originally Posted by shmerl View Post
    Disappointing, since it means they won't put any effort in advancing Wayland on mobile.
    At least they apparently decided not to roll their own display server. That would have been much much worse.

    And I don't see anything wrong with SurfaceFlinger since it's already optimized for mobile. Wayland can stay on desktops and notebooks. AMD's Bridgman already claimed that the OSS graphics drivers should be workable on any display server.

  4. #4
    Join Date
    Jan 2009
    Posts
    1,305

    Default

    Quote Originally Posted by Sonadow View Post
    At least they apparently decided not to roll their own display server. That would have been much much worse.

    And I don't see anything wrong with SurfaceFlinger since it's already optimized for mobile. Wayland can stay on desktops and notebooks. AMD's Bridgman already claimed that the OSS graphics drivers should be workable on any display server.
    I'm not sure how optimized it is. Did you see how laggy both android and ubuntu are?
    I recall a really great white paper by an Intel engineer about touch latency in android. I don't recall how much was due to the compositor but I bet it's more than is present in iphone.

    Quote Originally Posted by Sonadow View Post
    I have full faith Nvidia will port their proprietary driver over to Wayland once the majority of big name distributions adopt it. Obviously they are not going to be interested in building Wayland compatibility into the binary driver now when X is still so deeply entrenched as the de facto display server.
    Once RH and Suse move to Wayland you'll see the nvidia driver, at the latest. So, say, another three years?

  5. #5
    Join Date
    Jun 2009
    Posts
    519

    Default

    Quote Originally Posted by liam View Post


    Once RH and Suse move to Wayland you'll see the nvidia driver, at the latest. So, say, another three years?
    How optimistic.

    I was thinking 5 - 7 years.

    That said, i still don't know (and partly don't dare) how to try out using Wayland as a display server even though packages for it exist in Fedora 17 and 18 (and Mageia 2). Anyone got any idiot-friendly instructions to try out Wayland without borking up the systems?

    Or should I just wait until Wayland is deemed 'usable' enough for the distributions to start using it as the default display server over X?

  6. #6
    Join Date
    Jan 2009
    Posts
    1,305

    Default

    Quote Originally Posted by Sonadow View Post
    How optimistic.

    I was thinking 5 - 7 years.

    That said, i still don't know (and partly don't dare) how to try out using Wayland as a display server even though packages for it exist in Fedora 17 and 18 (and Mageia 2). Anyone got any idiot-friendly instructions to try out Wayland without borking up the systems?

    Or should I just wait until Wayland is deemed 'usable' enough for the distributions to start using it as the default display server over X?
    The estimate comes from RH, primarily, as I understand they release a new major version every 2.5 years, or so, and they're about a year away from releasing RHEL7, IIRC.
    Wayland should be quite safe to run once XWayland works properly.
    As for trying it out, you can either get one of the various isos (like Rebecca Black), or shut down X, and start wayland from one of the VTs. It shouldn't be that scary
    Having said that, you probably don't want to run it as your default display server yet. At least wait for XWayland.

    Quote Originally Posted by BO$$ View Post
    You should wait until they call it usable and then some another 2 years. What I've seen as 'usable' these days isn't actually usable until after a couple of years of more development.
    This isn't a file system, so it's not QUITE so life and death

  7. #7
    Join Date
    Dec 2011
    Location
    Basement
    Posts
    389

    Default

    Quote Originally Posted by Sonadow View Post
    How optimistic.

    I was thinking 5 - 7 years.
    You forgot the Intel factor.
    https://mail.gnome.org/archives/gtk-.../msg00119.html

  8. #8
    Join Date
    Dec 2012
    Posts
    196

    Default

    The design philosphy behind Wayland is quite similar to SurfaceFlinger. Then the best thing to to ditch Wayland, embrace and leverage the work done by Google and extend it to support a traditional desktop window manager and XSurfaceFlinger to support legacy X apps.

    Wayland has a chicken egg problem and convincing Nvidia/ATI to provide drivers for SurfaceFlinger would be much easier than for Wayland.

  9. #9
    Join Date
    Dec 2008
    Location
    San Bernardino, CA
    Posts
    231

    Default

    Michael,

    Can you please include Nexus 4 in your upcoming Linux benchmarks of Nexus 7 and Nexus 10.

  10. #10

    Default

    I don't think Canonical is doing a good choice using Android components for its Ubuntu tablet/phone. The problem with android is that it is developed behind closed doors and every now and then the code is dropped. Google will always have a technological advantage, Canonical will be left out of the development, and google will have the power to just kick Canonical out of the market, since Canonical has not the man power to fork android components and develop them. I hope this is not their long term plan.

    But even in the short term plan, why not choosing something like mer? Plasma active is going to be shipped on the vivaldi tabled and it will be based on mer! I really don't understand this choice.... in any case I hope we will have yet another alternative to the standard android OS..... I really don't like it

Posting Permissions

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