Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 2 Sep 2014 04:34:37 -0400
From: Rich Felker <>
Subject: Re: libhybris and musl?

On Tue, Sep 02, 2014 at 09:11:33AM +0200, Wermut wrote:
> We used libhybris for one single thing. Getting Android/bionic linked
> graphic drivers up and running under embedded glibc linux. Since all the
> hardware vendors startet to only deliver their drivers in binary form and
> exclusivly for Android, these is usually the only way to get GPU up and
> running.
> libhybris was originally developed for Sailfish OS that is using Android
> drivers of all kind under a glibc enviroment. The graphic Stack is Android
> OpenGL driver > libhybris > wayland. Other projects like the Intel/Samsung
> "mer" project is doing exactly the same.
> If you are interessted how to install and use it, there is a rudimentary
> how to:
> This thing is a therible hack, but unfortunatly this is often the only way
> to get things like OpenGL, hw video decoding etc. working on embedded arm
> linux. There are no signs that companies like Qualcom or ARM themself with
> their Mali GPU will deliver open source drivers.
> Linking your own apps to bionic/libhybris makes absolutly no sense. The
> reason for libhybris is to use bionic binaries (drivers) within glibc based
> enviroments.

How does this work when the binary driver is accessing the same symbol
names (mainly standard functions, but not necessarily) as the program
the driver is loaded into, but the latter needs the real versions in
libc and only the former should be routed through a hack layer?


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.