![]() |
Info.TheNSLU2TimeOfDayTimekeeping HistoryHide minor edits - Show changes to markup August 13, 2007, at 02:23 AM
by -- fixed false wikilinks
Changed lines 1-2 from:
The NSLU2 has a hardware Real Time Clock (RTC), however while Linux is running, time is actually kept using interrupts from the built in XScale? clock registers (i.e. the RTC is not used). to:
The NSLU2 has a hardware Real Time Clock (RTC), however while Linux is running, time is actually kept using interrupts from the built in XScale clock registers (i.e. the RTC is not used). Changed lines 23-24 from:
to:
August 11, 2007, at 06:06 PM
by -- Added drift entry
Changed lines 30-31 from:
to:
February 22, 2007, at 09:20 PM
by --
Changed line 30 from:
to:
February 22, 2007, at 09:19 PM
by -- added mine
Changed lines 29-30 from:
to:
February 22, 2007, at 07:12 AM
by -- Added ntp.drift info
Changed lines 28-29 from:
to:
August 06, 2006, at 01:57 PM
by -- Added NTP drift results
Changed lines 27-28 from:
to:
February 17, 2006, at 05:11 PM
by -- inserted a comma after running
Changed lines 1-2 from:
The NSLU2 has a hardware Real Time Clock (RTC), however while Linux is running time is actually kept using interrupts from the built in XScale? clock registers (i.e. the RTC is not used). to:
January 09, 2006, at 01:12 PM
by -- Add/update data
Changed line 22 from:
to:
Changed lines 26-27 from:
to:
January 09, 2006, at 10:08 AM
by --
Changed line 22 from:
to:
January 09, 2006, at 10:07 AM
by --
Changed line 22 from:
to:
January 08, 2006, at 03:09 PM
by -- added data
Added line 19:
January 06, 2006, at 01:19 PM
by --
Changed lines 24-25 from:
to:
January 06, 2006, at 08:40 AM
by -- Updated table to include my name and new ntp.drift (with more time to stabilize)
Changed line 23 from:
to:
January 06, 2006, at 04:49 AM
by --
Changed line 19 from:
to:
January 05, 2006, at 11:37 AM
by -- Added my ntp.drift info
Changed lines 23-24 from:
to:
January 04, 2006, at 11:12 AM
by -- fix formatting
Changed lines 17-23 from:
to:
January 04, 2006, at 11:10 AM
by -- Added some data
Added lines 15-23:
January 04, 2006, at 10:53 AM
by -- Brief description of how the XScale HW clock works
Added lines 1-14:
The NSLU2 has a hardware Real Time Clock (RTC), however while Linux is running time is actually kept using interrupts from the built in XScale? clock registers (i.e. the RTC is not used). The mainstream versions of the Linux kernel assume that IXP4XX boards provide a clock input to the CPU which causes clock counts to happen at a rate of 66.666666MHz. Unfortunately this would require a 33.333333MHz crystal and no one seems to sell those... In practice, therefore, an IXP4XX board has some built in clock drift which can be determined from the actual clock frequency. On the NSLU2 board the crystal is 33MHz and the clock count rate is 66MHz, other IXP4XX boards use 33.33MHz or 33.3333MHz crystals which are much closer to the Linux expected value. The Intel specified value is actually 33.33MHz (though the documentation may not be consistent.) OpenSlug kernels correct for the actual clock frequency in a variety of ways (depending on the kernel). In addition NTP software (ntp or openntp) will automatically correct the clock from external time server sources. NTP (but not openntp) writes a file In is my [jbowler's] idea that all NSLU2 boards show approximately the same drift and that some internal inaccuracy in the OpenSlug software is causing a small (about 10ppm) drift. If this can be established as a consistent error we can improve clock accuracy on the NSLU2 in the absence of NTP. Therefore if you install NTP on openslug (or variants) and run it for long enough (at least 24 hours) to both produce /etc/ntp.drift and get a consistent value please enter the value below:
view ·
edit ·
print ·
history ·
Last edited by fcarolo.
Based on work by Thomann, mas, Bernard Davison, Tim Auton, Peter Taylor, jbowler, beww, pTweety, Chris Burghart, Birko Bergt, and nilrog. Originally by jbowler. Page last modified on August 13, 2007, at 02:23 AM
|