From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
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 15:59:51 +0100 [thread overview]
Message-ID: <45DC5E67.8060101@xs4all.nl> (raw)
In-Reply-To: <m3wt2bem13.fsf@maximus.localdomain>
Krzysztof Halasa wrote:
> Udo van den Heuvel <udovdh@xs4all.nl> writes:
>
>> So if my non-VIA riser card can use DN 19 and also INT_A things should work?
>
> That INT_A may be INT_A from their (motherboard) point of view, but
> the riser card doesn't know about that, it only knows INTs as seen
> at its PCI edge connector (so this INT_A here is meaningless).
>
> Device numbers aren't rotated but rather derived from address lines
> (address/data). AD0-31 lines are the same across the whole PCI bus.
> That means device numbers are independent of POV.
>
>> (assuming that VIA Epia EN BIOS 1.07 is enough to use this card)
>
> My VIA EPIA-M 600 is probably older than your one, so I'd assume
> it should work as well.
> When you configure 0x13 and 0x14, both devices get IRQs - that means
> the BIOS can see both of them.
But the IRQ for the DVB-T card doesn't work.
I would need to test the DVB-T card alone to be sure it has working IRQ.
If so, what would be the conclusion?
>> The DN is the only variable so INT lines are hardwired on the riser card?
>
> Yep. You just need a bit of soldering.
What IRQ rerouting would I need to try? 1 of 3 choices?
Or one best bet?
Udo
next prev parent reply other threads:[~2007-02-21 15:00 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 [this message]
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
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=45DC5E67.8060101@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=s0348365@sms.ed.ac.uk \
/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