All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Bas Mevissen <ml@basmevissen.nl>
Cc: cpufreq mailing list <cpufreq@www.linux.org.uk>
Subject: Re: add new p3m model
Date: Mon, 8 Mar 2004 12:46:02 +0100	[thread overview]
Message-ID: <20040308114602.GF14593@devserv.devel.redhat.com> (raw)
In-Reply-To: <404C5D64.5040508@basmevissen.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1044 bytes --]

On Mon, Mar 08, 2004 at 12:47:48PM +0100, Bas Mevissen wrote:
> Arjan van de Ven wrote:
> >Hi,
> >
> >the patch below adds support for my laptop (Dell Inspiron 2600) which has
> >ebx return 7 for the p3 mobile in it....
> >
> >Greetings,
> >    Arjan van de Ven
> >
> >
> >--- linux-2.6.3/arch/i386/kernel/cpu/cpufreq/speedstep-lib.c~	2004-03-07 
> >15:31:51.305251000 +0100
> >+++ linux-2.6.3/arch/i386/kernel/cpu/cpufreq/speedstep-lib.c	2004-03-07 
> >15:31:51.305251000 +0100
> >@@ -265,10 +265,10 @@
> > 	case 0x0B: /* Intel PIII [Tualatin] */
> > 		/* cpuid_ebx(1) is 0x04 for desktop PIII,
> >-		                   0x06 for mobile PIII-M */
> >+		                   0x06 and 0x07 for mobile PIII-M */
> 
> It is only text, but shouldn't that read "0x06 or 0x07"? It is one of 
> the two and not both values at the same time.

hehe probably.

> 
> BTW. Is this 0x07 also according specs or just what happens on the i2k6?

I have been unable to find a spec for this unfortionatly. Intel has this
like great confusing mess wrt finding docs 

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

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq

  reply	other threads:[~2004-03-08 11:46 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 [this message]
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
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=20040308114602.GF14593@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ml@basmevissen.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.