From owner-freebsd-current@FreeBSD.ORG Mon Aug 2 13:17:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7802616A4CE for ; Mon, 2 Aug 2004 13:17:00 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (80-219-174-97.dclient.hispeed.ch [80.219.174.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id A690043D5F for ; Mon, 2 Aug 2004 13:16:58 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:50db:ae61:0:220:afff:fed4:dbcb]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id i72DGgH86309 verified NO) for ; Mon, 2 Aug 2004 15:16:46 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id i72DGfO86307; Mon, 2 Aug 2004 15:16:42 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Mon, 2 Aug 2004 15:16:42 +0200 (CEST) Message-Id: <200408021316.i72DGfO86307@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma To: FreeBSD Current References: <23206.1087846355@critter.freebsd.dk> <20040621.191446.45217670.imp@bsdimp.com> X-Mailman-Approved-At: Tue, 03 Aug 2004 14:17:20 +0000 Subject: Re: [HEADSUP] retire TIOCDCDTIMESTAMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Aug 2004 13:17:00 -0000 [keep replies on the list, not to me, to avoid bounces, thanks] [sorry for the lateness of this -- that's what I get for being offline] "M. Warner Losh" wrote: > In message: <23206.1087846355@critter.freebsd.dk> > Poul-Henning Kamp writes: > : The RFC 2783 PPS-API has been standardized to do everything > : TIOCDCDTIMESTAMP did and quite a bit more. > I think this is reasonable on its face. Unless this breaks a bunch of > ports I don't see a big problem with it. I have some problems using > pps api at times, but those aren't relevant for this change... I have expanded TIOC*TIMESTAMP in my own personal hive of hackery to also handle signals on the other modem status lines as well. Therefore I'm curious. As far as I know, I can simply revert this retirement in my own personalized codebase without difficulty if I choose. So far. Supposing I want to use the PPS-API. It seems that it's possible for me to select whether I want it to work on the DCD status line, or (hmm, one other, must grep code) status line. But is it possible for the PPS-API to work simultaneously on more than a single status line? A preliminary perusal of the code would suggest not, but I can't read code to save my life. Basically, my TIOC*TIMESTAMP hacks allowed me to gather timestamps from the four status lines, to be used by programs that could handle four sources of PPS data on a single port. I'd like to be able to do that with PPS-API as well, if possible. (The other wishlist item I have that might be applicable to PPS-API is to be able to query system-uptime as well as system-time at a status change, for cases where the system time has been stepped. This may be something irrelevant to or outside the scope of PPS-API. Clearly I need to figure out how to use that first, and maybe then I won't have such stupid questions.) thanks barry bouwsma