From: Raimonds Cicans <ray@apollo.lv>
To: Clemens Ladisch <clemens@ladisch.de>, linux-kernel@vger.kernel.org
Subject: Re: Questions about IOMMU & PCIe switch
Date: Wed, 07 Jan 2015 16:04:59 +0200 [thread overview]
Message-ID: <54AD3D0B.6060501@apollo.lv> (raw)
In-Reply-To: <54AD21E2.2020100@ladisch.de>
On 07.01.2015 14:09, Clemens Ladisch wrote:
> Raimonds Cicans wrote:
>> We have two kinds of PCIe cards:
>> A1 - based on chip B
>> A2 - based on same chip B but behind PCIe switch
>>
>> Card A1 work flawlessly in any configuration,
>> but card A2 work flawlessly only if system
>> lack IOMMU or have disabled IOMMU
> In theory, such a switch should be transparent.
>
>> Do we have to treat card with PCIe switch in special way?
> No. But the switch has to work correctly, and driver must be
> written correctly.
>
> Which switch? Which driver?
We talk about TBS 6285 Quad DVB-T PCIe receiver card.
Starting from version V20 manufacturer added Pericom
PCIe switch PI7C9X2G304SL.
Card have 2 out of kernel drivers:
1) Semi open from TBS:
http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v141225.zip
2) Open from: https://github.com/ljalves/linux_media
If you want more information you can look at open ticket:
https://github.com/ljalves/linux_media/issues/66
Raimonds Cicans
next prev parent reply other threads:[~2015-01-07 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 4:06 Questions about IOMMU & PCIe switch Raimonds Cicans
2015-01-07 12:09 ` Clemens Ladisch
2015-01-07 14:04 ` Raimonds Cicans [this message]
2015-01-08 8:34 ` Clemens Ladisch
2015-01-08 15:05 ` Raimonds Cicans
2015-01-08 15:32 ` Manu Abraham
-- strict thread matches above, loose matches on Subject: below --
2015-01-15 12:54 Luis Alves
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=54AD3D0B.6060501@apollo.lv \
--to=ray@apollo.lv \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
/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