<br><br><div><span class="gmail_quote">On 4/6/06, <b class="gmail_sendername">Goldenear</b> <<a href="mailto:goldenear@free.fr">goldenear@free.fr</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>>Kind of a shame. It would be nice if asterisk could make use of its own<br>>timing source (using the 2.6 HPET would be a good thing), so no ztdummy<br>>would be required.</blockquote><div><br>
I would basically argue at this point that not using the HPET directly
but rather using the new (2.6.16 and later) hi-resolution timers
abstraction in the kernel would be the best choice. You can get an
honest clock into ztdummy now without using rtc. see
<a href="http://lwn.net/Articles/167315/">http://lwn.net/Articles/167315/</a> for more details....<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">><br>><br>That's exactly what I was asking for :)<br>That would be really nice if Asterisk (when using VOIP only) could work
<br>properly without the need to load any kernel module.<br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-dev mailing list
<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></blockquote></div><br><br clear="all"><br>--
<br>Mike Taht<br>PostCards From the Bleeding Edge<br><a href="http://the-edge.blogspot.com">http://the-edge.blogspot.com</a>