On 10/18/05, <b class="gmail_sendername">Chih-Wei Huang</b> <<a href="mailto:cwhuang@citron.com.tw">cwhuang@citron.com.tw</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
BJ Weschke wrote:<br>><br>> The bug was closed because the ztdummy behavior is not the specific cause<br>> for the delay problem. That patch with USE_RTC was intended to make use of<br>> the real time resource available within the kernel >=
2.6.13 instead of<br>> relying on a OHCI USB resource which was the case previously.<br><br>But USE_RTC also compile for kernel < 2.6.13..<br>(at least, 2.6.9 in my system)<br>Is kernel >= 2.6.13 necessary?<br><br>
> If you're looking for a "fix" in MeetMe, some have reported success with<br>> applying the patches available in bug 5374.<br><br>Thank you for the info.<br><br>I tried that patch.<br>Unfortunately, it seems not improve the increasing delay problem
<br>of meetme.</blockquote><div><br>
</div></div><br>
Patch in bug # 5374 only makes a difference if Asterisk gets complied
with -DZAPTEL_OPTIMIZATIONS. When compiling Asterisk, can you tell if
-DZAPTEL_OPTIMIZATIONS is being used?<br>
<br>
After Asterisk is compliled this way, ztdummy needs to be running.<br>
<br>
Carlos<br>
<br>