Difference between revisions of "TerraTec Cinergy C DVB-C"

From LinuxTVWiki
Jump to: navigation, search
(CI support)
(Known Issues)
Line 105: Line 105:
 
==External Links==
 
==External Links==
 
* [http://tven.terratec.net/modules.php?op=modload&name=News&file=article&sid=267 Terratec product page]
 
* [http://tven.terratec.net/modules.php?op=modload&name=News&file=article&sid=267 Terratec product page]
 +
 +
==Known Issues==
 +
 +
* Working around i2c bus probing interference with ivtv [[http://www.linuxtv.org/pipermail/linux-dvb/2007-August/020087.html]]
  
 
[[Category:Hardware]]
 
[[Category:Hardware]]
 
[[Category:PCI]]
 
[[Category:PCI]]
 
[[Category:DVB-C]]
 
[[Category:DVB-C]]

Revision as of 16:24, 25 January 2009


This Article is a Stub or is Incomplete

This article, or sections contained within it, requires expansion. Help is needed to make this article more informative.

A DVB-C PCI card from TerraTec.

Drivers: work in progress; see below

Overview/Features

Looks to be a clone of the Azurewave/Twinhan AD-CP400 (VP-2040) [1]

Components Used

  • NXP/Philips CU1216 module
    • NXP/Philips TDA10023 (demodulator)
  • Mantis (bridge)

Identification

$ lspci -v -s 01:01.0
01:01.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01)
       Subsystem: TERRATEC Electronic GmbH Unknown device 1178
       Flags: bus master, medium devsel, latency 64, IRQ 22
       Memory at cfdff000 (32-bit, prefetchable) [size=4K]
$ lspci -vvn -s 01:01.0
01:01.0 0480: 1822:4e35 (rev 01)
        Subsystem: 153b:1178
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort+ <MAbort- >SERR- <PERR-
        Latency: 64 (2000ns min, 63750ns max)
        Interrupt: pin A routed to IRQ 22
        Region 0: Memory at cfdff000 (32-bit, prefetchable) [size=4K]


Other Images

Making it Work

Firmware

No firmware required.

Installing the driver

Foreword

Kernel 2.6.28 released on 24.12.2008 works with the mantis driver in the s2-liplianin repository.

The mantis-multiproto driver has been tested with Ubuntu Hardy (2.6.24?) on the 28.11.2008. CAM/CI is not working with current mantis for me. I have a crash when scanning or zapping with the CAM inserted. Take the CAM module out if you have one for the moment! (Is this also true for the new driver??)

Install mantis driver

Recommended: install the latest mantis drivers like this.

sudo apt-get install mercurial
hg clone http://mercurial.intuxication.org/hg/s2-liplianin
cd s2-liplianin
make
sudo make install
sudo reboot

Old mantis-multiproto repository intstructions. May not compile with latest kernels.

cd /usr/src
sudo apt-get install mercurial
sudo hg clone http://jusst.de/hg/mantis  
cd mantis
sudo make
sudo make install
sudo reboot

Sample kernel output

With latest build from http://jusst.de/hg/mantis:

[   47.563542] found a VP-2040 PCI DVB-C device on (01:01.0),
[   47.563543]     Mantis Rev 1 [153b:1178], irq: 22, latency: 64
[   47.563545]     memory: 0xcfdff000, mmio: 0xf89de000
[   47.566227]     MAC Address=[00:08:ca:1c:73:1d]
[   47.566254] mantis_alloc_buffers (0): DMA=0x37850000 cpu=0xf7850000 size=65536
[   47.566292] mantis_alloc_buffers (0): RISC=0x37913000 cpu=0xf7913000 size=1000
[   47.566332] DVB: registering new adapter (Mantis dvb adapter)
[   48.086203] mantis_frontend_init (0): Probing for CU1216 (DVB-C)
[   48.088334] mantis_frontend_init (0): found Philips CU1216 DVB-C frontend 0x0c
[   48.088378] mantis_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach success
[   48.088424] DVB: registering frontend 0 (Philips TDA10023 DVB-C)...
[   54.367799] mantis_ack_wait (0): Slave RACK Fail !

Remote Control Support

For the old driver (Manu's) RC works after applying the following patch. See [2]

NOTE: I wonder why this patch has not been merged into the trunk. Does it break anything?

Regarding the new driver. I think the remote is supported already out-of-the box. Can anybody confirm that?

CI support

CI/CAM support for the optional CI module is not working yet (30.10.2014)

External Links

Known Issues

  • Working around i2c bus probing interference with ivtv [[3]]