Pinnacle PCTV 200e: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
m (some formatting etc)
m (minor edit)
Line 20: Line 20:


===Drivers===
===Drivers===
Currently there is no in kernel drivers for this device.
''provide the details of where the drivers and patches and necessary tools are available ... this means you''


However, experimental support does exist. The following drivers are needed for these devices:
====Current Status====
The code itself is already working. It just needs some cleanup and testing before it can be submitted. Everyone who wants to help, can do so. Just contact the [http://www.linuxtv.org/lists.php LinuxTV mailing list], or contact the developer [http://freeznet.ath.cx:81/public/contact.php directly].

Since the developers of this driver have virtually no time, no further development is being planned for now. So if you want the driver to be integrated into the official v4l-dvb tree before January 2008, you are welcome to do it yourself.

The following drivers are needed for these devices:
- dvb-usb.ko
- dvb-usb.ko
- pctv200e.ko
- pctv200e.ko
You need to use the v4l-dvb tree based on mrec's development and overwrite the files with the updated versions provided below. It's not the most eloquent solution, but ....
* [http://mcentral.de/hg/~mrec/v4l-dvb-kernel mrec's linuxtv-tree ''(not in sync with original linuxtv tree)'']
* [http://freeznet.ath.cx:81/files/pctv200e-juan-cleaned.zip updated files]


====Source Code====
====Current Status====
The drivers work, but the code itself needs some cleanup and further testing before it can be submitted. Everyone who wants to help can do so. Just contact the [http://www.linuxtv.org/lists.php LinuxTV mailing list], or contact the developer [http://freeznet.ath.cx:81/public/contact.php directly].
To use the driver, you need to use the v4l-dvb tree based on mrec's developement and overwrite the files with the updated versions provided below. It's not very professional. Neither are we :) ...


Since the developers of this driver have virtually no time, no further development is being planned for now. So if you want the driver to be integrated into the official v4l-dvb tree before January 2008, you are welcome to do it yourself.
* [http://mcentral.de/hg/~mrec/v4l-dvb-kernel mrec's linuxtv-tree ''(not in sync with original linuxtv tree)'']
* [http://freeznet.ath.cx:81/files/pctv200e-juan-cleaned.zip updated files]


====Development ToDo List====
====Development ToDo List====

Revision as of 19:12, 24 January 2008

A DVB-T USB 2.0 device from Pinnacle.

It is currently not supported in the LinuxTV tree, however, drivers do exist (see below).

Overview/Features

The PCTV 200e was first presented at CeBIT 2005, and is still available for about EUR 40. It is identical to some other Pinnacle models; the PCTV 260e, the PCTV 60e and the "PCTV DVB-T Pro USB". It comes with a detachable active antenna.

Components Used

  • Microtune MT2060 tuner (i2c addr: 0xC0)
  • Zarlink MT352 demodulator (i2c addr: 0x3e)
  • Cypress CY7C68013A (FX2LP) USB bridge

Identification

The output of lsusb -v provides that that it has a subsystem ID of: 2304:020e

Making it Work

Firmware

None required ?

Drivers

Currently there is no in kernel drivers for this device.

However, experimental support does exist. The following drivers are needed for these devices:

 - dvb-usb.ko
 - pctv200e.ko

You need to use the v4l-dvb tree based on mrec's development and overwrite the files with the updated versions provided below. It's not the most eloquent solution, but ....

Current Status

The drivers work, but the code itself needs some cleanup and further testing before it can be submitted. Everyone who wants to help can do so. Just contact the LinuxTV mailing list, or contact the developer directly.

Since the developers of this driver have virtually no time, no further development is being planned for now. So if you want the driver to be integrated into the official v4l-dvb tree before January 2008, you are welcome to do it yourself.

Development ToDo List

  • handle debug output
  • integrate into official v4l tree
  • do intensive testing
  • support the remote control

Sample kernel output

provide the relevant portion of dmesg here

Remote Controll Support

discuss support for the remote control here

External Links