From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Dave Jones <davej@codemonkey.org.uk>,
cpufreq@lists.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: cpufreq longhaul locks up
Date: Fri, 04 May 2007 22:11:44 +0200 [thread overview]
Message-ID: <463B9380.5090503@interia.pl> (raw)
In-Reply-To: <Pine.LNX.4.61.0705042042270.18504@yvahk01.tjqt.qr>
>> Btw. I've been writting many times: if You want to use ondemand with
>> Longhaul You don't need cpufreq at all.
>
> Does VIA Nehemiah do hardware-driven autoregulation like Transmeta
> Crusoe too? (I suspect no, have not seen that happen.)
No.
>> It is just one another cool gadget for You.
>> Longhaul wasn't designed to change frequency often.
>
> Is there a way I can start with a specific governor (powersave) right
> from the start so that all devices that Linux will initialize assume
> the CPU runs at <choose something> MHz?
You have to search cpufreq mail list archives. I think that I saw
patch recently.
>> It has big latency and requires so much preparation that it isn't worth
>> if You don't need to save power or cool down CPU.
>
> I found frequency switching on my VIA to be fast enough.
Timer frequency equal to 1000Hz?
> Jan
Rafa³
----------------------------------------------------------------------
Wicie, rozumicie....
Zobacz >>> http://link.interia.pl/f1a74
WARNING: multiple messages have this Message-ID (diff)
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Dave Jones <davej@codemonkey.org.uk>,
cpufreq@lists.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: cpufreq longhaul locks up
Date: Fri, 04 May 2007 22:11:44 +0200 [thread overview]
Message-ID: <463B9380.5090503@interia.pl> (raw)
In-Reply-To: <Pine.LNX.4.61.0705042042270.18504@yvahk01.tjqt.qr>
>> Btw. I've been writting many times: if You want to use ondemand with
>> Longhaul You don't need cpufreq at all.
>
> Does VIA Nehemiah do hardware-driven autoregulation like Transmeta
> Crusoe too? (I suspect no, have not seen that happen.)
No.
>> It is just one another cool gadget for You.
>> Longhaul wasn't designed to change frequency often.
>
> Is there a way I can start with a specific governor (powersave) right
> from the start so that all devices that Linux will initialize assume
> the CPU runs at <choose something> MHz?
You have to search cpufreq mail list archives. I think that I saw
patch recently.
>> It has big latency and requires so much preparation that it isn't worth
>> if You don't need to save power or cool down CPU.
>
> I found frequency switching on my VIA to be fast enough.
Timer frequency equal to 1000Hz?
> Jan
Rafał
----------------------------------------------------------------------
Wicie, rozumicie....
Zobacz >>> http://link.interia.pl/f1a74
next prev parent reply other threads:[~2007-05-04 20:11 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 10:16 cpufreq longhaul locks up Jan Engelhardt
2007-05-04 11:36 ` Wander Winkelhorst
2007-05-04 11:51 ` Jan Engelhardt
2007-05-04 11:51 ` Jan Engelhardt
2007-05-04 17:08 ` Rafał Bilski
2007-05-04 17:08 ` Rafał Bilski
2007-05-04 17:42 ` Chuck Ebbert
2007-05-04 17:42 ` Chuck Ebbert
2007-05-04 18:40 ` Rafał Bilski
2007-05-04 18:08 ` Wander Winkelhorst
2007-05-04 19:00 ` Rafał Bilski
2007-05-04 19:00 ` Rafał Bilski
2007-05-04 18:48 ` Jan Engelhardt
2007-05-04 18:48 ` Jan Engelhardt
2007-05-04 20:11 ` Rafał Bilski [this message]
2007-05-04 20:11 ` Rafał Bilski
2007-05-04 21:03 ` Jan Engelhardt
2007-05-04 21:03 ` Jan Engelhardt
2007-05-04 20:37 ` john stultz
2007-05-04 21:02 ` Jan Engelhardt
2007-05-04 22:49 ` john stultz
2007-05-04 23:32 ` Jan Engelhardt
2007-05-05 4:03 ` Rafał Bilski
2007-05-05 8:00 ` Jan Engelhardt
2007-05-05 8:00 ` Jan Engelhardt
2007-05-05 13:58 ` Rafał Bilski
2007-05-05 13:58 ` Rafał Bilski
2007-05-05 18:13 ` Jan Engelhardt
2007-05-05 18:13 ` Jan Engelhardt
2007-05-04 22:20 ` David Johnson
2007-05-04 22:20 ` David Johnson
2007-05-04 23:37 ` Jan Engelhardt
2007-05-04 23:37 ` Jan Engelhardt
2007-05-05 5:40 ` Rafał Bilski
2007-05-05 5:40 ` Rafał Bilski
2007-05-05 8:44 ` Wander Winkelhorst
2007-05-05 14:02 ` Rafał Bilski
2007-05-05 14:02 ` Rafał Bilski
2007-05-05 17:48 ` Rafał Bilski
2007-05-05 17:48 ` Rafał Bilski
2007-05-05 18:42 ` Jan Engelhardt
2007-05-05 18:42 ` Jan Engelhardt
2007-05-05 19:58 ` Rafał Bilski
2007-05-05 19:58 ` Rafał Bilski
2007-05-05 20:30 ` Jan Engelhardt
2007-05-05 20:30 ` Jan Engelhardt
2007-05-05 20:50 ` Jan Engelhardt
2007-05-05 20:50 ` Jan Engelhardt
2007-05-05 21:32 ` Rafał Bilski
2007-05-06 7:53 ` Jan Engelhardt
2007-05-06 7:53 ` Jan Engelhardt
2007-05-06 5:12 ` Rafał Bilski
2007-05-06 5:12 ` Rafał Bilski
2007-05-06 8:03 ` Jan Engelhardt
2007-05-06 8:03 ` Jan Engelhardt
2007-05-06 9:23 ` Rafał Bilski
2007-05-06 9:23 ` Rafał Bilski
2007-05-06 9:32 ` Jan Engelhardt
2007-05-06 10:25 ` Rafał Bilski
2007-05-06 10:25 ` Rafał Bilski
2007-05-06 11:33 ` Jan Engelhardt
2007-05-06 12:20 ` Rafał Bilski
2007-05-05 9:37 ` Jan Engelhardt
2007-05-05 9:37 ` Jan Engelhardt
2007-05-05 14:10 ` Rafał Bilski
2007-05-05 14:10 ` Rafał Bilski
2007-05-05 17:38 ` Jan Engelhardt
2007-05-05 17:38 ` Jan Engelhardt
2007-05-05 18:04 ` Rafał Bilski
2007-05-05 18:04 ` Rafał Bilski
2007-05-05 18:23 ` Jan Engelhardt
2007-05-05 18:23 ` Jan Engelhardt
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=463B9380.5090503@interia.pl \
--to=rafalbilski@interia.pl \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=jengelh@linux01.gwdg.de \
--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.