[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070802115743.GB29735@srcf.ucam.org>
Date: Thu, 2 Aug 2007 12:57:43 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: trenn@...e.de, Adrian Schröter <adrian@...e.de>,
Knut Petersen <Knut_Petersen@...nline.de>,
linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>,
pavel@....cz, lenb@...nel.org, "Zhang, Rui" <rui.zhang@...el.com>,
Jean Delvare <khali@...ux-fr.org>,
Alexey Starikovskiy <aystarik@...il.com>
Subject: Re: 2.6.22 regression: thermal trip points
On Thu, Aug 02, 2007 at 12:59:47PM +0100, Alan Cox wrote:
> > I strongly suspect that the vast majority[1] of hardware that "needs"
> > the trip points changing works perfectly well under Windows, so it's
>
> Windows as I understand it has vendor mechanisms to allow the bits
> shipped with the OS to override/ignore just about everything trip points
> included. Lots of hardware that requires fixups in Linux and just works
> in Windows is not Linux bugs but Windows magic .inf files and other
> registry gunge done by the machine vendor. We see this in ATA, in power
> management and elsewhere.
I've seen no evidence that this happens with thermal trip points.
--
Matthew Garrett | mjg59@...f.ucam.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists