From: Clemens Koller <clemens.koller@anagramm.de>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Robert Hancock <hancockr@shaw.ca>,
pharon@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Dual slot PCI riser messes up ivtv
Date: Thu, 28 Jun 2007 19:04:38 +0200 [thread overview]
Message-ID: <4683EA26.6030306@anagramm.de> (raw)
In-Reply-To: <20070621162654.GA10008@csclub.uwaterloo.ca>
Hi, Lennart!
Lennart Sorensen schrieb:
> On Thu, Jun 28, 2007 at 05:32:48PM +0200, Clemens Koller wrote:
>> Robert Hancock schrieb:
>>> Islam Amer wrote:
>>>> I am trying to build a settop box with two cards, a PVR-150 and a DVB
>>>> card. The mini-ITX motherboard has only one PCI slot, so I bought an
>>>> active PCI riser.
>> Please define "active". Is there a PCI bridge chip on the riser card?
>> Or better: Tell us manufacturer and type of this PCI riser card and the
>> mini-ITX board.
>
> Certainly many riser cards only have jumpers to change the irq for the
> second slot, or some default built in remapping. And they may have id
> select pins to pick which slots they should pretend to be. From what I
> have read, via mini itx boards require a very specific design for riser
> boards, which isn't what most riser boards do. Other mini itx boards
> are probably different.
The main problem is the unknown BIOS support for the PCI configuration.
Maybe the manufacturer is at least willing to publish the default
configuration, so the PCI riser can be modified/fixed to the same
config. (Just call him and ask for the board designer... YMMV)
However, AFAIK this (re-)configuration can be done by the kernel, too.
(on embedded ppc platforms, the PCI mapping is done in the kernel)
At least from the electrical engineer's point of view it's not
difficult to modify a dumb passive PCI riser card to have the IRQ's and
REQ/GNTs routed and have the IDSEL soldered with 220 Ohms to the
proper AD line pin. (been there, done that)
(If somebody want's to mess around with that stuff, contact
me off list, it's getting OT here.)
> Certainly the simplest is a riser card with a proper pci bridge that
> creates a secondary pci bus with it's own device ids and maps the
> interrupts correctly. Then all that really matters is that the bios on
> the board supports pci bridges (a few companies actually manage to fail
> to support pci bridges at all in their bioses).
True. It might be more easy to get that running, hoping that
the BIOS enumerates the bridge right.
Kernel support shouldn't be an issue here as long as the
chip is supported.
Best greets,
--
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com
next prev parent reply other threads:[~2007-06-21 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ELPuDi4dcntxF8hk4oCNldcvgoc@ifi.uio.no>
2007-06-21 14:23 ` Dual slot PCI riser messes up ivtv Robert Hancock
2007-06-28 15:32 ` Clemens Koller
2007-06-21 16:26 ` Lennart Sorensen
2007-06-28 17:04 ` Clemens Koller [this message]
2007-06-24 14:27 ` Islam Amer
2007-06-24 16:24 ` Krzysztof Halasa
2007-06-24 18:44 ` Clemens Koller
2007-06-21 11:49 Islam Amer
2007-06-22 15:41 ` 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=4683EA26.6030306@anagramm.de \
--to=clemens.koller@anagramm.de \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--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