public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jurgen Kramer <gtm.kramer@inter.nl.net>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.0-test7] cpufreq longhaul trouble
Date: Fri, 10 Oct 2003 22:03:23 +0200	[thread overview]
Message-ID: <1065816203.1904.6.camel@paragon.slim> (raw)
In-Reply-To: <20031010195800.GK25856@redhat.com>

On Fri, 2003-10-10 at 21:58, Dave Jones wrote:
> On Fri, Oct 10, 2003 at 09:54:11PM +0200, Jurgen Kramer wrote:
>  > >  > 995
>  > > wtf, it still displays "Highestspeed=798MHz" on startup though right ?
>  > Yep,
> 
> another stupid bug.
> calc_speed should look like this..
> 
> static unsigned int calc_speed (int mult, int fsb)
> {
>     int mhz;
>     mhz = (mult/10)*fsb;
>     if (mult%10)
>         mhz += fsb/2;
>     return mhz;
> }
> 

Fixed that one:

[root@paradox cpufreq]# more *
::::::::::::::
cpuinfo_max_freq
::::::::::::::
798
::::::::::::::
cpuinfo_min_freq
::::::::::::::
399
::::::::::::::
scaling_available_governors
::::::::::::::
userspace
::::::::::::::
scaling_driver
::::::::::::::
longhaul
::::::::::::::
scaling_governor
::::::::::::::
userspace
::::::::::::::
scaling_max_freq
::::::::::::::
798
::::::::::::::
scaling_min_freq
::::::::::::::
399
::::::::::::::
scaling_setspeed
::::::::::::::
798



      reply	other threads:[~2003-10-10 20:05 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
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 [this message]

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=1065816203.1904.6.camel@paragon.slim \
    --to=gtm.kramer@inter.nl.net \
    --cc=davej@redhat.com \
    --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