public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: matthias brill <matthias.brill@akamail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: banias with different (unusual?) model_name
Date: Sat, 21 Aug 2004 13:53:16 +0200	[thread overview]
Message-ID: <20040821115316.GA2582@akamail.com> (raw)
In-Reply-To: <1093008335.30968.32.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

hi alan, jeremy

On Fri, Aug 20, 2004 at 02:25:36PM +0100, Alan Cox wrote:
> > i've found a pentium-m banias which reports "Mobile Genuine Intel(R)
> > processor       1400MHz" in /proc/cpuinfo.  this (strange?) signature
> > prevents speedstep-centrino.c from working properly.
> 
> Signatures appear to be BIOS set so that would make sense.

that fact wasn't obvious to me -- i've updated the BIOS and the strange
banias signature is now gone.  it reports the expected "Intel(R)
Pentium(R) M processor 1400MHz" string now.

in excess the "ACPI-behaviour" changes from "totally broken" to "not
working" which is kind of a progress... 8-}


On Fri, Aug 20, 2004 at 07:19:31PM -0700, Jeremy Fitzhardinge wrote:
> Yeah, there seem to be a few of these around.  I'm just not certain that
> they're identical to "normal" Banias as far as operating points go.

it seems that the reported value depends on the mental health of the
BIOS-programmer at hand, therefore the suplied string might not be
trustworthy.

if i understand correctly, the type of the cpu can be determined by
looking at the family, model and stepping -- assuming that these values
are reported directly  by the CPUID (0FA2) instruction. 

the BIOS supplied model_name string in speedstep-centrino.c is parsed to
get the clock cycle time of the cpu.  is this actually supposed to be
the "right" way (or worse: the only way) to get this information?


thias

-- 
Matthias Brill <matthias.brill@akamail.com>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-21 11:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20  9:33 banias with different (unusual?) model_name matthias brill
2004-08-20 13:25 ` Alan Cox
2004-08-21 11:53   ` matthias brill [this message]
2004-08-23 11:13     ` Dave Jones
2004-08-21  2:19 ` Jeremy Fitzhardinge

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=20040821115316.GA2582@akamail.com \
    --to=matthias.brill@akamail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cpufreq@www.linux.org.uk \
    --cc=jeremy@goop.org \
    --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