All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
	Linux ACPI List <acpi@phobos.fachschaften.tu-muenchen.de>
Subject: Re: Changing CPU Speed while running Linux
Date: Thu, 14 Jun 2001 00:23:07 +0200	[thread overview]
Message-ID: <20010613221355Z264238-17720+3532@vger.kernel.org> (raw)

Arjan van de Ven wrote:
>
> Sven Geggus wrote:
> >
> > Hi there,
> >
> > on my Elan410 based System it is very easy to change the CPU clock
> > speed by means od two outb commands.
> >
> > I was wondering, if it does some harm to the Kernel if the CPU is
> > reprogrammed using a different CPU clock speed, while the system is up and
> > running.
>
> I have a module for the K6 PowerNow which allows you to do
>
> echo 450 > /proc/sys/cpu/0/frequency
>
> and does the right thing wrt udelay / bogomips etc..
> I can dig it out if you want.. sounds like this should be a more generic
> thing.

Yes, please.

After (all) Athlon 4/MT (Palomino)  and Duron mobile feature PowerNow! it 
should be usefull for more and more people.

Regards,
	Dieter

BTW	I think there are only a "few" K6-2+/K6-III+ out ;-)
	But PowerNow! is nice stuff. I had an eye on an 1 GHz Palomino
	at CeBIT '2001.
-- 
Dieter Nützel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
Cognitive Systems Group
Vogt-Kölln-Straße 30
D-22527 Hamburg, Germany

email: nuetzel@kogs.informatik.uni-hamburg.de
@home: Dieter.Nuetzel@hamburg.de

             reply	other threads:[~2001-06-13 22:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 22:23 Dieter Nützel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-13 12:35 Changing CPU Speed while running Linux Sven Geggus
2001-06-13 13:21 ` Arjan van de Ven
2001-06-13 13:41   ` Magnus Sandberg
2001-06-13 13:49     ` Dave Jones
2001-06-14 13:12   ` Pavel Machek
2001-06-16 10:46     ` arjan
2001-06-16 13:23     ` Alan Cox
2001-06-16 13:56       ` Ian Stirling

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=20010613221355Z264238-17720+3532@vger.kernel.org \
    --to=dieter.nuetzel@hamburg.de \
    --cc=acpi@phobos.fachschaften.tu-muenchen.de \
    --cc=arjanv@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 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.