linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Anton Blanchard <anton@linuxcare.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: allow notsc option for buggy cpus
Date: Sat, 10 Mar 2001 22:21:46 +0200	[thread overview]
Message-ID: <20010310222146.L23336@mea-ext.zmailer.org> (raw)
In-Reply-To: <20010310115828.A7514@linuxcare.com> <E14bY2D-00063q-00@the-village.bc.nu>
In-Reply-To: <E14bY2D-00063q-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sat, Mar 10, 2001 at 01:19:03AM +0000

On Sat, Mar 10, 2001 at 01:19:03AM +0000, Alan Cox wrote:
> > My IBM Thinkpad 600E changes between 100MHz and 400MHz depending if the
> > power is on. This means gettimeofday goes backwards if you boot with the
> Intel speedstep CPU. 
> 
> > Even so, we should really catch these cpus at run time. 
> Intel are being remarkably reluctant on the documentation front.  We have
> the AMD speed change docs, but the intel ones (chipset not cpu based
> primarily) don't seem to be publically available. In fact the 815M manual
> looks like someone quite pointedly went through and removed the relevant
> material before publication

	Isn't that one of the things that the ACPI is for ?
	Aren't we supposed to use  ACPI  for this ?

/Matti Aarnio

  parent reply	other threads:[~2001-03-10 20:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-10  0:58 [PATCH]: allow notsc option for buggy cpus Anton Blanchard
2001-03-10  1:19 ` Alan Cox
2001-03-10  2:09   ` David Huggins-Daines
2001-03-10 11:36     ` Alan Cox
2001-03-12 15:21       ` Jes Sorensen
2001-03-10 20:21   ` Matti Aarnio [this message]
2001-03-10 20:28     ` Alan Cox
2001-03-11 14:38   ` Anton Blanchard
2001-03-11 14:49     ` Alan Cox

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=20010310222146.L23336@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=anton@linuxcare.com.au \
    --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;
as well as URLs for NNTP newsgroup(s).