Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 4 Mar 2003 13:47:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 4 Mar 2003 13:47:16 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:4365 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Tue, 4 Mar 2003 13:47:15 -0500 Date: Tue, 4 Mar 2003 10:54:21 -0800 (PST) From: Linus Torvalds To: Ivan Kokshaysky cc: raarts@office.netland.nl, , , Donald Becker , Greg KH , jamal , Jeff Garzik , , , Robert Olsson Subject: Re: PCI init issues In-Reply-To: <20030304212648.A6455@jurassic.park.msu.ru> Message-ID: 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: 1178 Lines: 31 On Tue, 4 Mar 2003, Ivan Kokshaysky wrote: > > Indeed, looks like only pin 0 (INT_A of that card) is connected. :-( Well, I'd say it looks like the MP table _claims_ that only pin0 is connected. Remember: the claim was that this machine worked on WinXP. So there are at least two potential reasons for that: - The MP table is simply wrong, and WinXP gets the routing information from somewhere else (ie most likely ACPI) - The MP table is right, and only pin0 is connected, and WinXP only uses pin0 (ie it puts the card in some state where all irqs are shared across all of the four tulip chips). Maybe somebody can come up with other schenarios. It would be interesting to hear what "Device Manager" (or whatever it is called) unde WinXP claims the interrupts are on this machine... Are they all on irq 48 on XP too? Or has XP gotten magic knowledge somewhere (ACPI?) and they are on different irq's? Linus - 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/