2015 10:34, Raimonds Cicans wrote:
History of problem:
1) I own computer based on AMD Athlon(tm) II X2 240e Processor on Asus
M5A97 LE R2.0 motherboard
2) I own TBS6981 card (Dual DVB-S/S2 PCIe receiver, in kernel driver)
3) I used kernel 3.13.something
4) everything was fine
5) time to time I tried to
d write down
good/bad region and continue with first message and then do
new bisection for other message but on reduced region
Thank you.
Raimonds Cicans
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kern
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
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
special way?
How?
Where (PCI bridge driver? card's driver?)?
Any examples in kernel?
Thank you.
Raimonds Cicans
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kerne
t fully fixed?
d) Receiver's driver: likely
Questions:
1) What 'domain=0x001c' mean?
2) Where I can find definition of possible flags?
3) What kind of address is written in message?
- physical?
- virtual?
- address from devices point of view?
Thank you.
Raimo
6 matches
Mail list logo