From: James Mabry <jamabryl@student.gc.maricopa.edu>
To: cpufreq <cpufreq@www.linux.org.uk>
Subject: Re: Athlon Mobile Support
Date: Wed, 02 Jul 2003 00:49:40 -0700 [thread overview]
Message-ID: <3F028E94.8020008@student.gc.maricopa.edu> (raw)
In-Reply-To: 3F0289AA.6090208@searchbroker.de
Lars Gemeinhardt wrote:
> one question - same answer!
Oops sorry. Thought the answer I was looking for would be different than
your previous. I'll try it out and report on how things went.
Reading more about cpufreq it sounds like this does not provide voltage
regulation? I'm using cpufreq in the hopes to greatly increase my
battery life. Should I expect this as a result? Thanks.
--
Slackware Linux -
Find out about the 4S rule.
www.slackware-advocacy.org/whyuse.html
Then try it out for yourself.
www.slackware.org
next prev parent reply other threads:[~2003-07-02 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 7:26 Athlon Mobile Support James Mabry
2003-07-02 7:28 ` Lars Gemeinhardt
2003-07-02 7:49 ` James Mabry [this message]
2003-07-02 7:55 ` Lars Gemeinhardt
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 7:36 Athlon Mobile support Iacopo Spalletti
2003-07-02 6:19 Iacopo Spalletti
2003-07-02 6:28 ` Lars Gemeinhardt
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=3F028E94.8020008@student.gc.maricopa.edu \
--to=jamabryl@student.gc.maricopa.edu \
--cc=cpufreq@www.linux.org.uk \
/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.