From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "William Heimbigner" <icxcnika@mar.tar.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cpufreq default governor
Date: Tue, 24 Apr 2007 14:50:38 +0200 [thread overview]
Message-ID: <6bffcb0e0704240550x2c47cd1ap8101a9b0db5c6c7d@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704241235560.25153@server.thyself>
On 24/04/07, William Heimbigner <icxcnika@mar.tar.cc> wrote:
> On Tue, 24 Apr 2007, Michal Piotrowski wrote:
>
> > Hi William,
> >
> > On 24/04/07, William Heimbigner <icxcnika@mar.tar.cc> wrote:
> >> Question: is there some reason that kconfig does not allow for default
> >> governors of conservative/ondemand/powersave?
> >
> > Performance?
> >
> >> I'm not aware of any reason why one of those governors could not be used
> >> as default.
> >
> > My hardware doesn't work properly with ondemand governor. I hear
> > strange noises when frequency is changed.
> >
>
> That doesn't mean it isn't working, though.
I didn't say that cpufreq ondemand is broken. It's a hardware problem.
> I here weird noises if the cpu
> is clocked anywhere from 333MHz to 1GHz (sounds like an RD-D2 beeping
> noises in ultra high pitch?)
Yes, something like that.
>
> William Heimbigner
> icxcnika@mar.tar.cc
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group (PL)
(http://www.stardust.webpages.pl/ltg/)
LTG - Linux Testers Group (EN)
(http://www.stardust.webpages.pl/linux_testers_group_en/)
next prev parent reply other threads:[~2007-04-24 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 7:57 William Heimbigner
2007-04-24 8:34 ` Michal Piotrowski
2007-04-24 12:37 ` William Heimbigner
2007-04-24 12:50 ` Michal Piotrowski [this message]
2007-04-24 12:56 ` William Heimbigner
2007-04-24 13:07 ` Michal Piotrowski
2007-04-24 13:25 ` William Heimbigner
2007-04-24 17:56 ` Ian E. Morgan
2007-04-25 20:25 ` Lee Revell
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=6bffcb0e0704240550x2c47cd1ap8101a9b0db5c6c7d@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=icxcnika@mar.tar.cc \
--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
all inboxes | Powered by JetHome®