From: Krzysztof Halasa <khc@pm.waw.pl>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: linux-kernel@vger.kernel.org,
Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Subject: Re: PCI riser cards and PCI irq routing, etc
Date: Wed, 21 Feb 2007 20:54:50 +0100 [thread overview]
Message-ID: <m3tzxfqoad.fsf@maximus.localdomain> (raw)
In-Reply-To: <45DC8B3A.2080301@xs4all.nl> (Udo van den Heuvel's message of "Wed, 21 Feb 2007 19:11:06 +0100")
Udo van den Heuvel <udovdh@xs4all.nl> writes:
> Is the situation, with default DN setting of 19 as displayed below,
> `normal` w.r.t. interrupts?
> I mean: Both the DVB card with DN19 and the Unichrome Pro video adapter
> have the same irq although they are on different busses.
It's normal (and consistent with EPIA-M). The first UHCI USB (#0)
could get it, too (but it may be connected differently with IO-APIC,
I haven't checked).
> How can I find out what INT_A/B/C/D line is mapped to what irq?
That "INT_A/B/C/D" stuff depends on the point of view. In the BIOS
setup you can select some IRQs (which Linux could change anyway)
but it's a chipset-centric view (not very useful here).
Every PCI card have INT_A/B/C/D signals and they are (may be) remapped
on the riser card and on the motherboard.
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-02-21 19:54 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 14:07 PCI riser cards and PCI irq routing, etc Udo van den Heuvel
2007-02-18 15:54 ` Lennart Sorensen
2007-02-18 16:15 ` Udo van den Heuvel
2007-02-18 19:39 ` Lennart Sorensen
2007-02-19 1:50 ` Alistair John Strachan
2007-02-19 4:04 ` Udo van den Heuvel
2007-02-19 15:17 ` Lennart Sorensen
2007-02-19 15:43 ` Udo van den Heuvel
2007-02-19 17:13 ` Lennart Sorensen
2007-02-19 15:09 ` Udo van den Heuvel
2007-02-19 20:37 ` Krzysztof Halasa
2007-02-20 4:17 ` Udo van den Heuvel
2007-02-20 14:56 ` Alistair John Strachan
2007-02-20 15:44 ` Udo van den Heuvel
2007-02-20 19:51 ` Alistair John Strachan
2007-02-21 9:24 ` Udo van den Heuvel
2007-02-21 12:24 ` Krzysztof Halasa
2007-02-21 14:59 ` Udo van den Heuvel
2007-02-21 15:12 ` Lennart Sorensen
[not found] ` <m3hctfqjna.fsf@maximus.localdomain>
2007-02-21 22:40 ` Lennart Sorensen
2007-02-21 23:55 ` Alistair John Strachan
2007-02-22 1:19 ` Krzysztof Halasa
2007-02-23 15:45 ` Udo van den Heuvel
2007-02-23 15:54 ` Lennart Sorensen
2007-02-23 17:55 ` Krzysztof Halasa
2007-02-23 18:17 ` Udo van den Heuvel
2007-02-23 19:42 ` Krzysztof Halasa
2007-03-03 14:35 ` Udo van den Heuvel
2007-02-23 18:12 ` Krzysztof Halasa
2007-02-23 18:44 ` Udo van den Heuvel
2007-02-23 20:00 ` Krzysztof Halasa
2007-02-25 15:59 ` Udo van den Heuvel
2007-02-22 1:16 ` Krzysztof Halasa
2007-02-21 18:11 ` Udo van den Heuvel
2007-02-21 19:54 ` Krzysztof Halasa [this message]
2007-02-21 20:13 ` Lennart Sorensen
2007-02-21 19:36 ` Krzysztof Halasa
2007-02-21 13:44 ` Lennart Sorensen
2007-02-21 18:55 ` Udo van den Heuvel
2007-02-20 20:47 ` Krzysztof Halasa
2007-02-20 21:51 ` Lennart Sorensen
2007-02-21 0:11 ` Krzysztof Halasa
2007-02-21 13:46 ` Lennart Sorensen
2007-02-20 4:35 ` Udo van den Heuvel
2007-02-21 0:03 ` Krzysztof Halasa
2007-02-18 20:50 ` Krzysztof Halasa
2007-02-18 20:42 ` Krzysztof Halasa
2007-02-19 15:03 ` Lennart Sorensen
2007-02-19 18:23 ` Krzysztof Halasa
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=m3tzxfqoad.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=s0348365@sms.ed.ac.uk \
--cc=udovdh@xs4all.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.