> Has it convinced you to include the Titanium 400 MHz into the future
> cpufreq supported models?
Your numbers look good. Send me a patch :)
Ben.
Hi Ben
Am Sonntag, 15. Juni 2003 15:52 schrieb Benjamin Herrenschmidt:
> On Thu, 2003-06-12 at 16:00, Krisztian Mark Szentes wrote:
> > On Friday 23 May 2003 00:48, Segher Boessenkool wrote:
> > > Krisztian Mark Szentes wrote:
> > > > I wonder why there is no /proc/cpufreq on my Titanium PowerBoo
On Thu, 2003-06-12 at 16:00, Krisztian Mark Szentes wrote:
> On Friday 23 May 2003 00:48, Segher Boessenkool wrote:
> > Krisztian Mark Szentes wrote:
> > > I wonder why there is no /proc/cpufreq on my Titanium PowerBook G4
> > > (400 MHz).
> > Because no-one filled in the right values yet.
> ...
>
On Friday 13 June 2003 12:49, Krisztian Mark Szentes wrote:
> On Thursday 12 June 2003 16:06, Benjamin Herrenschmidt wrote:
> > Can you change #undef DEBUG_FREQ to #define DEBUG_FREQ in
> > pmac_cpufreq.c ?
> >
I am still about to compile. Now since the upgrade, kernel 2.4.20-ben10
simply does not
On Fri, 2003-06-13 at 14:09, Russell King wrote:
> On Fri, Jun 13, 2003 at 12:53:18PM +0200, Benjamin Herrenschmidt wrote:
> > The bogomips is recalculated based on what I think is the new
> > frequency, so the value may be wrong. With DEBUG_FREQ, I re-do a
> > measure and print the number in dmesg
On Fri, Jun 13, 2003 at 12:53:18PM +0200, Benjamin Herrenschmidt wrote:
> The bogomips is recalculated based on what I think is the new
> frequency, so the value may be wrong. With DEBUG_FREQ, I re-do a
> measure and print the number in dmesg (the bogomips in /proc/cpuinfo
> is still the one recalc
On Thursday 12 June 2003 16:06, Benjamin Herrenschmidt wrote:
> Can you change #undef DEBUG_FREQ to #define DEBUG_FREQ in pmac_cpufreq.c
> ?
>
> That will force the driver to recalc the bogomips on speed change. Once
> done, check that the recalculated bogomips changes to about 600 at
> low speed a
The bogomips is recalculated based on what I think is the new
frequency, so the value may be wrong. With DEBUG_FREQ, I re-do a
measure and print the number in dmesg (the bogomips in /proc/cpuinfo
is still the one recalculated, not the one re-mesured).
So set DEBUG_FREQ and tell me what dmesg says
On Thursday 12 June 2003 16:06, Benjamin Herrenschmidt wrote:
> Can you change #undef DEBUG_FREQ to #define DEBUG_FREQ in pmac_cpufreq.c
unfortunately, I apt-get upgraded gcc in the meantime and the gcc compiler
now stops with an internal error. :-(
I gotta investigate further into it (if it sto
Hi,
Benjamin Herrenschmidt wrote:
>
> > The time reported by xpmumon and klaptopd have increased by some estimated
> > 10%. (from 180 Min to 200 Min.)
> >
> > As far as I can tell, it runs as fine. I will report any trouble.
>
> Can you change #undef DEBUG_FREQ to #define DEBUG_FREQ in pmac_
> The time reported by xpmumon and klaptopd have increased by some estimated
> 10%. (from 180 Min to 200 Min.)
>
> As far as I can tell, it runs as fine. I will report any trouble.
Can you change #undef DEBUG_FREQ to #define DEBUG_FREQ in pmac_cpufreq.c ?
That will force the driver to recalc
On Friday 23 May 2003 00:48, Segher Boessenkool wrote:
> Krisztian Mark Szentes wrote:
> > I wonder why there is no /proc/cpufreq on my Titanium PowerBook G4
> > (400 MHz).
> Because no-one filled in the right values yet.
...
> I seem to remember the PowerBook3,2 @ 400 has a low speed of
> 300MHz,
Krisztian Mark Szentes wrote:
Hi
I wonder why there is no /proc/cpufreq on my Titanium PowerBook G4 (400 MHz).
Because no-one filled in the right values yet.
In linux-2.4.20/arch/ppc/platforms/pmac_cpufreq.c it says:
/* Currently, we support the following machines:
*
* - Titanium Power
Hi
I wonder why there is no /proc/cpufreq on my Titanium PowerBook G4 (400 MHz).
I use the plain vanilla kernel.org 2.4.20 kernel compiled with the benh10 and
mh6 patches. I also have no cpufreq related error messages in syslog.
In .config it says:
CONFIG_CPU_FREQ=y
# CONFIG_CPU_FREQ_24_API is
14 matches
Mail list logo
