cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Bruno Ducrot <ducrot@poupinou.org>,
	cpufreq@www.linux.org.uk, aeriksson@fastmail.fm,
	davej@redhat.com
Subject: Re: add new p3m model
Date: Mon, 15 Mar 2004 15:45:28 +0100	[thread overview]
Message-ID: <20040315144528.GC7069@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040315143827.GA9696@dominikbrodowski.de>


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

On Mon, Mar 15, 2004 at 03:38:27PM +0100, Dominik Brodowski wrote:
> On Mon, Mar 15, 2004 at 03:21:01PM +0100, Arjan van de Ven wrote:
> > 
> > On Sun, Mar 14, 2004 at 03:34:07PM +0100, Dominik Brodowski wrote:
> > > On Mon, Mar 08, 2004 at 12:15:31PM +0100, 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....
> > > 
> > > Can you send a /proc/cpuinfo, please?
> > 
> > processor	: 0
> > vendor_id	: GenuineIntel
> > cpu family	: 6
> > model		: 11
> > model name	: Mobile Intel(R) Celeron(TM) CPU         1200MHz
>                                   ^^^^^^^
> so it's not a mobile Pentium III-M as you said before; but a Celeron. 
> Celeron's don't support SpeedStep [*].

Hmmmm. Dell provides a windows driver for it..

[-- 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-15 14:45 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 [this message]
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=20040315144528.GC7069@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=aeriksson@fastmail.fm \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=ducrot@poupinou.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