From: Jiri Slaby <jslaby@suse.cz>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
lenb@kernel.org, linux-pci@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH 1/1] ACPI: pci_irq, add PRT_ quirk for IBM Bartolo
Date: Wed, 30 Jun 2010 11:20:51 +0200 [thread overview]
Message-ID: <4C2B0C73.9050200@suse.cz> (raw)
In-Reply-To: <AANLkTimkElR1u-iRyFfCEQR5VTZvcyEIGQodfmFNtbC_@mail.gmail.com>
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
next prev parent reply other threads:[~2010-06-30 9:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 21:21 Jiri Slaby
2010-06-28 0:14 ` Robert Hancock
2010-06-28 6:13 ` Jiri Slaby
2010-06-28 17:14 ` Matthew Garrett
2010-06-28 20:12 ` Jiri Slaby
2010-06-28 20:48 ` Matthew Garrett
2010-06-28 21:37 ` Robert Hancock
2010-06-29 18:40 ` Jiri Slaby
2010-06-29 23:23 ` Robert Hancock
2010-06-30 9:20 ` Jiri Slaby [this message]
2010-06-30 9:40 ` Jiri Slaby
2010-07-06 0:28 ` Robert Hancock
2010-07-19 16:29 ` Jiri Slaby
2010-07-19 19:19 ` Robert Hancock
2010-07-20 9:29 ` Jiri Slaby
2010-08-24 8:11 ` Jiri Slaby
2010-08-24 23:25 ` Robert Hancock
2010-08-30 7:36 ` Jiri Slaby
2010-09-07 11:02 ` Jiri Slaby
2010-09-07 14:40 ` Robert Hancock
2010-09-08 15:05 ` Jiri Slaby
2011-04-12 8:48 ` [RFC " Jiri Slaby
2011-04-12 8:58 ` Jiri Slaby
2011-04-12 15:56 ` Jesse Barnes
2011-04-12 15:59 ` Matthew Garrett
2011-04-14 9:40 ` Jiri Slaby
2011-05-13 7:18 ` Jiri Slaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C2B0C73.9050200@suse.cz \
--to=jslaby@suse.cz \
--cc=hancockrwd@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome