cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot@poupinou.org>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@www.linux.org.uk
Subject: Re: longhaul: Unknown VIA CPU
Date: Wed, 3 Sep 2003 15:45:24 +0200	[thread overview]
Message-ID: <20030903134524.GC4401@poupinou.org> (raw)
In-Reply-To: <20030903132457.GH1225@redhat.com>

On Wed, Sep 03, 2003 at 02:24:57PM +0100, Dave Jones wrote:
> On Wed, Sep 03, 2003 at 02:52:04PM +0200, Ducrot Bruno wrote:
>  > >  > also, the email
>  > >  > address will need to be changed to the codemonkey one :)
>  > > 
>  > > Already fixed in 2.6, not sure about the 2.4/2.4-ac backports.
>  > 
>  > ducrot@neptune:~$ cvs rdiff -u -r LINUX_2_4 -rLINUX_2_5 cpufreq/linux/arch/i386/kernel/cpufreq/longhaul.c
> 
> I'm not sure if I pushed the changes back to CVS after merging to
> 2.5 mainline.

ducrot@neptune:~$ diff -u ~/tmp/cpufreq/25/cpufreq/linux/arch/i386/kernel/cpufreq/longhaul.c \
	/var/share/cvs/bitkeeper/cpufreq-2.5/arch/i386/kernel/cpu/cpufreq/longhaul.c
@@ -584,7 +584,7 @@
        if (ret != 0)
                return ret;
 
-       policy->governor = CPUFREQ_DEFAULT_GOVERNOR;
+       policy->policy = CPUFREQ_POLICY_PERFORMANCE;
        policy->cpuinfo.transition_latency = CPUFREQ_ETERNAL;
 
        policy->cur = (unsigned int) (longhaul_get_cpu_fsb() * longhaul_get_cpu_mult() * 100);

(cvs don't have some core update).

Cheers,

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

      reply	other threads:[~2003-09-03 13:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 22:23 longhaul: Unknown VIA CPU Vincent Stehlé
2003-09-03  0:49 ` Dave Jones
2003-09-03 13:49 ` Sven Dowideit
2003-09-03 12:00   ` Dave Jones
2003-09-03 12:52     ` Ducrot Bruno
2003-09-03 13:24       ` Dave Jones
2003-09-03 13:45         ` Ducrot Bruno [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=20030903134524.GC4401@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox