From: Karol Kozimor <sziwan@hell.org.pl>
To: john stultz <johnstul@us.ibm.com>
Cc: Dominik Brodowski <linux@brodo.de>,
dtor_core@ameritech.net, acpi-devel@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] X86_PM_TIMER: /proc/cpuinfo doesn't get updated
Date: Wed, 17 Mar 2004 01:13:24 +0100 [thread overview]
Message-ID: <20040317001324.GA19180@hell.org.pl> (raw)
In-Reply-To: <1079479694.5408.47.camel@cog.beaverton.ibm.com>
Thus wrote john stultz:
> Hmm. This is untested, but I think this should do the trick.
Hmm... without the patch, neither cpu MHz nor bogomips are updated, with
the patch cpu MHz value seems correct (both using acpi.ko and
speedstep-ich.ko, but the bogomips is still at its initial value.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan@hell.org.pl
next prev parent reply other threads:[~2004-03-17 0:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040316182257.GA2734@dreamland.darkstar.lan>
[not found] ` <20040316194805.GC20014@picchio.gall.it>
2004-03-16 21:42 ` [ACPI] X86_PM_TIMER: /proc/cpuinfo doesn't get updated Karol Kozimor
2004-03-16 23:19 ` Dmitry Torokhov
2004-03-16 23:32 ` john stultz
2004-03-17 0:30 ` Dmitry Torokhov
2004-03-16 23:28 ` john stultz
2004-03-16 23:33 ` Dominik Brodowski
[not found] ` <1079484413.5408.56.camel@cog.beaverton.ibm.com>
2004-03-17 9:50 ` Dominik Brodowski
2004-03-18 20:55 ` [PATCH] linux-2.6.5-rc1_cpukhz-fix_A0.patch john stultz
2004-03-17 0:13 ` Karol Kozimor [this message]
2004-03-17 0:33 ` [ACPI] X86_PM_TIMER: /proc/cpuinfo doesn't get updated Dmitry Torokhov
[not found] <481113193@toto.iv>
[not found] ` <16471.43776.178128.198317@wombat.chubb.wattle.id.au>
[not found] ` <200403162340.57546.dtor_core@ameritech.net>
2004-03-17 9:53 ` Dominik Brodowski
2004-03-17 22:56 ` Nate Lawson
2004-03-18 8:51 ` Dominik Brodowski
2004-03-18 21:05 ` john stultz
2004-03-17 10:00 ` 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=20040317001324.GA19180@hell.org.pl \
--to=sziwan@hell.org.pl \
--cc=acpi-devel@lists.sourceforge.net \
--cc=dtor_core@ameritech.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
/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