Just a quick heads up on Sailfish development progress. (outside Jolla of course)

It’s getting started already, doesn’t it? it’s a sign! We will see Sailfish OS on so many ARM based devices. So cool!

So I have been informed by a bloke on Twitter named Martin Brook (@vgrade) who claimed that he got Sailfish OS up and running on a libhybris enabled ARM based cubieboard2.

What is libhybris : Hybris is a solution that commits hybris, by allowing us to use bionic-based HW adaptations in glibc systems.

Or in other words (According to Wikipedia) : Hybris or libhybris is a compatibility layer for computers running GNU-compatible Linux distributions to load software written for Bionic-based Linux systems – mainly Android libraries and device drivers.

So basically it is an open source hardware if you want to put it in easy words. Turned out to be wrong.

sailfish OS on libhybris enabled cubieboard2 http://t.co/yRCzwNSRbW — Martin Brook (@vgrade) October 25, 2013

It’s pretty early stage but everything has a start point, right? So guess what? Our beloved Nokia N9 is ARM based… You got anything from that? 😉

Ah before I forget there was also a video of a Sony device (Not sure if it’s an Xperia T/TX or what! They all look the same! 😀 ) also on twitter, from Dmitry Panfilov (@energycsdx)

No specific details other than being the early stage SDK home screen being ran natively on an Android phone.

Here:

Hope you enjoyed this quick heads up, sorry if it’s not as complete as you would imagine it to be, but that’s fairly all information I could gather about it. Martin claimed that the guides would be out soon for other interested developers.

@jjaone official guides will come soon but basically get sdk packages and install on top of libhybris adaptation — Martin Brook (@vgrade) October 25, 2013

Please leave your comments down below and feel free to give us your feedback!

Update: According to our friend Shmerl over on Diaspora* Network, there is more to libhybris which I didn’t mention:

“It’s an adaptation layer which allows using Android targeted blob drivers (especially GPU ones) with Wayland and glibc systems. Normally Linux driver lives in the kernel (and such drivers are open). But closed ones split the driver into a kernel (open) and userspace (closed) parts. Userspace blob is compiled against a given libc library. And Android uses bionic, while normal Linux like Mer and Co. use glibc. That’s where the problems begin, when hw manufacturers don’t provide open drivers (100% in the kernel), and their closed blobs are built only for bionic. That’s the main problem which libhybris came to solve (to reuse those blobs). It’s not about any reverse engineering to make “open hardware”. Reverse engineered efforts are for example Freedreno and Lima.”

More details on that can be find here:

Part 1

Part 2

Cheers.

Sepehr Noori (James)