From: visyz@visyz.net
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Pentium III (Coppermine) cpufreq support
Date: Thu, 29 Jan 2004 15:28:24 -0500 [thread overview]
Message-ID: <20040129202824.GA7866@visyz.net> (raw)
In-Reply-To: <20040129105041.GV25416@poupinou.org>
From Ducrot Bruno on Thu, Jan 29, 2004 at 11:50:41AM +0100:
> On Thu, Jan 29, 2004 at 12:16:00AM -0500, visyz@visyz.net wrote:
> > So, I think I'm one of the 3 people in the world who have a Mobile
> > Pentium III (Coppermine).
>
> I receive more emails on this topics than 'two'...
Pardon the attitude. I was getting a bit angry at my laptop for not
working with your speedstep systems. I didn't mean to come across quite
like i did.
> > Heh. Yeah. anyways. I have an HP Omnibook 4150B, which amounts to the
> > aforementioned coppermine (with speeds from 233-450mhz), on a
> > 440BX/ZX/DX bridge. I tried out the test program to see if it's usable,
> > and while 1 bit did change, it was in GOP 0x0034, not 0x0038. Or maybe
> > that's the other way around. Basically, the one that was supposed to
> > change didn't, and the one that wasn't, did.
>
> What program? Mine? Also are you sure you looked in the web page.
> It's up to the manufacturer to *decide* what GPO to use. So there
> is *no* possibility to know the correct GPO pin.
The one available at http://www.poupinou.org/cpufreq/
and yes, while I was reading around the website, I got the impression
that the dumped logs were /not/ to be emailed to you directly anymore.
At this point, I'm thinking I mixed up the various cpufreq pages I've
been looking at.
If you're still interested in a fairly old laptop's speedstep, I'll
follow the instructions on your page and send you the results later.
====
Again, I must apologize to you as a group. My manners were forgotten.
~Gibby
next prev parent reply other threads:[~2004-01-29 20:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 5:16 Pentium III (Coppermine) cpufreq support visyz
2004-01-29 9:26 ` Dominik Brodowski
2004-01-29 8:50 ` aeriksson2
2004-01-29 11:35 ` Ducrot Bruno
2004-01-29 9:31 ` aeriksson
2004-01-29 12:39 ` Ducrot Bruno
2004-01-29 10:40 ` Anders Eriksson
2004-01-29 14:26 ` Ducrot Bruno
2004-01-29 13:18 ` aeriksson2
2004-01-29 16:10 ` Ducrot Bruno
2004-01-29 10:56 ` Ducrot Bruno
2004-01-29 20:47 ` visyz
2004-01-29 10:50 ` Ducrot Bruno
2004-01-29 20:28 ` visyz [this message]
2004-01-30 9:25 ` Ducrot Bruno
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=20040129202824.GA7866@visyz.net \
--to=visyz@visyz.net \
--cc=cpufreq@www.linux.org.uk \
--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