From: Bruno Ducrot <ducrot@poupinou.org>
To: cpufreq@www.linux.org.uk
Subject: Re: [PATCH] Fix cpu recognization if BIOS does not set cpu to max freq [was: Re: [Bug 3600] New: Cpu recognization fails after upgrade from 2.6.7 to 2.6.9]
Date: Wed, 10 Nov 2004 21:15:02 +0100 [thread overview]
Message-ID: <20041110201502.GC31422@poupinou.org> (raw)
In-Reply-To: <20041029153544.GA9799@dominikbrodowski.de>
> - there's an entry "fsbspeed" in pst_s. Is this useful to determining the
> FSB, and then checking whether FSB*CFID makes more sense than FSB*MFID
> when comparing it to cpu_khz?
There is no such information if you have to configure with acpi...
Further, fsbspeed is used in order to check if PST is valid by
comparing with the actual FSB.
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-11-10 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 14:13 [Bug 3600] New: Cpu recognization fails after upgrade from 2.6.7 to 2.6.9 bugme-daemon
2004-10-20 15:47 ` Kronos
2004-10-20 16:05 ` Daniele Bonomi
2004-10-20 16:51 ` Kronos
2004-10-21 10:25 ` Bruno Ducrot
2004-10-21 16:10 ` Kronos
2004-10-23 21:43 ` [PATCH] Fix cpu recognization if BIOS does not set cpu to max freq [was: Re: [Bug 3600] New: Cpu recognization fails after upgrade from 2.6.7 to 2.6.9] Kronos
2004-10-29 15:35 ` Dominik Brodowski
2004-11-10 20:15 ` Bruno Ducrot [this message]
2004-11-02 21:10 ` [Bug 3600] New: Cpu recognization fails after upgrade from 2.6.7 to 2.6.9 Dave Jones
2004-11-02 22:13 ` [PATCH for other issue included] " Dominik Brodowski
2004-10-20 19:37 ` Daniele Bonomi
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=20041110201502.GC31422@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
/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