Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] timing for geeks
- Date: Sat, 3 Dec 2005 13:26:56 +0100
- From: Michal Hajek <hajek1@example.com>
- Subject: Re: [tlug] timing for geeks
- References: <20051202154627.GB4348@example.com> <20051202152527.302e2f6f.jep200404@example.com>
- User-agent: Mutt/1.5.9i
Hello :) Thank you Jim and also Josh for replyes. :) Great! :) Since so far only two of you responded, I can afford the luxury to give a prize for every (so far) attendant of the contest :)) When you happen to be in Prague, do not hesitate to let me know :) Next... I am still working on the topic, but here are some quick comments: * Jim (jep200404@example.com) [051202 21:43]: > This is a rich experiment with many twists and turns. definitely, now I am only beginnig to discover all the truth... eg. see: http://source.mvista.com/~ganzinger/hrt/home_page.html and also in Documentation included in linux kernel source see: rtc.txt (:( I did not read it all through yet...) Unfortunately, Josh program - using either gettimeofday() or clock_gettime() - still produces "saw-ish" time signal. And this did not change even though I tried it with CLOCK_REALTIME and also CLOCK_MONOTONIC clock variables [1]. Thus basicaly, using these functions does not solve the problem. But definitely they are much better choice than my original try with ftime(). :)))) [1] see man clock_gettime Best regards Michal
- Follow-Ups:
- Re: [tlug] timing for geeks
- From: Ian Wells
- Re: [tlug] A Rich Experiment Indeed
- From: Jim
- References:
- [tlug] timing for geeks :)
- From: Michal Hajek
- Re: [tlug] timing for geeks
- From: Jim
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Mea Culpa
- Next by Date: [tlug] US keyboards
- Previous by thread: Re: [tlug] timing for geeks
- Next by thread: Re: [tlug] timing for geeks
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links