when overlay is created, it walks through overlay hardware module > if (overlayRef != 0) { > if (hw_get_module(OVERLAY_HARDWARE_MODULE_ID, &module) == 0) { > if (overlay_data_open(module, &mOverlayData) == NO_ERROR) { > mStatus = mOverlayData->initialize(mOverlayData, > overlayRef->mOverlayHandle); > }
so, instead of generating generic liboverlay.so, its better to generate module with hardware name appeneded. you can update your overlay -> Android.mk module name as below.. LOCAL_MODULE := overlay.$(TARGET_BOARD_PLATFORM) Not sure if you leave it as just liboverlay.so, it will work or not.. On Fri, May 7, 2010 at 7:18 PM, Sambhav <isamb...@gmail.com> wrote: > Hi, > > By default overlay module at *hardware\libhardware\modules\overlay* is a > skeleton implementation. > I am calling the V4L2 driver calls from these functions. > I have build the module - liboverlay.so > > Where should I indicate that Overlay calls made from * > frameworks/base/libs/ui/Overlay.cpp* to use the services from *liboverlay.so > *created above. > > Regards, > Sambhav > > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting