From owner-freebsd-current  Wed Mar 27  1:49:39 2002
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by hub.freebsd.org (Postfix) with ESMTP id 53F4A37B405
	for <freebsd-current@FreeBSD.ORG>; Wed, 27 Mar 2002 01:49:34 -0800 (PST)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2R9nFe7023805;
	Wed, 27 Mar 2002 10:49:15 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Kyle Butt <kylebutt@myrealbox.com>
Cc: Dag-Erling Smorgrav <des@ofug.org>, freebsd-current@FreeBSD.ORG
Subject: Re: Superfast clock on current. 
In-Reply-To: Your message of "Wed, 27 Mar 2002 11:00:12 MST."
             <871ye5vqkz.wl@kylebutt.dorms.usu.edu> 
Date: Wed, 27 Mar 2002 10:49:15 +0100
Message-ID: <23804.1017222555@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


Uhm, I just whacked the code into my editor, you may need
more #includes like <sys/param.h> or <sys/types.h>

In message <871ye5vqkz.wl@kylebutt.dorms.usu.edu>, Kyle Butt writes:
>At Wed, 27 Mar 2002 08:42:49 +0100,
>
>bash-2.04$ gcc -o apci apci.c
>In file included from apci.c:2:
>/usr/include/machine/cpufunc.h:72: syntax error before `bsfl'
>/usr/include/machine/cpufunc.h:72: syntax error before `mask'
>/usr/include/machine/cpufunc.h: In function `bsfl':
>/usr/include/machine/cpufunc.h:74: syntax error before `result'
>...
>
>I looked, apparently it doesn't like u_int. I don't know why.
>
>Poul-Henning Kamp wrote:
>> 
>> In message <xzp8z8edhaj.fsf@flood.ping.uio.no>, Dag-Erling Smorgrav writes:
>> >Kyle Butt <kylebutt@myrealbox.com> writes:
>> >> My system clock is running twice as fast as it should be,
>> >> but it doesn't affect timing functions. Ex:
>> >> [...]
>> >> Has anyone else experienced this problem?
>> >
>> >I'm seeing the exact same problem on, guess what...
>> 
>> Can I get one of you to collect a hund-thousand samples of the ACPI
>> timer for me ?
>> 
>> You need to find the exact I/O port it lives on, and then run
>> the following program and send me the uuencoded stdout ?
>> 
>> 	#include <stdio.h>
>> 	#include <machine/cpufunc.h>
>> 
>> 	#define PORT 0x1008
>> 	#define N 100000
>> 	uint32_t  h[N];
>> 
>> 	main()
>> 	{
>> 		FILE *f;
>> 
>> 		f = fopen("/dev/io", "r");
>> 
>> 		memset(h, 0, sizeof h);
>> 		insl(PORT, h, N);
>> 		write (1, h, sizeof h);
>> 	}
>> 
>> 
>> 
>> -- 
>> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
>> phk@FreeBSD.ORG         | TCP/IP since RFC 956
>> FreeBSD committer       | BSD since 4.3-tahoe    
>> Never attribute to malice what can adequately be explained by incompetence.
>> 
>

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message