From owner-freebsd-hackers Fri Jan 9 05:50:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA21121 for hackers-outgoing; Fri, 9 Jan 1998 05:50:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (ppp11.portal.net.au [202.12.71.111]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA21107 for ; Fri, 9 Jan 1998 05:50:49 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id AAA00728; Sat, 10 Jan 1998 00:13:57 +1030 (CST) Message-Id: <199801091343.AAA00728@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: daniel_sobral@voga.com.br cc: mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: Device Driver In-reply-to: Your message of "Fri, 09 Jan 1998 11:46:18 -0300." <83256587.0050BC26.00@papagaio.voga.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Jan 1998 00:13:56 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > > > Each tsleep() count corresponds to 1/hz seconds, where hz should > > be considered opaque. > > Yup, but since I'm using tsleep to block for "a while", while the card does > it's business, and waking up now and then to since if it has finished, I'd > like to have _some_ notion of home much is hz. It's way different if hz is > usually in then tenths of second, than if hz is hardly less than 1/100s. Not at all. You want to block for 1/10th of a second? Pass hz/10 as an argument. This way you can change the clock on the fly and still not lose your timing. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\