From owner-freebsd-current Wed Mar 27 3:43:48 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 4CCDF37B419 for ; Wed, 27 Mar 2002 03:43:42 -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 g2RBhMe7044866; Wed, 27 Mar 2002 12:43:22 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kyle Butt Cc: Dag-Erling Smorgrav , freebsd-current@FreeBSD.ORG Subject: Re: Superfast clock on current. In-Reply-To: Your message of "Wed, 27 Mar 2002 13:18:12 MST." <87wuvxu5mj.wl@kylebutt.dorms.usu.edu> Date: Wed, 27 Mar 2002 12:43:22 +0100 Message-ID: <44865.1017229402@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <87wuvxu5mj.wl@kylebutt.dorms.usu.edu>, Kyle Butt writes: >At Wed, 27 Mar 2002 10:49:15 +0100, >Poul-Henning Kamp wrote: >> >> >> Uhm, I just whacked the code into my editor, you may need >> more #includes like or > >Thanks. That did the trick. Now how do I go about finding that >port? Is that something I can glean from the dmesg, or do I have >to look somewhere else for that? You should have a line like this in your dmesg: acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 in that case 0xe408 is the port. > >> >> 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 , Dag-Erling Smorgrav writes: >> >> >Kyle Butt 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 >> >> #include >> >> >> >> #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. >> > -- 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