Hi David, I have sent you the code. Please let me know if you have any clue.
Thanks, -Ravi On Jan 22, 5:53 pm, David Turner <[email protected]> wrote: > please send them to me directly ([email protected]) > (or if the source is small, just inline it here) > > > > On Thu, Jan 22, 2009 at 3:18 PM, ravikbsh <[email protected]> wrote: > > > Hi David, > > > Thanks for the quick reply. Yes, i have the complete test code and the > > make file which simulates this problem. > > How do it send them? I dont see any option to attach source code. > > > On Jan 22, 4:42 pm, David Turner <[email protected]> wrote: > > > Hmmm, do you have a small and complete source file for a test that > > exhibit > > > the problem ? > > > > timer management has been modified to properly implement SIGEV_THREAD > > > timers, > > > however SIGEV_SIGNAL ones should not be impacted. > > > > are you sure you don't have the signal blocked ? > > > > On Thu, Jan 22, 2009 at 2:17 PM, ravikbsh <[email protected]> wrote: > > > > > I am trying to port timer APIs to Zoom2 running android. I see that, > > > > when i call timer_create, it returns 0 (meaning success). Then the > > > > callback never gets called. Following is the code snippet, > > > > > sigev.sigev_notify = SIGEV_SIGNAL; > > > > sigev.sigev_signo = signo; > > > > sigev.sigev_value.sival_ptr = timerid; > > > > sigev.sigev_value.sival_int = timer; > > > > > timer_create(CLOCK_REALTIME, &sigev, timerid); > > > > > If this can help, the same code works on Zoom1. Also I have tried with > > > > SIGEV_NONE with the same result. > > > > > It this broken in the recent release?- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
