Well, playing with developing of device driver, reverse engineering/disassembling of Windows driver TD3101_3104AV.sys, sniffing of usb protocol and extracting firmware got first result under 2.6.37.6 kernel:
kernel: [10116.711051] usb 1-3: new high speed USB device using ehci_hcd and address 10
kernel: [10116.825450] usb 1-3: New USB device found, idVendor=3100, idProduct=f200
kernel: [10116.825455] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
kernel: [10116.831143] td310x: Firmware CRC ok
kernel: [10116.846223] td310x: Firmware loading complete
kernel: [10116.846252] td310x: Waiting to soft reconnect device
kernel: [10116.876373] usb 1-3: USB disconnect, address 10
kernel: [10116.876416] td310x: Device disconnected
kernel: [10118.634047] usb 1-3: new high speed USB device using ehci_hcd and address 11
kernel: [10118.749853] usb 1-3: New USB device found, idVendor=3100, idProduct=f200
kernel: [10118.749858] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: [10118.749863] usb 1-3: Product: TD310X
kernel: [10118.749867] usb 1-3: Manufacturer: Conexant
kernel: [10118.783100] td310x: Manufacturer Conexant, product TD310X
kernel: [10118.783108] td310x: Hardware has 6 interfaces
kernel: [10118.783246] td310x: Interface #0 has 3 endpoints
kernel: [10118.783254] td310x: EP #1, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.783262] td310x: EP #1, type: bulk, dir: ->, packet: 512 bytes
kernel: [10118.783269] td310x: EP #2, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.783622] td310x: Interface #1 has 3 endpoints
kernel: [10118.783632] td310x: EP #1, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.783638] td310x: EP #1, type: bulk, dir: ->, packet: 512 bytes
kernel: [10118.783646] td310x: EP #2, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.784041] td310x: Interface #2 has 3 endpoints
kernel: [10118.784050] td310x: EP #1, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.784057] td310x: EP #1, type: bulk, dir: ->, packet: 512 bytes
kernel: [10118.784066] td310x: EP #2, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.784488] td310x: Interface #3 has 3 endpoints
kernel: [10118.784498] td310x: EP #1, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.784505] td310x: EP #1, type: bulk, dir: ->, packet: 512 bytes
kernel: [10118.784513] td310x: EP #2, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.784766] td310x: Interface #4 has 3 endpoints
kernel: [10118.784772] td310x: EP #1, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.784777] td310x: EP #1, type: bulk, dir: ->, packet: 512 bytes
kernel: [10118.784781] td310x: EP #2, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.785149] td310x: Interface #5 has 3 endpoints
kernel: [10118.785155] td310x: EP #1, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.785159] td310x: EP #1, type: bulk, dir: ->, packet: 512 bytes
kernel: [10118.785163] td310x: EP #2, type: bulk, dir: <-, packet: 512 bytes
kernel: [10118.786629] td310x: Successfully registered device
This card has 2 audio and 4 video capture channels. Based on CY7C68013A56LFXC and cx25843-24Z chips. Next step is to understand i2c/urb exchange, 0x44 is cx25843 i2c address:
08 44 03 08 03 03 <- 0x44 i2c write
09 02 01 44 08 03 <- 0x44 i2c read
If someone have any useful info of this board, plz let me know.
I2C disassembled subroutine
Playing with the same toy
checking "easycap" compatibility, looks like same chipset. or am i wrong?
Playing around with the same toy
Looking for compatibility with easycap linux driver. Looks like same chipset. or am i wrong?
Easycap looking similar to my device
Yes, look like this is twins