cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot@poupinou.org>
To: aeriksson@fastmail.fm
Cc: Dave Jones <davej@redhat.com>,
	Arjan van de Ven <arjanv@redhat.com>,
	cpufreq@www.linux.org.uk
Subject: Re: speedstep capability checks
Date: Fri, 19 Mar 2004 12:06:37 +0100	[thread overview]
Message-ID: <20040319110637.GF28592@poupinou.org> (raw)
In-Reply-To: <20040318195720.D89C43F04@latitude.mynet.no-ip.org>

On Thu, Mar 18, 2004 at 08:57:20PM +0100, aeriksson@fastmail.fm wrote:
> 
> 
> davej@redhat.com said:
> >> A few SpeedStep-capable systems don't perform according to
> >> specification: the CPUID and/or some MSRs don't tell us the 
> >> CPU is SpeedStep capable even though it definitely is.
> 
> > Is there nothing in the errata documents about this ? 
> 
> <snip>
> 
> > I'd merge this really as a last resort, and it's beginning to sound
> > like we don't really have any options (other than not support those
> > broken boxes). Ugh. 
> 
> 
> ...and ducrot@poupinou.org replied:
> > There is nothing in any data sheets for the check anyway, other than
> > it's not possible to distinguish a PIII (coppermine) with Speedstep
> > technology from one without Speedstep technology.  There is nothing
> > in any spec update I'm aware. 
> 
> 
> So, is the patch ok to merge?

To be more precise: if you look only datasheets and spec update,
there is no check given, but there is an application note, and there
is no errata for that AN.
I still don't understand why for example it hasn't been included
in any spec update?

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  reply	other threads:[~2004-03-19 11:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-14 15:20 speedstep capability checks aeriksson
2004-03-15 14:15 ` Dominik Brodowski
2004-03-08 11:15   ` add new p3m model Arjan van de Ven
2004-03-08 11:47     ` Bas Mevissen
2004-03-08 11:46       ` Arjan van de Ven
2004-03-08 12:08         ` Bas Mevissen
2004-03-08 13:31     ` Bruno Ducrot
2004-03-14 14:34       ` Dominik Brodowski
2004-03-15 14:21         ` Arjan van de Ven
2004-03-15 14:38           ` Dominik Brodowski
2004-03-15 14:45             ` Arjan van de Ven
2004-03-15 15:46               ` Bruno Ducrot
2004-03-15 15:55                 ` Dave Jones
2004-03-15 14:20   ` speedstep capability checks Arjan van de Ven
2004-03-15 15:37     ` Bruno Ducrot
2004-03-15 19:25       ` aeriksson
2004-03-15 19:35         ` Bruno Ducrot
2004-03-15 19:44           ` Arjan van de Ven
2004-03-15 19:50         ` [updated patch] " Dominik Brodowski
2004-03-15 21:09   ` Dave Jones
2004-03-16  7:38     ` Dominik Brodowski
2004-03-16 13:01       ` Dave Jones
2004-03-16 15:01         ` Bruno Ducrot
2004-03-16 15:58           ` Dominik Brodowski
2004-03-16 16:00         ` Dominik Brodowski
2004-03-16 16:36           ` Bruno Ducrot
2004-03-18 19:57             ` aeriksson
2004-03-19 11:06               ` Bruno Ducrot [this message]
2004-03-15 18:36 ` Bruno Ducrot
2004-03-15 19:20   ` aeriksson
2004-03-15 19:36     ` Bruno Ducrot
2004-03-15 19:46     ` 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=20040319110637.GF28592@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=aeriksson@fastmail.fm \
    --cc=arjanv@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.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