Recalculate delaytab[]. We need to round up in case we were on the edge of a

tick and the hardware mysteriously responds fast enough that the delay ends
up being 1 tick short.  An unlikely event, but just in case anything actually
relies on this...
This commit is contained in:
mycroft 1999-03-29 17:54:34 +00:00
parent c40877ff9d
commit 7c33a450ba
1 changed files with 5 additions and 5 deletions

View File

@ -1,4 +1,4 @@
/* $NetBSD: clock.c,v 1.60 1999/03/29 17:33:29 mycroft Exp $ */ /* $NetBSD: clock.c,v 1.61 1999/03/29 17:54:34 mycroft Exp $ */
/*- /*-
* Copyright (c) 1993, 1994 Charles M. Hannum. * Copyright (c) 1993, 1994 Charles M. Hannum.
@ -322,10 +322,10 @@ delay(n)
int n; int n;
{ {
int tick, otick; int tick, otick;
static int delaytab[26] = { static const int delaytab[26] = {
0, 1, 2, 4, 5, 6, 7, 8, 10, 11, 0, 2, 3, 4, 5, 6, 7, 9, 10, 11,
12, 13, 14, 16, 17, 18, 19, 20, 21, 23, 12, 13, 15, 16, 17, 18, 19, 21, 22, 23,
24, 25, 26, 27, 29, 30, 24, 25, 27, 28, 29, 30,
}; };
/* allow DELAY() to be used before startrtclock() */ /* allow DELAY() to be used before startrtclock() */