From: Frederik Reiss <frederikreiss@gmx.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: bad ACPI tables for Dothan?
Date: Wed, 28 Jul 2004 15:25:41 +0200 [thread overview]
Message-ID: <4107A955.5060101@gmx.de> (raw)
In-Reply-To: <1090973581.16558.13.camel@localhost>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeremy Fitzhardinge schrieb:
| In theory the ACPI tables should work fine for this Dothan, but they
| seem corrupt. It seems that centrino_cpu_init_acpi() is getting a
| 0xffff control register value, and a corresponding 25GHz CPU core speed.
| I'm assuming there's someone who knows what this means.
|
| J
Hi,
I found the Problem:
The ACPI table has 16 entrys, but only the first 5 entrys are valid
values the rest of them seems to have 0xffff as value.
If i add the line "p.state_count=5;" before line 345 in the
speedstep-centrino.c which you send me it works perfect for me.
Hope this helps :)
- --
He was always at a loss when people acted like this. When machines went
funny you just oiled them or prodded them or, if nothing else worked, hit
them with a hammer. Nomes didn't respond well to this treatment.
(Diggers)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBB6lVcLHece3p3gARAqP0AJ99o/K+71vW8RyLIuzWjeBznxcWUwCgwKN4
pHfeF4VhO7npc8OJlBSbHKw=
=rlBJ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-28 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <410557B4.6060303@gmx.de>
[not found] ` <1090872497.8114.3.camel@localhost>
[not found] ` <41061454.90306@gmx.de>
[not found] ` <1090965071.16558.2.camel@localhost>
[not found] ` <4106E08D.3000909@gmx.de>
[not found] ` <1090970168.16558.7.camel@localhost>
[not found] ` <4106EB87.4010603@gmx.de>
2004-07-28 0:13 ` bad ACPI tables for Dothan? Jeremy Fitzhardinge
2004-07-28 0:32 ` Frederik Reiss
2004-07-28 13:25 ` Frederik Reiss [this message]
2004-07-28 17:30 ` Dominik Brodowski
2004-07-28 0:59 paul.devriendt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4107A955.5060101@gmx.de \
--to=frederikreiss@gmx.de \
--cc=cpufreq@www.linux.org.uk \
--cc=jeremy@goop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.