[chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 1.29.1-169-gcea68eb

2014-06-02 Thread git
This is an automated email from git. It was enerated because a ref change was pushed to the repository "chrony/chrony.git". The branch, master has been updated via cea68ebc6fa4a7add9cb3bbd428cff80875eba32 (commit) via a33a955163c1af459af176b3fdc1c4c56b4f25f3 (commit) via

Re: [chrony-dev] [PATCH] More reliable method of reading rtc for initial trim

2014-06-02 Thread Miroslav Lichvar
On Mon, Jun 02, 2014 at 11:48:13AM +0200, Hattink, Tjalling [FINT] wrote: > > > I've been able to see this behavior by continuously reading the rtc > > > clock. > > > > Was that with the RTC_RD_TIME ioctl or were you reading CMOS directly? > > I tried to reproduce it with a program continuosly

RE: [chrony-dev] [PATCH] More reliable method of reading rtc for initial trim

2014-06-02 Thread Hattink, Tjalling [FINT]
> Isn't the following code in the kernel code (above the CMOS > operations) supposed to prevent that? > > /* >* read RTC once any update in progress is done. The update >* can take just over 2ms. We wait 20ms. There is no need to >* to poll-wait (up to 1s - eeccch)