From: Dave Jones <davej@redhat.com>
To: Daniel Rubio Bonilla <danielrubiob@terra.es>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: How can I guess the system FSB speed?
Date: Tue, 14 Mar 2006 18:40:27 -0500 [thread overview]
Message-ID: <20060314234027.GB8659@redhat.com> (raw)
In-Reply-To: <200603150018.33139.danielrubiob@terra.es>
On Wed, Mar 15, 2006 at 12:18:33AM +0100, Daniel Rubio Bonilla wrote:
> Hi to everyone. I am new in this mailing list.
>
> I would like to ask how could I guess the speed of the FSB of the system, if
> there is any way...
you can't reliably. the best you can hope for is to decode the EBLCR MSR
if present. Unfortuantly, it has different meaning on pretty much
every CPU out there, which makes it a bit of a mess to decode.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-03-14 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 23:18 How can I guess the system FSB speed? Daniel Rubio Bonilla
2006-03-14 23:40 ` Dave Jones [this message]
2006-03-15 18:48 ` Daniel Rubio Bonilla
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=20060314234027.GB8659@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=danielrubiob@terra.es \
/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