Could you provide the chip manufacturer or some other specification? What kind of chip is it? I think that, as strange the system (and proprietary) is, it will always connect to a device thru a file descriptor created by the .so lib (if not by the kernel). Is it a kind of frame buffer (may be not)? Only then you could be able to know where modify the surfaceflinger. The only documentation are the lists and the code.
Regards Nik On Mar 25, 2:50 am, Rik vd Heijden <[email protected]> wrote: > 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
