Date: Wed, 27 Mar 2002 12:43:22 +0100 From: Poul-Henning Kamp <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. Message-ID: <44865.1017229402@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 27 Mar 2002 13:18:12 MST." <87wuvxu5mj.wl@kylebutt.dorms.usu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <sys/param.h> or <sys/types.h>
>
>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 <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.
>>
>
--
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44865.1017229402>