Re: driver problem: cx231xx error -71 with Hauppauge USB live2 on Ubuntu 11.04, netbook edition

2011-07-26 Thread Doychin Dokov
I'm having the same problem, on Ubuntu Server 11.04 x64, kernel 2.6.38-10. I've also tried Debian with the same results. Here's the debug log from the Ubuntu installation: [416830.888124] cx231xx #0: cx231xx #0/0: registered device video3 [v4l2] [416830.888243] cx231xx #0: cx231xx #0/0:

Re: driver problem: cx231xx error -71 with Hauppauge USB live2 on Ubuntu 11.04, netbook edition

2011-07-26 Thread Doychin Dokov
На 26.7.2011 г. 15:17 ч., Devin Heitmueller написа: On Tue, Jul 26, 2011 at 7:53 AM, Doychin Dokovr...@net1.cc wrote: [416830.939483] cx231xx #0: can't change interface 3 alt no. to 0 (err=-71) This is with the stock kernel, no media_build tree installed (I'm currently compiling it).

Re: [PATCH] Fix regression introduced which broke the Hauppauge USBLive 2

2011-07-26 Thread Doychin Dokov
На 24.7.2011 г. 04:17 ч., Devin Heitmueller написа: The following patch addresses the regression introduced in the cx231xx driver which stopped the Hauppauge USBLive2 from working. Confirmed working by both myself and the user who reported the issue on the KernelLabs blog (Robert DeLuca). I

Re: [PATCH] Add support for PCTV452E.

2011-06-12 Thread Doychin Dokov
Debian's 2.6.32.5 and 2.6.38-bpo2 on a Debian Squeeze system. На 11.6.2011 г. 19:38 ч., Doychin Dokov написа: i've been using the patches in the latest media_tree for some hours - the S2-3650 CI seems to work. There's one thing that disturbs me, though - when it scans / locks on a frequency, another

Re: [PATCH] Add support for PCTV452E.

2011-06-12 Thread Doychin Dokov
On 2.6.32.5 with s2-liplianin tree this is not observed, i.e. everything works as expected - the S2-3650 does not cause the TBS device to stutter. На 12.6.2011 г. 23:27 ч., Doychin Dokov написа: The same thing happens when the devices are on different USB buses: Bus 002 Device 004: ID 0b48:300a

Re: [PATCH] Add support for PCTV452E.

2011-06-12 Thread Doychin Dokov
be the reason for that, or at least where I should focus at searching? На 13.6.2011 г. 00:38 ч., Doychin Dokov написа: On 2.6.32.5 with s2-liplianin tree this is not observed, i.e. everything works as expected - the S2-3650 does not cause the TBS device to stutter. На 12.6.2011 г. 23:27 ч

Re: [PATCH] Add support for PCTV452E.

2011-06-11 Thread Doychin Dokov
i've been using the patches in the latest media_tree for some hours - the S2-3650 CI seems to work. There's one thing that disturbs me, though - when it scans / locks on a frequency, another device on the same PC, using the same stb6100, gets stuck for a moment. Any ideas what might be the

Re: [PATCH] Add support for PCTV452E.

2011-06-10 Thread Doychin Dokov
I think you've missed this line at the end of ttpci-eeprom.c : EXPORT_SYMBOL(ttpci_eeprom_decode_mac); -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: TT S2-3650CI problems with high-SR DVB-S2 transponders

2011-05-11 Thread Doychin Dokov
I've just tried with the 2.6.38 kernel from the backports, and the lock fix only - result is the same, unusable output from device - too many discontinuities. Noone using the S2-3600 / 3650 on high-rate transponders? Any other Linux-supported USB DVB-S2 device with CI and high SR support?

TT S2-3650CI problems with high-SR DVB-S2 transponders

2011-05-10 Thread Doychin Dokov
I've been trying to get TechnoTrend S2-3650CI running with DVB-S2 transponder with SR of 3. I'm using stock Debian 6 kernel 2.6.32-5-amd64 and s2-liplianin tree. Initially, the device couldn't lock the 30K transponders at all. After applying patch [1], it locks without any problems, and

Re: TT S2-3650CI problems with high-SR DVB-S2 transponders

2011-05-10 Thread Doychin Dokov
На 11.5.2011 г. 02:24 ч., Doychin Dokov написа: I've been trying to get TechnoTrend S2-3650CI running with DVB-S2 transponder with SR of 3. I'm using stock Debian 6 kernel 2.6.32-5-amd64 and s2-liplianin tree. Initially, the device couldn't lock the 30K transponders at all. After applying