From owner-freebsd-hackers  Fri Mar 22 05:20:32 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA05307
          for hackers-outgoing; Fri, 22 Mar 1996 05:20:32 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA05302
          for <hackers@FreeBSD.org>; Fri, 22 Mar 1996 05:20:29 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id AAA06941; Sat, 23 Mar 1996 00:17:50 +1100
Date: Sat, 23 Mar 1996 00:17:50 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603221317.AAA06941@godzilla.zeta.org.au>
To: bde@zeta.org.au, pst@shockwave.com
Subject: Re: real time interrupts in FreeBSD?
Cc: hackers@FreeBSD.org
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>Do you feel it's better to acquire timer 0 once, set my 1ms interrupt rate,
>and leave the ms timer running until the camera device is no longer open,
>or do you think that when I need to download a frame, I should switch the
>clock rate, do my wait, restore the clock rate, and go on?

I would try letting it run.  This will probably work OK, and it saves you
from having to worry about other drivers stealing the timer.

Bruce