Messages in this thread | | | Date | Thu, 08 Jan 2015 17:05:44 +0200 | From | Raimonds Cicans <> | Subject | Re: Questions about IOMMU & PCIe switch |
| |
On 08.01.2015 10:34, Clemens Ladisch wrote: > Raimonds Cicans wrote: >> https://github.com/ljalves/linux_media/issues/66 > If the TBS driver works, why don't you use it? 1) driver is not stable in 24x7 setups
2) driver use old DVBAPI. This cause problems with some user space programs.
3) TBS recommends to use card in MSI interrupt mode but this mode on IOMMU systems do not work: card is able to find transponders and tune to it but can not receive any data
4) I use GRSecurity patched kernels but external media drivers are incompatible with such kernels. I am forced to use driver source code injection in kernel from project https://github.com/bas-t/saa716x-intree which injects few drivers from https://github.com/ljalves/linux_media in kernel source tree.
5) I prefer open source drivers, but TBS drivers are half way open - open back-end drivers and closed front-end drivers.
> > The WARNING from the kernel log indicates a hardware bug in the PCIe > bridge. Do you have the same card, and do you also get this warning > with kernel 3.16? 1) I have same card with same revision number
2) affected computer is Intel based but mine is AMD based
3) I can not test kernel 3.16 because I had IOMMU related regression in kernels 3.14-3.17 (AMD-Vi: Completion-Wait loop timed out) On other kernels I do not have such warning, but starting from kernel 3.17.7 I have IOMMU related messages with my other card (TBS 6981):
AMD-Vi: Event logged [IO_PAGE_FAULT device=08:00.0 domain=0x001c address=0x0000000001355000 flags=0x0000]
and
WARNING: CPU: 0 PID: 13204 at drivers/iommu/amd_iommu.c:2625 dma_ops_domain_unmap.part.9+0x4d/0x56()
Because TBS 6981 driver is included in kernel I contacted yesterday linux-media mailing list, but not received answer yet.
Raimonds Cicans
| |