Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268439AbUJJTEX (ORCPT ); Sun, 10 Oct 2004 15:04:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268447AbUJJTEX (ORCPT ); Sun, 10 Oct 2004 15:04:23 -0400 Received: from pollux.ds.pg.gda.pl ([153.19.208.7]:31750 "EHLO pollux.ds.pg.gda.pl") by vger.kernel.org with ESMTP id S268439AbUJJTEN (ORCPT ); Sun, 10 Oct 2004 15:04:13 -0400 Date: Sun, 10 Oct 2004 20:04:09 +0100 (BST) From: "Maciej W. Rozycki" To: Linus Torvalds Cc: Len Brown , Andrew Morton , Kernel Mailing List , ACPI Developers Subject: Re: [BKPATCH] LAPIC fix for 2.6 In-Reply-To: Message-ID: References: <1097429707.30734.21.camel@d845pe> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 909 Lines: 22 On Sun, 10 Oct 2004, Linus Torvalds wrote: > > Hi Linus, please do a > > > > bk pull bk://linux-acpi.bkbits.net/26-latest-release > > Ok, this version of the patch suddenly looks like a real bug-fix in that > it now makes the command line options "lapic"/"nolapic" a lot more > logical. Hmm, any particular reason to keep the local APIC disabled by default? Most BIOS vendors keep it disabled just because it's easier to get stuff set up this way -- with the APIC enabled you need to do the same steps to program the 8259As as with the APIC disabled, plus program the APIC itself, which provides no gain to BIOS itself or to DOS, so why bother? Maciej - 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/