linux-kernel - Re: PCI riser cards and PCI irq routing, etc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070221201303.GH22464@csclub.uwaterloo.ca>
Date:	Wed, 21 Feb 2007 15:13:03 -0500
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Udo van den Heuvel <udovdh@...all.nl>
Cc:	linux-kernel@...r.kernel.org, Krzysztof Halasa <khc@...waw.pl>,
	Alistair John Strachan <s0348365@....ed.ac.uk>
Subject: Re: PCI riser cards and PCI irq routing, etc

On Wed, Feb 21, 2007 at 07:11:06PM +0100, Udo van den Heuvel wrote:
> BTW:
> 
> 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.

Unfortunately, on bus 0, which is always the main bus of a system, there
is no such thing as normal.  The BIOS knows how the mainboard is wired
and hence knows how to assign IRQs.  It is only ones you get past bus 0
and onto secondary busses behind bridges that fixed rules apply since
that is when things have to work universally.  So in your case, via can
do whatever they want with IRQs for each DN, since they know the layout
of the mainboard.  The problem with riser cards without a pci bridge
chip, is that they try to modify bus 0 without the knowledge of the
board maker, which means the bios won't have a clue how it is wired.
Use of any riser card not explicitly supported by the board is hence
unsupported and really not recommended.

> (...)
> 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]
> 
> 01:00.0 VGA compatible controller: VIA Technologies, Inc. UniChrome Pro
> IGP (rev
>  01) (prog-if 00 [VGA])
>         Subsystem: VIA Technologies, Inc. UniChrome Pro IGP
>         Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16
>         Memory at f4000000 (32-bit, prefetchable) [size=64M]
>         Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
>         [virtual] Expansion ROM at fc000000 [disabled] [size=64K]
>         Capabilities: [60] Power Management version 2
>         Capabilities: [70] AGP version 3.0
> 
> How can I find out what INT_A/B/C/D line is mapped to what irq?

Read the manual/developer guide.

--
Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/