From: Karol Kozimor <sziwan@hell.org.pl>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dtor_core@ameritech.net>
Subject: Re: [2.6.0-mm2] PM timer still has problems
Date: Sat, 17 Jan 2004 02:54:47 +0100 [thread overview]
Message-ID: <20040117015447.GA30456@hell.org.pl> (raw)
In-Reply-To: <200401052332.24739.dtor_core@ameritech.net>
Thus wrote Dmitry Torokhov:
> Or that Karol's laptop has ACPI PM timer that is accessed through the
> memory (ACPI_ADR_SPACE_SYSTEM_MEMORY), is there such implementations?
> Right now timer_pm.c only supports IO-port based timer access.
Apparently, the PM timer now works as of 2.6.1-mm4:
#v+
Detected 1700.569 MHz processor.
Using pmtmr for high-res timesource
#v-
But the BogoMIPS loop is still wrong:
#v+
Calibrating delay loop... 1683.45 BogoMIPS
#v-
It looks as if it needed to be multiplied by two, right?
Additionally, the /proc/cpuinfo is not updated on governor change (I'm
using the speedstep-ich driver which otherwise works fine), although the
real CPU frequency certainly is. I'm not sure if this is in any way
related though.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan@hell.org.pl
next prev parent reply other threads:[~2004-01-17 1:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 20:48 [2.6.0-mm2] PM timer still has problems Karol Kozimor
2003-12-31 4:02 ` Andrew Morton
2004-01-04 0:44 ` Karol Kozimor
2004-01-05 6:17 ` Dmitry Torokhov
2004-01-05 12:18 ` Karol Kozimor
2004-01-06 8:31 ` john stultz
2004-01-07 6:30 ` Dmitry Torokhov
2004-01-07 17:01 ` john stultz
2004-03-29 15:44 ` Karol Kozimor
2004-01-05 22:11 ` john stultz
2004-01-05 22:17 ` Karol Kozimor
2004-01-05 22:32 ` john stultz
2004-01-05 22:54 ` Karol Kozimor
2004-01-05 23:18 ` Karol Kozimor
2004-01-05 23:30 ` john stultz
2004-01-06 4:32 ` Dmitry Torokhov
2004-01-17 1:54 ` Karol Kozimor [this message]
2004-01-24 0:55 ` Karol Kozimor
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=20040117015447.GA30456@hell.org.pl \
--to=sziwan@hell.org.pl \
--cc=dtor_core@ameritech.net \
--cc=johnstul@us.ibm.com \
--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