From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: Krzysztof Halasa <khc@pm.waw.pl>
Subject: Re: PCI riser cards and PCI irq routing, etc
Date: Fri, 23 Feb 2007 19:44:56 +0100 [thread overview]
Message-ID: <45DF3628.8060706@xs4all.nl> (raw)
In-Reply-To: <m3slcw68vr.fsf@maximus.localdomain>
Krzysztof Halasa wrote:
> Udo van den Heuvel <udovdh@xs4all.nl> writes:
>
>> I will try a different case with a different dual PCI riser card soon.
>> This Morex riser has DN20-31 or so, so more options.
>
> OTOH I wonder how do they use DN 21-31? The board uses lines AD11 to AD31
> (21 lines) for selecting devices #0 - #20. 32-bit PCI bus has only 32
> address/data lines :-)
>
> Perhaps they mean AD20-AD31 lines = device #9 - #0x14=20? If that is
> the case, you can try:
> - their "DN30" = device 0x13 = 19, which is apparently what the VIA riser
> card does,
> - their "DN21" = device 0xA = 10, which could work as well.
>
> I'm afraid both would require (different) soldering.
My dmesg says:
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 11 12) *5
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 10 *11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 *10 11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [ALKA] (IRQs *20)
ACPI: PCI Interrupt Link [ALKB] (IRQs *21)
ACPI: PCI Interrupt Link [ALKC] (IRQs *22)
ACPI: PCI Interrupt Link [ALKD] (IRQs *23), disabled.
lspci -v says:
00:13.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: TERRATEC Electronic GmbH Unknown device 1157
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at fdffc000 (32-bit, non-prefetchable) [size=512]
00:14.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: TERRATEC Electronic GmbH Unknown device 1155
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fdffb000 (32-bit, non-prefetchable) [size=512]
Does this provide additional info to you?
http://www.itx-warehouse.co.uk/Product.aspx?ProductID=410 says:
Description VIA Dual PCI Riser
The EXT-PCI is a PCI riser card which expands a PCI slot into two PCI slots.
EXT-PCI slot 1 (lower slot) uses the system resources (Device ID, INT)
of the PCI slot of the motherboard.
EXT-PCI slot 2 (Upper slot) uses device 19 and INT_A.
Upper slot has the problems. TranquilPC does not even respond anymore.
The lower slot is a copy of the normal (single) PCI slot w.r.t. devcie
and irq, it has DN20 and irq 20.
dmesg links ALNKA to IRQ 20. So if ALNKA is INTA both PCI cards should
share IRQ 20?
next prev parent reply other threads:[~2007-02-23 18:45 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 [this message]
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
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=45DF3628.8060706@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.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