Page 1 of 4 123 ... LastLast
Results 1 to 10 of 63

Thread: Jolla Brings Wayland Atop Android GPU Drivers

Hybrid View

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

    Default Jolla Brings Wayland Atop Android GPU Drivers

    Phoronix: Jolla Brings Wayland Atop Android GPU Drivers

    Jolla, the start-up company built around former Nokia N9 engineers developing the Sailfish OS for mobile phones, might be dating Wayland. Jolla's Chief Research Engineer has made it possible to run Wayland atop Android GPU drivers. Additionally, it's being done with glibc rather than Android's Bionic libc derivative...

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

  2. #2
    Join Date
    Apr 2010
    Posts
    100

    Default

    probably wrong but feels a bit that Mir was the wakeup call that Wayland needed. Now keep the momentum

  3. #3
    Join Date
    Feb 2011
    Posts
    1,068

    Default

    Quote Originally Posted by Xilanaz View Post
    probably wrong but feels a bit that Mir was the wakeup call that Wayland needed. Now keep the momentum
    You need to read the blog post. This is the guy who developed the android interface that Mir is using. And it was not intended for Mir, Canonical just forked it without even telling him. This was not a brilliant move by Canonical at all, as always is was someone else's work, but as always people assume it was Canonical's because Canonical doesn't go out of their way to give credit to those who actually do the work.

    To put it another way: the only reason to use Mir never existed to begin with, and the Mir developers knew it from the moment they started using this library.

  4. #4
    Join Date
    Jan 2013
    Posts
    1,116

    Default

    That article really made me laugh. Canonical is just pathetic.

  5. #5
    Join Date
    Jan 2013
    Posts
    1,446

    Default

    That's it, it's decided, my next phone will run Sailfish

  6. #6

    Default

    Getting unified Android/Linux/ChromeOS drivers would be ideal, whoever manages to bring us that. It should've been Google's project from day one of Android, but I guess it wasn't their priority, which is too bad because that has led to some of the biggest fragmentation issues of Android.

  7. #7
    Join Date
    Oct 2011
    Location
    Germany
    Posts
    238

    Default

    Quote Originally Posted by Krysto View Post
    Getting unified Android/Linux/ChromeOS drivers would be ideal, whoever manages to bring us that. It should've been Google's project from day one of Android, but I guess it wasn't their priority, which is too bad because that has led to some of the biggest fragmentation issues of Android.
    driver != driver the problem are the driver that are not part of the kernel, eg the drivers that run in userspace. This isn't the problem with wayland as it requires no user space drivers like X11.

  8. #8
    Join Date
    Jul 2012
    Posts
    63

    Default

    Wayland is actually making some progress, perhaps the announcement of Mir made the Wayland guys move a bit faster. Hopefully we will have a fully functional Wayland desktop BEFORE the year 2025 now! I would like to see Wayland overtake X instead of Mir, but seriously it's all going to come down to performance & stability and not open source politics.

  9. #9
    Join Date
    Oct 2011
    Posts
    38

    Default

    Quote Originally Posted by Krysto View Post
    Getting unified Android/Linux/ChromeOS drivers would be ideal, whoever manages to bring us that. It should've been Google's project from day one of Android, but I guess it wasn't their priority, which is too bad because that has led to some of the biggest fragmentation issues of Android.
    But only if the drivers were not closed. If closed drivers goes mainstream in linux, you can also use windows.

  10. #10
    Join Date
    Sep 2010
    Posts
    655

    Default

    Quote Originally Posted by Krysto View Post
    Getting unified Android/Linux/ChromeOS drivers would be ideal, whoever manages to bring us that. It should've been Google's project from day one of Android, but I guess it wasn't their priority, which is too bad because that has led to some of the biggest fragmentation issues of Android.
    Not going to happen.

    Not all features from mobile are needed on desktop (OpenVG?)
    Not all features from desktop are wonted on mobile. In fact some are most unwelcome (power hungry ones).

    Some well defined and limited feature set that would be supported across devices and gpus is probable though.

Posting Permissions

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