We have the biggest part of our system working. But our system doesn't 
provide /dev/fb* or /dev/graphics/*
The manufacturer of our chip made a userspace daemon and an .so file to 
interface with the display (which are not open-source). And this .so-file is 
linked to a different version of libc then the android libc.
When Android tries to load the .so-file the surfaceflinger crashes and 
logcat shows a relocation-error with the libc's.
So we think we must make a modification to Android in order to change the 
the way android interfaces with the display to this system.

Our question is, what exactly do we need to change in Android in order to 
get Android to interface to the .so file then to the framebuffer.

The platform is ported before by other OEM's, but we don't have a source of 
it.

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to