Re: [PATCH 1/1] ACPI: pci_irq, add PRT_ quirk for IBM Bartolo

[Jiri Slaby <jslaby@suse.cz>]

On 07/06/2010 02:28 AM, Robert Hancock wrote:
> On 06/30/2010 03:20 AM, Jiri Slaby wrote:
>> 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.
> 
> Well, you can see if Windows shows IRQ 10 or 11 for that device..

But how can I find out which link it is routed to in Windows? Without
that information the number is meaningless, no?

thanks,
-- 
js
suse labs