From: Dave Jones <davej@redhat.com>
To: Jurgen Kramer <gtm.kramer@inter.nl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.0-test7] cpufreq longhaul trouble
Date: Fri, 10 Oct 2003 20:31:51 +0100 [thread overview]
Message-ID: <20031010193151.GI25856@redhat.com> (raw)
In-Reply-To: <1065812601.1842.6.camel@paragon.slim>
On Fri, Oct 10, 2003 at 09:03:22PM +0200, Jurgen Kramer wrote:
> Ok, changing line 394 gives:
>
> <snip>
> longhaul: VIA C3 'Ezra' [C5C] CPU detected. Longhaul v1 supported.
> longhaul: MinMult=3.0x MaxMult=6.0x
> longhaul: FSB: 133MHz Lowestspeed=399MHz Highestspeed=798MHz
> <snip>
>
> But should it really be v1? With 2.4.20 I get:
> ep 28 21:09:28 paradox kernel: longhaul: VIA CPU detected. Longhaul
> version 2 supported
> Sep 28 21:09:28 paradox kernel: longhaul: CPU currently at 798MHz (133 x
> 6.0)
> Sep 28 21:09:28 paradox kernel: longhaul: MinMult(x10)=30
> MaxMult(x10)=60
> Sep 28 21:09:28 paradox kernel: longhaul: Lowestspeed=399000
> Highestspeed=798000
> Sep 28 21:09:28 paradox kernel: longhaul: New FSB:133 Mult(x10):60
> Sep 28 21:09:28 paradox kernel: longhaul: New FSB:133 Mult(x10):30
Note that the various speeds etc now match.
Why we got away with this in 2.4 I'm not sure, depends which patch you used.
> x86info -a gives (running 2.6.0test7):
...
> /dev/cpu/0/msr: No such device
Heh. this was the important bit.. Doesn't matter now anyway.
Dave
--
Dave Jones http://www.codemonkey.org.uk
next prev parent reply other threads:[~2003-10-10 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 11:15 [2.6.0-test7] cpufreq longhaul trouble Jurgen Kramer
2003-10-10 18:11 ` Dave Jones
2003-10-10 18:42 ` Dave Jones
2003-10-10 19:03 ` Jurgen Kramer
2003-10-10 19:31 ` Dave Jones [this message]
2003-10-10 19:14 ` Jurgen Kramer
2003-10-10 19:34 ` Dave Jones
2003-10-10 19:54 ` Jurgen Kramer
2003-10-10 19:58 ` Dave Jones
2003-10-10 20:03 ` Jurgen Kramer
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=20031010193151.GI25856@redhat.com \
--to=davej@redhat.com \
--cc=gtm.kramer@inter.nl.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox