linux-kernel - Re: Dual slot PCI riser messes up ivtv

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: <m3bqf8ro72.fsf@maximus.localdomain>
Date:	Fri, 22 Jun 2007 17:41:53 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	pharon@...il.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Dual slot PCI riser messes up ivtv

Islam Amer <pharon@...il.com> writes:

> [   37.298400] ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 17 (level,
> low) -> IRQ 22
> [   37.298413] saa7134[0]: found at 0000:00:05.0, rev: 1, irq: 22,
> latency: 32, mmio: 0x0

The riser card must not be very active as the device(s) are sitting
on bus #0, that means no PCI-PCI bridge.

BTW: REQ/GraNT lines are not a problem and probably that's what the
manufacturer considers "active". IDSEL lines may be a problem (they
define device#, must not clash with other devices, and it would be
nice if the BIOS recognized them). IRQ lines are usually the main
problem.

OTOH I wonder if we should make it possible to force IRQs on
per-device basis? Or is it already possible?
-- 
Krzysztof Halasa
-
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/