| |||||||||||||
MeeGo to return next month with Jolla phone launch (The H)MeeGo to return next month with Jolla phone launch (The H)Posted Oct 10, 2012 22:37 UTC (Wed) by mjg59 (subscriber, #23239)In reply to: MeeGo to return next month with Jolla phone launch (The H) by shmerl Parent article: MeeGo to return next month with Jolla phone launch (The H)
That's not true at all. You've got a framebuffer and a GLES driver, which is what's always been the traditional graphics environment on embedded Linux.
(Log in to post comments)
MeeGo to return next month with Jolla phone launch (The H) Posted Oct 10, 2012 22:42 UTC (Wed) by shmerl (guest, #65921) [Link]
I mean useless out of the box (as in the KWin example above). I.e. with some serious work it can get better, but this work is not yet done, so end user can't simply take the existing mobile hardware and use it with non Android Linux distro. That was the point of the discussion above - i.e. splitting/duplication of effort (instead of sharing it).
MeeGo to return next month with Jolla phone launch (The H) Posted Oct 10, 2012 22:42 UTC (Wed) by swetland (subscriber, #63414) [Link]
The biggest headache here is probably that the opengl library is linked against bionic instead of glibc, but there are a number of ways you could shim that (with some creative linker trickery), since the actual OpenGL API/ABI is not dependent on libc's data structures. That's assuming you can't convince your SoC/GPU vendor to provide a version linked against glibc or staticly.
I can see that being annoying, but it's certainly not insurmountable.
|
|||||||||||||