From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: matthias.brill@akamail.com
Cc: jeremy@goop.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: banias with different (unusual?) model_name
Date: Fri, 20 Aug 2004 14:25:36 +0100 [thread overview]
Message-ID: <1093008335.30968.32.camel@localhost.localdomain> (raw)
In-Reply-To: <20040820093344.GA2923@akamail.com>
On Gwe, 2004-08-20 at 10:33, matthias brill wrote:
> hi jeremy
>
> 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.
> # diff -up arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c.default arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c
> --- arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c.default 2004-08-19 19:53:59.000000000 +0200
> +++ arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c 2004-08-19 20:49:06.000000000 +0200
> @@ -195,7 +195,7 @@ static struct cpufreq_frequency_table ba
>
> #define _BANIAS(cpuid, max, name) \
> { .cpu_id = cpuid, \
> - .model_name = "Intel(R) Pentium(R) M processor " name "MHz", \
> + .model_name = "Mobile Genuine Intel(R) processor " name "MHz", \
> .max_freq = (max)*1000, \
> .op_points = banias_##max, \
> }
>
You need a new entry "_WEIRDBANIAS" and entries in the table so that
you don't break other people by such a change but yes
> it seems that only the model_name is different for this CPU?
next prev parent reply other threads:[~2004-08-20 14:28 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 [this message]
2004-08-21 11:53 ` matthias brill
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=1093008335.30968.32.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.brill@akamail.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