Re: [time-nuts] FreeBSD, NetBSD, or Minix-III?

2009-05-18 Thread Poul-Henning Kamp
In message 20090518041523.7b7cdb...@ip-64-139-1-69.sjc.megapath.net, Hal Murr ay writes: Why not add a hardware latch with a fixed delay to read. Because then you need locking to prevent multiple threads/processes from accssing the hardware at the same time. -- Poul-Henning Kamp | UNIX

Re: [time-nuts] FreeBSD, NetBSD, or Minix-III?

2009-05-18 Thread Magnus Danielson
M. Warner Losh skrev: : I think this case doesn't work right: : read high : overflow : long gap : read low : read high : : Suppose the low half overflows once a second so I can use handy numbers. : : If the long gap is 0.6 second, the MSB of the low half will be on so we use : the

Re: [time-nuts] FreeBSD, NetBSD, or Minix-III?

2009-05-18 Thread Magnus Danielson
Hal Murray skrev: I'm interested in the case where interrupts and scheduling are enabled so there may be arbitrary gaps inserted into the simple code. Interrupts enabled means that you can't make it reliable. Sure you can. Just compare the two high samples and try again if they are

Re: [time-nuts] FreeBSD, NetBSD, or Minix-III?

2009-05-18 Thread Hal Murray
stanley_reyno...@yahoo.com said: I need to go back and read what you are trying to measure with your clock. Is it internal to the computer or an external event ? I was thinking of a FPGA on a PCI bus. It has to be PCI rather than USB in order to get reasonable timings. I was going to put

Re: [time-nuts] FreeBSD, NetBSD, or Minix-III?

2009-05-18 Thread Poul-Henning Kamp
In message 20090518081256.97f2bb...@ip-64-139-1-69.sjc.megapath.net, Hal Murr ay writes: I was going to put the Unix clock in the FPGA. It's a pair of 32 bit words. The high word is seconds since some magic date/time. The low word is nano-seconds within this second. Please, will you guys

Re: [time-nuts] FreeBSD, NetBSD, or Minix-III?

2009-05-18 Thread Lux, James P
On 5/18/09 1:12 AM, Hal Murray hmur...@megapathdsl.net wrote: stanley_reyno...@yahoo.com said: I need to go back and read what you are trying to measure with your clock. Is it internal to the computer or an external event ? I was thinking of a FPGA on a PCI bus. It has to be PCI

Re: [time-nuts] FreeBSD, NetBSD, or Minix-III?

2009-05-18 Thread Lux, James P
On 5/18/09 6:18 AM, Lux, James P james.p@jpl.nasa.gov wrote: On 5/18/09 1:12 AM, Hal Murray hmur...@megapathdsl.net wrote: stanley_reyno...@yahoo.com said: I need to go back and read what you are trying to measure with your clock. Is it internal to the computer or an

Re: [time-nuts] FreeBSD, NetBSD, or Minix-III?

2009-05-18 Thread Poul-Henning Kamp
In message c636b079.7d49%james.p@jpl.nasa.gov, Lux, James P writes: An integer divide in software is quite fast (unless you're working with something like a Z80). You only need to divide when you want to change your estimate of the counters range, for generating timestamps a multiplication

Re: [time-nuts] FreeBSD, NetBSD, or Minix-III?

2009-05-18 Thread M. Warner Losh
In message: c636b079.7d49%james.p@jpl.nasa.gov Lux, James P james.p@jpl.nasa.gov writes: : I also wouldn't have the low order counter count nanoseconds, or even set it : up as seconds/subseconds. I'd echo this, since you are artificially limiting the clocks that are input to

[time-nuts] Msg to N.Z. time nuts re time pips

2009-05-18 Thread Murray Greenman
Geoff, I'm not in a position to check at present, but have also noticed discrepancies in the time pips in the past. I'd not use a GPS receiver for this, as they can easily indicate a second or so out. I use a GPS Disciplined Receiver (HP Z3801A or Trimble NTGS50AA) for the job. I suggest you talk

Re: [time-nuts] Msg to N.Z. time nuts

2009-05-18 Thread Philip Pemberton
Hal Murray wrote: One case was a gross software bug. I think it was triggered by a pending leap second. http://www.megapathdsl.net/~hmurray/ntp/leap-gps.gif Interesting that the three receivers with issues were all SiRF III based. Do you know what firmware these were running? How are

[time-nuts] worth anything ? Tracor 308A Will not lock

2009-05-18 Thread Pete Lancashire
http://petelancashire.com/gallery/main.php?g2_itemId=3279 comments on .. now in a pile that may become scrap location is 45 miles from Portland Oregon -pete ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to

Re: [time-nuts] Msg to N.Z. time nuts

2009-05-18 Thread Hal Murray
li...@philpem.me.uk said: Interesting that the three receivers with issues were all SiRF III based. Do you know what firmware these were running? Nope. If you know the recipe to find out, I'll ask them. :) I just scanned their NMEA documentation and didn't see any way to get it. How

Re: [time-nuts] Msg to N.Z. time nuts

2009-05-18 Thread Philip Pemberton
Hal Murray wrote: Interesting that the three receivers with issues were all SiRF III based. Do you know what firmware these were running? Nope. If you know the recipe to find out, I'll ask them. :) I just scanned their NMEA documentation and didn't see any way to get it. If memory

Re: [time-nuts] Msg to N.Z. time nuts

2009-05-18 Thread Hal Murray
li...@philpem.me.uk said: Interesting that the three receivers with issues were all SiRF III based. Do you know what firmware these were running? Nope. If you know the recipe to find out, I'll ask them. :) Failing that, the sirfmon app that comes with gpsd might get the receiver