(first data on tm5600) |
(more info) |
||
| Line 3: | Line 3: | ||
This page explains how the Trident TM5600 chipset works in Linux, in particular with the following product that embeds it: [http://www.konigelectronic.com/en_us/55831665 KÖNIG CMP-USBVG6] (bought [http://www.ascii-info.com/acquisition-video/3067-konig-editeur-audio-video-usb-20.html here] 30€). | This page explains how the Trident TM5600 chipset works in Linux, in particular with the following product that embeds it: [http://www.konigelectronic.com/en_us/55831665 KÖNIG CMP-USBVG6] (bought [http://www.ascii-info.com/acquisition-video/3067-konig-editeur-audio-video-usb-20.html here] 30€). | ||
First of all, Trident seems to be well known for refusing to help coding free drivers and even disclosing information about the chipsets, so that's a good reason not to buy it in the first place. | First of all, Trident seems to be well known for [http://www.redaelli.org/matteo-blog/2010/01/01/do-not-buy-dvb-usb-devices-with-trident-chipsets/ refusing to help coding free drivers] and even disclosing information about the chipsets, so that's a good reason not to buy it in the first place. | ||
The driver supporting this chipset is [http://www.linuxtv.org/wiki/index.php/Trident_TM6000 tm6000]. The kernel doesn't know the device in particular, but recognizes the chipset: | The driver supporting this chipset is [http://www.linuxtv.org/wiki/index.php/Trident_TM6000 tm6000]. The kernel doesn't know the device in particular, but recognizes the chipset: <code>tm6000: Found Generic tm5600 board</code>. | ||
'''Grabbing video works fine.''' You plug the USB, you run "mplayer tv://" and you have the image, it's as simple as that if your kernel was compiled with CONFIG_VIDEO_TM6000 (distribution's kernels are). | '''Grabbing video works fine.''' You plug the USB, you run "<code>mplayer tv://</code>" and you have the image, it's as simple as that if your kernel was compiled with <code>CONFIG_VIDEO_TM6000</code> (distribution's kernels are). With mplayer displaying the feed, it takes 20% of user space CPU on an AMD64 2GHz. | ||
The image is not very stable (it moves a bit), but I don't know how stable is the source being tested. There is a green line at the bottom of the image. | The image is not very stable (it moves up and down a bit), but I don't know how stable is the source being tested. There is a green line at the bottom of the image. | ||
Warnings from the kernel "<code>xc2028 2-0061: Error: firmware xc3028-v24.fw not found</code>" must not be fixed as explained on the [http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028 XC2028 page], because it crashes the driver, or at least it makes the device not work, I don't know why yet. | |||
Revision as of 03:29, 30 August 2012
TM5600 USB video grabber
This page explains how the Trident TM5600 chipset works in Linux, in particular with the following product that embeds it: KÖNIG CMP-USBVG6 (bought here 30€).
First of all, Trident seems to be well known for refusing to help coding free drivers and even disclosing information about the chipsets, so that's a good reason not to buy it in the first place.
The driver supporting this chipset is tm6000. The kernel doesn't know the device in particular, but recognizes the chipset: tm6000: Found Generic tm5600 board.
Grabbing video works fine. You plug the USB, you run "mplayer tv://" and you have the image, it's as simple as that if your kernel was compiled with CONFIG_VIDEO_TM6000 (distribution's kernels are). With mplayer displaying the feed, it takes 20% of user space CPU on an AMD64 2GHz.
The image is not very stable (it moves up and down a bit), but I don't know how stable is the source being tested. There is a green line at the bottom of the image.
Warnings from the kernel "xc2028 2-0061: Error: firmware xc3028-v24.fw not found" must not be fixed as explained on the XC2028 page, because it crashes the driver, or at least it makes the device not work, I don't know why yet.