public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Felix von Leitner <felix-linuxkernel@fefe.de>
Cc: Adam Belay <abelay@novell.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, cpufreq@ZenII.linux.org.uk
Subject: Re: 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10
Date: Thu, 24 Mar 2005 15:33:52 -0800	[thread overview]
Message-ID: <42434E60.1060209@goop.org> (raw)
In-Reply-To: <20050322222943.GA10442@codeblau.de>

Felix von Leitner wrote:

>>ACPI is the preferred (and only standardized) method of controlling cpu
>>throttling on x86 systems.
>>    
>>
>
>  1. I don't trust ACPI
>  2. my battery runs out quicker with ACPI compared to cpufreq
>
>I _really_ _really_ don't want ACPI.  No, really not.  This is no idle
>decision.  My current notebook is the only hardware I have ever seen
>enabling ACPI not completely break Linux.  Of all my 10+ machines,
>including my other 3 ones that are actually in use.
>  
>
Unfortunately, the Dothans *REQUIRE* some degree of ACPI support; the
speedfreq-centrino needs to extract a table from ACPI to know what are
valid operating (voltage/frequency) points to use for the CPU.  The
patch you're using is definitely wrong in principle, though if it works
for you in practice then by all means use it.

The problem is that there are 4 different voltage grades of Dothan -
VID#A to VID#D - and there doesn't appear to be a way to tell what grade
a CPU is from software at runtime; this is a problem because there's no
one set of voltages you can use across all 4 grades (they have
non-overlapping voltage limits).  It's unknown whether running a Dothan
out of voltage spec will cause reliability problems or damage.

    J

  reply	other threads:[~2005-03-24 23:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 20:21 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10 Felix von Leitner
2005-03-12  1:32 ` Andrew Morton
2005-03-13 21:30   ` Felix von Leitner
2005-03-12  1:33 ` Andrew Morton
2005-03-22  0:33   ` Andrew Morton
2005-03-22  2:18     ` Johannes Stezenbach
2005-03-22 16:22       ` Johannes Stezenbach
2005-03-24 11:59   ` [PATCH] [IPV6] Fix address/interface handling according to the scoping architecture (is Re: 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10) YOSHIFUJI Hideaki / 吉藤英明
2005-04-25 19:57     ` IPv6 has trouble assigning an interface Felix von Leitner
2005-04-25 21:00       ` Pekka Savola
2005-04-26  6:10         ` Felix von Leitner
2005-04-27 22:57           ` Kyle Moffett
2005-04-27 23:31             ` David Stevens
2005-03-12  1:35 ` 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10 Andrew Morton
2005-03-12  3:54   ` Adam Belay
2005-03-22  0:32     ` Andrew Morton
2005-03-22  1:20       ` Adam Belay
2005-03-22 22:29         ` Felix von Leitner
2005-03-24 23:33           ` Jeremy Fitzhardinge [this message]
2005-03-25  0:17             ` Felix von Leitner
2005-03-25 13:37         ` Bruno Ducrot
2005-03-13 21:31   ` Felix von Leitner
2005-03-12  3:51 ` Adam Belay
     [not found] <3GZyA-16B-17@gated-at.bofh.it>
2005-03-12  5:06 ` Robert Hancock
2005-03-12  5:19   ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2005-03-12 10:24 Stefan Rompf
2005-03-12 20:34 ` Greg KH

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=42434E60.1060209@goop.org \
    --to=jeremy@goop.org \
    --cc=abelay@novell.com \
    --cc=akpm@osdl.org \
    --cc=cpufreq@ZenII.linux.org.uk \
    --cc=felix-linuxkernel@fefe.de \
    --cc=linux-kernel@vger.kernel.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