lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHFNz9Kj=+Gip-n=4tGaXfUXqc0QHoZgjZJ9s-0sTTFzTv4hxA@mail.gmail.com>
Date:	Thu, 8 Jan 2015 21:02:10 +0530
From:	Manu Abraham <abraham.manu@...il.com>
To:	Raimonds Cicans <ray@...llo.lv>
Cc:	Clemens Ladisch <clemens@...isch.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Questions about IOMMU & PCIe switch

On Thu, Jan 8, 2015 at 8:35 PM, Raimonds Cicans <ray@...llo.lv> wrote:
> 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.

It shouldn't. It is backward compatible.

>
> 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

TBS didn't even have the courtesy to say thanks, but still.
They don't have any clue on the driver.

You shouldn't use MSI mode on most systems unless you
are sure that your machine works perfectly well with MSI
mode.

You should simply use standard interrupt mode, if you are
unsure.

In any sense, that card looks a bit odd:

1. It doesn't need a PCIe switch, nor that CPLD in there for
the fact that it is using a SAA7160, rather than an E version,
which thereby support 4 FGPI inputs (4 simultaneous TS's)
(Redundant components)

2. But in any sense, the PCIe switch is transparent, It doesn't
need any programming. All what you can do with the PCIe
switch is to reprogram the lines to it, nothing more. In any
case, if your card is detected, there's no point in playing with
the PCIe switch

3. The TS failure in a while can most likely be attributed to
bad CPLD programming. On the cards that I have worked
with, they've worked pretty well.


Regards,

Manu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ