From: Ashley Pittman <ashley@pittman.co.uk>
To: mgillespie@mgillespie.plus.com
Cc: cpufreq <cpufreq@www.linux.org.uk>
Subject: Re: problems with longhaul cpufreq driver.
Date: Mon, 08 Dec 2003 16:39:03 +0000 [thread overview]
Message-ID: <1070901543.27939.103.camel@ashley> (raw)
In-Reply-To: <20031208162600.mgillespie@Plus.Net>
On Mon, 2003-12-08 at 16:26, mgillespie@mgillespie.plus.com wrote:
> If I check the dmesg log, I see the following on startup:
>
> longhaul: VIA C3 'Ezra' [C5C] CPU detected. Longhaul v2 supported.
> longhaul: MinMult=5.0x MaxMult=6.0x
> longhaul: FSB: 0MHz Lowestspeed=0MHz Highestspeed=0MHz
> longhaul: FSB:0 Mult:10.0x
The problem here is the FSB is being reported as 0, this is wrong.
> Anyone else got this problem?
I had a very similar problem with my c3 using a 2.6 kernel, I posted a
patch to this list a while ago that, whilst incorrect in some ways is
probably enough to allow the module to work. There was a discussion
about a better way to do it but I don't think that anything has been
committed yet.
I would be interested to know if the patch works for you.
Ashley,
next prev parent reply other threads:[~2003-12-08 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 16:26 problems with longhaul cpufreq driver mgillespie
2003-12-08 16:39 ` Ashley Pittman [this message]
2003-12-08 19:38 ` Ducrot Bruno
2003-12-08 20:32 ` Mark Gillespie
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=1070901543.27939.103.camel@ashley \
--to=ashley@pittman.co.uk \
--cc=cpufreq@www.linux.org.uk \
--cc=mgillespie@mgillespie.plus.com \
/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.