Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261552AbUAWM5n (ORCPT ); Fri, 23 Jan 2004 07:57:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266547AbUAWM5n (ORCPT ); Fri, 23 Jan 2004 07:57:43 -0500 Received: from aun.it.uu.se ([130.238.12.36]:59592 "EHLO aun.it.uu.se") by vger.kernel.org with ESMTP id S261552AbUAWM5m (ORCPT ); Fri, 23 Jan 2004 07:57:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16401.6720.115695.872847@alkaid.it.uu.se> Date: Fri, 23 Jan 2004 13:57:36 +0100 From: Mikael Pettersson To: "Maciej W. Rozycki" Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH][2.6] local APIC LVTT init bug In-Reply-To: References: <16400.9569.745184.16182@alkaid.it.uu.se> X-Mailer: VM 7.17 under Emacs 20.7.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 979 Lines: 25 Maciej W. Rozycki writes: > On Thu, 22 Jan 2004, Mikael Pettersson wrote: > > > __setup_APIC_LVTT() incorrectly sets i82489DX-only bits > > which are reserved in integrated local APICs, causing > > problems in some machines. Fixed in this patch by making > > this setting conditional. > > Sigh -- why can't designers keep such a trivial backwards > compatibility??? The integrated APIC was said to be backwards compatible > when introduced and so far all implementations used to. What you write > means that has been broken -- could please say which vendor to blame? The ASUS L3800C was mentioned. I don't know of any others. > Your proposal is therefore the only correct one. Thanks for confirming that. /Mikael - 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/