Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965155AbWEaWDb (ORCPT ); Wed, 31 May 2006 18:03:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965198AbWEaWDb (ORCPT ); Wed, 31 May 2006 18:03:31 -0400 Received: from linux01.gwdg.de ([134.76.13.21]:23186 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S965155AbWEaWDa (ORCPT ); Wed, 31 May 2006 18:03:30 -0400 Date: Thu, 1 Jun 2006 00:03:27 +0200 (MEST) From: Jan Engelhardt To: Keith Chew cc: Erik Mouw , linux-kernel@vger.kernel.org Subject: Re: IO APIC IRQ assignment In-Reply-To: <20f65d530605300705l60bfcca7k47a41c95bf42a0ef@mail.gmail.com> Message-ID: References: <20f65d530605300521q1d56c3a3t84be3d92f1df0c14@mail.gmail.com> <20060530135017.GD5151@harddisk-recovery.com> <20f65d530605300705l60bfcca7k47a41c95bf42a0ef@mail.gmail.com> 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: 829 Lines: 26 >> >> Or the engineer means that in legacy PIC mode the IRQs are shared, but >> in APIC mode they can be separated. That is a different thing, cause in >> that case the IRQ lines are not physically connected, but put together >> in PIC mode and can again be separated by using APIC mode. > > Ah, you could be right here. In the BIOS, there an option to > enable/disable APIC, which corresponds to what you are suggesting > above. > Plus CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y but I guess you already have these. Jan Engelhardt -- - 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/