From: "Vitaly Wool" <vitalywool@gmail.com>
To: "Auke Kok" <auke-jan.h.kok@intel.com>
Cc: "David Singleton" <daviado@gmail.com>,
linux-pm@lists.osdl.org,
"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] OpPoint summary
Date: Thu, 14 Sep 2006 22:15:55 +0400 [thread overview]
Message-ID: <acd2a5930609141115u67c3fdcaqc304e0fbf5d8b04f@mail.gmail.com> (raw)
In-Reply-To: <45099095.3020303@intel.com>
On 9/14/06, Auke Kok <auke-jan.h.kok@intel.com> wrote:
> David Singleton wrote:
>
> > +static const struct cpu_id cpu_ids[] = {
> > + [CPU_BANIAS] = { 6, 9, 5 },
> > + [CPU_DOTHAN_A1] = { 6, 13, 1 },
> > + [CPU_DOTHAN_A2] = { 6, 13, 2 },
> > + [CPU_DOTHAN_B0] = { 6, 13, 6 },
> > + [CPU_MP4HT_D0] = {15, 3, 4 },
> > + [CPU_MP4HT_E0] = {15, 4, 1 },
> > +};
>
>
> Any reason why { 6, 13, 8 } is missing? My lenovo T43 identifies itself as such:
>
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 13
> model name : Intel(R) Pentium(R) M processor 1.86GHz
> stepping : 8
>
> I'm not sure a Dothan B1 exists, but some postings suggest even C0 and C1 are
> valid steppings. I'm sure OpPoint could work with those as well.
Heh, that shows pretty much that the approach itself is not good...
And this is only beginning.
Vitaly
next prev parent reply other threads:[~2006-09-14 18:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <450516E8.9010403@gmail.com>
[not found] ` <20060911082025.GD1898@elf.ucw.cz>
[not found] ` <b0623b9bb79afacc77cddc6e39c96b62@nomadgs.com>
[not found] ` <20060911195546.GB11901@elf.ucw.cz>
[not found] ` <4505CCDA.8020501@gmail.com>
[not found] ` <20060911210026.GG11901@elf.ucw.cz>
[not found] ` <4505DDA6.8080603@gmail.com>
2006-09-11 22:56 ` cpufreq terminally broken [was Re: community PM requirements/issues and PowerOP] Pavel Machek
2006-09-12 0:17 ` Mark Gross
2006-09-12 3:37 ` Greg KH
2006-09-13 23:50 ` [linux-pm] " David Singleton
2006-09-14 5:30 ` Vitaly Wool
2006-09-14 5:55 ` OpPoint summary Greg KH
2006-09-14 7:35 ` [linux-pm] " Vitaly Wool
2006-09-14 16:55 ` David Singleton
2006-09-14 17:03 ` David Singleton
2006-09-14 17:07 ` David Singleton
2006-09-14 17:25 ` Auke Kok
2006-09-14 18:15 ` Vitaly Wool [this message]
2006-09-14 18:17 ` David Singleton
2006-09-17 17:48 ` Pavel Machek
2006-09-18 14:33 ` [linux-pm] " Richard A. Griffiths
2006-09-18 16:13 ` Matthew Locke
2006-09-14 17:11 ` David Singleton
2006-09-17 5:07 ` David Singleton
2006-09-17 12:56 ` Pavel Machek
2006-09-17 12:58 ` Pavel Machek
2006-09-17 22:43 ` [linux-pm] " Matthew Locke
2006-09-12 8:33 ` cpufreq terminally broken [was Re: community PM requirements/issues and PowerOP] Pavel Machek
2006-09-12 9:10 ` [linux-pm] " Vitaly Wool
2006-09-12 9:16 ` Pavel Machek
2006-09-12 9:23 ` Vitaly Wool
2006-09-14 15:04 ` Mark Gross
2006-09-14 14:58 ` Mark Gross
2006-09-18 13:36 [linux-pm] OpPoint summary Scott E. Preece
2006-09-18 13:46 ` Pavel Machek
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=acd2a5930609141115u67c3fdcaqc304e0fbf5d8b04f@mail.gmail.com \
--to=vitalywool@gmail.com \
--cc=auke-jan.h.kok@intel.com \
--cc=daviado@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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
all inboxes | Powered by JetHome®