All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Michael Clark <mclark@metaparadigm.com>
Cc: michael@mage.metaparadigm.com, cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: static freq table support for Pentium M Dothan
Date: Wed, 18 Aug 2004 15:45:06 -0700	[thread overview]
Message-ID: <1092869106.3133.1.camel@localhost> (raw)
In-Reply-To: <E1Bwu3z-0007gV-4Q@mage.metaparadigm.com>

On Tue, 2004-08-17 at 10:51 +0800, Michael Clark wrote:
> Having all of the voltages in the code (VID#A through VID#D) is really
> more for the purposes of completeness. The VID#A voltages after some
> thought are the most conservative setting (also same as seen in the ACPI
> tables of my Thinkpad), as the max voltage of the Dothans is 1.6, having
> the higher voltage will allow for greater power supply tolerance.

I was considering this approach, but I got concerned because the voltage
ranges of VID#A and VID#D don't overlap - so by using VID#A voltages on
a #D CPU, you'd be driving it out of spec.

	J

  parent reply	other threads:[~2004-08-18 22:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17  2:51 static freq table support for Pentium M Dothan Michael Clark
2004-08-17 22:04 ` Oliver Antwerpen
2004-08-18  9:44   ` Bruno Ducrot
2004-08-18 22:45 ` Jeremy Fitzhardinge [this message]
2004-09-08 19:59 ` Stefan Tomanek
2004-09-08 21:31   ` Dominik Brodowski
2004-09-08 21:43     ` Stefan Tomanek
2004-09-08 22:01       ` Dominik Brodowski
2004-09-08 23:07         ` Stefan Tomanek
2004-09-09  7:00           ` Dominik Brodowski
2004-09-09  8:54             ` Stefan Tomanek
2004-09-09  8:58           ` Bruno Ducrot
2004-09-09 15:33             ` Dominik Brodowski
2004-09-09 18:41             ` Stefan Tomanek

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=1092869106.3133.1.camel@localhost \
    --to=jeremy@goop.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=mclark@metaparadigm.com \
    --cc=michael@mage.metaparadigm.com \
    /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.