From: Krzysztof Halasa <khc@pm.waw.pl>
To: pharon@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dual slot PCI riser messes up ivtv
Date: Fri, 22 Jun 2007 17:41:53 +0200 [thread overview]
Message-ID: <m3bqf8ro72.fsf@maximus.localdomain> (raw)
In-Reply-To: <1182426585.9143.2.camel@iamer-laptop> (Islam Amer's message of "Thu, 21 Jun 2007 14:49:45 +0300")
Islam Amer <pharon@gmail.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
next prev parent reply other threads:[~2007-06-22 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 11:49 Dual slot PCI riser messes up ivtv Islam Amer
2007-06-22 15:41 ` Krzysztof Halasa [this message]
[not found] <fa.ELPuDi4dcntxF8hk4oCNldcvgoc@ifi.uio.no>
2007-06-21 14:23 ` Robert Hancock
2007-06-28 15:32 ` Clemens Koller
2007-06-21 16:26 ` Lennart Sorensen
2007-06-28 17:04 ` Clemens Koller
2007-06-24 14:27 ` Islam Amer
2007-06-24 16:24 ` Krzysztof Halasa
2007-06-24 18:44 ` Clemens Koller
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=m3bqf8ro72.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=pharon@gmail.com \
/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