seems indeed like the only possible sollution. On Fri, Mar 25, 2011 at 4:47 AM, Chih-Wei <[email protected]> wrote:
> I don't know what you have done > and what code base you used. > Maybe you should ask your vendor to > provide bionic linked .so, or static libraries, > or even the source code. > > I suggest you refer to http://www.android-x86.org > to see what we have implemented for > hw acceleration of intel's graphic chipset. > > On 3月23日, 下午4時49分, Rik vd Heijden <[email protected]> > wrote: > > Hi all, > > We are intending to port Android to an x86 platform. Since the > > platform doesn't supply a framebuffer we need to modify android to > > communicate with the display driver.(like gralloc or overlay ?) > > > > The creator of our platform supplies .so-files (without a source) to > > get the display working. These .so-files are dependent on glibc. We > > can link a gralloc/overlay-library but when surfaceflinger tries to > > load it it gets a relocate-error when linking to the .so file. > > > > We are in the stadium of getting the display working, the (Android) > > Linux kernel is booting and all the services start properly except the > > surfaceflinger. > > > > Is there any (good) documentation about getting the display working > > without a framebuffer-device? > > Does anybody have a clue about getting the display working with .so- > > files linking against an other library than bionic libc? > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
