From owner-freebsd-hackers  Thu Jun  1 14:33:18 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id OAA03476
          for hackers-outgoing; Thu, 1 Jun 1995 14:33:18 -0700
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA03468
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 1 Jun 1995 14:33:14 -0700
Received: (from julian@localhost) by ref.tfs.com (8.6.8/8.6.6) id OAA00219; Thu, 1 Jun 1995 14:33:12 -0700
From: Julian Elischer <julian@ref.tfs.com>
Message-Id: <199506012133.OAA00219@ref.tfs.com>
Subject: Re: Interval timer/System clock
To: james@miller.cs.uwm.edu (Jim Lowe)
Date: Thu, 1 Jun 1995 14:33:11 -0700 (PDT)
Cc: freebsd-hackers@FreeBSD.ORG
In-Reply-To: <199506012039.PAA20210@miller.cs.uwm.edu> from "Jim Lowe" at Jun 1, 95 03:39:51 pm
Content-Type: text
Content-Length: 292       
Sender: hackers-owner@FreeBSD.ORG
Precedence: bulk

The timers are really the user-end view of a ball of spaghetti you
don't really want to get into too much :)

FreeBSD can change it's system clock to 16KHz to run audio
through the speaker.. but somehow (!) the other timers appear unchanged..

bde is the man to speak to about that..

julian