From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6046 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: libhybris and musl? Date: Tue, 2 Sep 2014 04:34:37 -0400 Message-ID: <20140902083437.GJ12888@brightrain.aerifal.cx> References: <25172046.n8KGkBYA4f@krypton> <20140901210823.GF12888@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1409646898 22346 80.91.229.3 (2 Sep 2014 08:34:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 2 Sep 2014 08:34:58 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6053-gllmg-musl=m.gmane.org@lists.openwall.com Tue Sep 02 10:34:53 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1XOjYB-00038A-79 for gllmg-musl@plane.gmane.org; Tue, 02 Sep 2014 10:34:51 +0200 Original-Received: (qmail 16083 invoked by uid 550); 2 Sep 2014 08:34:49 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 16075 invoked from network); 2 Sep 2014 08:34:49 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:6046 Archived-At: 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: > http://www.cnx-software.com/2013/04/21/how-to-use-libhybris-and-android-gpu-libraries-with-mer-linux-on-the-cubieboard/ > > 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? Rich