From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Slaby Subject: Re: [PATCH 1/1] ACPI: pci_irq, add PRT_ quirk for IBM Bartolo Date: Wed, 30 Jun 2010 11:20:51 +0200 Message-ID: <4C2B0C73.9050200@suse.cz> References: <1277673679-21458-1-git-send-email-jslaby@suse.cz> <4C27E965.80508@gmail.com> <4C283D84.6080504@suse.cz> <20100628171410.GA27367@srcf.ucam.org> <4C290245.2040001@suse.cz> <20100628204820.GA32503@srcf.ucam.org> <4C2A3E27.4060407@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from fg-out-1718.google.com ([72.14.220.154]:48786 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752147Ab0F3JUw (ORCPT ); Wed, 30 Jun 2010 05:20:52 -0400 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Robert Hancock Cc: Matthew Garrett , lenb@kernel.org, linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, Jesse Barnes On 06/30/2010 01:23 AM, Robert Hancock wrote: > What kind of slot is it, and what kind of device was being used, > something designed for this machine or just some random card? It's a netmos 9835 serial card with 2 ports. PCI, there is no PCIe in the machine as far as I can see. > Can they > tell what IRQ the device is reportedly using in Windows and if it > matches what Linux reports? I can ask them. What I know is that with acpi=noirq (or with the quirk) the IRQ number is 10, with acpi without the quirk, it's 11: PCI: setting IRQ 2 as level-triggered serial 0000:00:09.0: found PCI INT A -> IRQ 2 0000:00:09.0: ttyS4 at I/O 0x1898 (irq = 10) is a 16550A 0000:00:09.0: ttyS5 at I/O 0x1890 (irq = 10) is a 16550A ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered serial 0000:00:09.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11 0000:00:09.0: ttyS4 at I/O 0x1898 (irq = 11) is a 16550A 0000:00:09.0: ttyS5 at I/O 0x1890 (irq = 11) is a 16550A I still no point in comparing this to Windows' setup. We can't find out whether it is quirked or better (without some bug) handled there. regards, -- js suse labs