Subject: Re: IO-APIC on nforce2 [PATCH]
From: Len Brown <len.brown@intel.com>
To: Christian =?ISO-8859-1?Q?Kr=F6ner?= 
	<christian.kroener@tu-harburg.de>
Cc: linux-kernel@vger.kernel.org, "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
       ross@datscreative.com.au
In-Reply-To: <200404142157.34502.christian.kroener@tu-harburg.de>
References: <200404131117.31306.ross@datscreative.com.au>
	 <1081893978.2251.653.camel@dhcppc4>
	 <200404141502.14023.ross@datscreative.com.au>
	 <200404142157.34502.christian.kroener@tu-harburg.de>
Content-Type: text/plain; charset=ISO-8859-1
Organization: 
Message-Id: <1081988224.15062.75.camel@dhcppc4>
Mime-Version: 1.0
Date: 14 Apr 2004 20:17:05 -0400
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 866
Lines: 24

On Wed, 2004-04-14 at 15:57, Christian Kr?ner wrote:

> This is simply great, any uncommon hi-load disappeared.
> Will something like this get into mainline soon, maybe with automatic chipset 
> detection?

I'm okay putting the bootparam and the workaround into the kernel,
for it is generic and we may find other platforms need it.

But I don't have a clean way to make it automatic.
This is a BIOS bug, so chipset ID will not always work.

We could list the BIOS in dmi_scan(), but I hate doing
that b/c then the vendor releases a new version of their
broken BIOS and the automatic workaround no longer works...

-Len


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/