Hi,
About to mail that,
So I suppose the problem is not with the CLOCK_REALTIME, but with
SIGEV_THREAD, I have a SIGEV_THREAD unfortunately, now trying out with
SIGEV_SIGNAL, just to make sure, that's the problem...
Here is how I setup...
evp.sigev_value.sival_int = *timerHandle; // pass the handle as argument
evp.sigev_notify_function = TimerHandlerFunc;
evp.sigev_notify_attributes = NULL;
evp.sigev_notify = SIGEV_THREAD;
rc = timer_create(CLOCK_REALTIME, &evp, &timerParams[idx].timerId);
On Wed, Dec 3, 2008 at 4:05 PM, David Turner <[EMAIL PROTECTED]> wrote:
> Can you give more details on how you setup your timer. For the record,
> SIGEV_THREAD timers are not supported on the G1.
> This will be fixed soon in an upcoming update to the system code though.
>
> On the other hand, it should be relatively easy to work-around the issue by
> creating a thread that does the wait and function callback (which is
> essentially what the implementation is going to do anyway).
>
> If this is not a SIGEV_THREAD timer, please provide a small test case to
> reproduce the issue, and I'll look into it
>
>
> On Wed, Dec 3, 2008 at 12:04 PM, pavan savoy <[EMAIL PROTECTED]>wrote:
>
>> Hi,
>>
>> I am trying to port a code which has a timer_create
>>
>> I get an EINVAL error, which suggests that there isn't a defined clock ID,
>> However I do see a definition for CLOCK_REALTIME,
>> What's happening, the second argument, that of sigevent seems ok in my
>> case, and the 3rd argument is returned..
>>
>> So is this a problem with the 1st argument, If so, why is it occuring ?
>> even thou' CLOCK_REALTIME is defined ??
>>
>> regards,
>> Pavan
>>
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
