From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Gillespie Subject: Re: problems with longhaul cpufreq driver. Date: Mon, 08 Dec 2003 20:32:19 +0000 Sender: cpufreq-bounces@www.linux.org.uk Message-ID: <3FD4DFD3.4010202@markgillespie.co.uk> References: <20031208162600.mgillespie@Plus.Net> <1070901543.27939.103.camel@ashley> <20031208193852.GA23953@poupinou.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20031208193852.GA23953@poupinou.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: cpufreq-bounces@www.linux.org.uk Content-Type: text/plain; charset="us-ascii"; format="flowed" To: cpufreq Ducrot Bruno wrote: > On Mon, Dec 08, 2003 at 04:39:03PM +0000, Ashley Pittman wrote: > >>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. >> My hack was even simpler!! I just hacked the function guess_fsb to always return 133!! (the kernel nor code is going nowhere other than this small eden box, so it matters not)... My DMESG now shows: longhaul: VIA C3 'Ezra' [C5C] CPU detected. Longhaul v2 supported. longhaul: MinMult=5.0x MaxMult=6.0x longhaul: FSB: 133MHz Lowestspeed=665MHz Highestspeed=798MHz Thanks all for the pointers...