From: Pavel Machek <pavel@ucw.cz>
To: Bruno Ducrot <ducrot@poupinou.org>,
paul.devriendt@amd.com,
Cpufreq mailing list <cpufreq@www.linux.org.uk>
Subject: Re: My latest powernow-k8.c
Date: Fri, 19 Mar 2004 14:56:05 +0100 [thread overview]
Message-ID: <20040319135605.GD248@elf.ucw.cz> (raw)
In-Reply-To: <20040319133517.GA28122@dominikbrodowski.de>
Hi!
> > > > Attached are my latest .c and .h ... I am sending the whole files rather than patches, as a check that I did not miss a patch that you wanted. Mail here has been a little less reliable that one might wish for.
> > > >
> > > > I added back in the cpu number in the dprintks to aid MP debugging. I fixed a PSB problem where the battery limits were getting lost. And, I tweaked the smp processor init stuff as discussed in emails.
> > > >
> > > > I am still thinking about the FIXME where Dominik asked for more validity checking. So, that is still FIXME.
> > >
> > > Huh, now this is strange:
> > >
> > > root@amd:~# echo "0%88%88%powersave" > /proc/cpufreq
> > > root@amd:~# cat /proc/cpufreq
> > > minimum CPU frequency - maximum CPU frequency - policy
> > > CPU 0 1584000 kHz ( 88 %) - 1600000 kHz ( 88 %) - powersave
> > > root@amd:~#
>
> Why is this strange? Can you elaborate, please?
CPU can not do 1.584MHz. Why did it round 88% down to 1.584GHz but
maximum frequency 1.6GHz? Kernel 2.6.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-03-19 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99F2150714F93F448942F9A9F112634C1163C59A@txexmtae.amd.com>
2004-03-19 11:24 ` My latest powernow-k8.c Pavel Machek
2004-03-19 12:41 ` Bruno Ducrot
2004-03-19 13:35 ` Dominik Brodowski
2004-03-19 13:56 ` Pavel Machek [this message]
2004-03-19 14:33 ` Dominik Brodowski
2004-03-19 15:52 ` Bruno Ducrot
2004-03-20 8:28 ` Dominik Brodowski
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=20040319135605.GD248@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.org \
--cc=paul.devriendt@amd.com \
/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