From: thunder7@xs4all.nl
To: Inter filmati <interfc@jumpy.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cpufreq/powernowd limiting CPU frequency on kernels >=2.6.16
Date: Thu, 26 Oct 2006 21:01:42 +0200 [thread overview]
Message-ID: <20061026190142.GA31153@amd64.of.nowhere> (raw)
In-Reply-To: <001201c6f928$89c9a720$2b20ff27@flaviopc>
From: Inter filmati <interfc@jumpy.it>
Date: Thu, Oct 26, 2006 at 07:59:41PM +0200
> >
> >If you care about that changed, try to find out what patch caused this,
> >but in general, there's no support for overclocking in the kernel, and
> >bugreports from overclocked systems are frowned upon.
> >
> It would be kind to find out why the problem seems to show only from 2.6.16
> and not before, unfortunately I ain't so skilled to investigate into
> cpufreq source.
>
You could start by trying 2.6.16-rc1, -rc2, -rc3 and find out in which
kernel it changed. Then, read the changelog for that patch to find out
what changed in the cpufreq driver. So far, no great skill required.
Then, post here, mentioning which patch caused the different behaviour.
Jurriaan
--
Despite the best efforts of a quantum bigfoot drive (yes I know everyone
told me they suck, now I know they were right) 2.1.109ac1 is now available
Alan Cox announcing Linux 2.1.109ac1
Debian (Unstable) GNU/Linux 2.6.18-mm3 2x5042 bogomips load 0.91
prev parent reply other threads:[~2006-10-26 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 17:08 Inter filmati
2006-10-26 17:41 ` thunder7
2006-10-26 17:59 ` Inter filmati
2006-10-26 19:01 ` thunder7 [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=20061026190142.GA31153@amd64.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=interfc@jumpy.it \
--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®