Re: terratec h5 rev. 3?
On 23 December 2012 00:42, Mauro Carvalho Chehab mche...@redhat.com wrote: Em Sat, 22 Dec 2012 22:25:24 +0100 Roland Scheidegger rscheidegger_li...@hispeed.ch escreveu: Am 21.12.2012 06:38, schrieb linux-media-ow...@vger.kernel.org: Hi, I've recently got a terratec h5 for dvb-c and thought it would be supported but it looks like it's a newer revision not recognized by em28xx. After using the new_id hack it gets recognized and using various htc cards (notably h5 or cinergy htc stick, cards 79 and 82 respectively) it seems to _nearly_ work but not quite (I was using h5 firmware for the older version). Tuning, channel scan works however tv (or dvb radio) does not, since it appears the error rate is going through the roof (with some imagination it is possible to see some parts of the picture sometimes and hear some audio pieces). femon tells something like this: snip Hmm actually it doesn't work any better at all with windows neither, so I guess it doesn't like my cable signal (I do have another mantis-based pci dvb-c card which works without issue). Maybe the tuner is just crappy. So I guess it wouldn't hurt to simply add the usb id of this card (0ccd:10b6) as another terratec h5 (this doesn't get you the IR but it's a start I guess). The dvb-t part though works without issue on windows, and I could not get that to work in linux (I've used kaffeine and dvb-fe-tool to force the dvbt delivery system if that's supposed to work). When scanning the right frequency it spew out some error messages though: DvbScanFilter::timerEvent: timeout while reading section; type = 0 pid = 0 kaffeine(7527) DvbScanFilter::timerEvent: timeout while reading section; type = 2 pid = 17 If DVB-T is also not working, then I suspect that the device is different than the previous revisions. There are two ways to connect the DRX-K with em28xx: serial or parallel. Maybe you need to touch that. The better would be to sniff the usb traffic using the tools at v4l-utils.git and see what's happening there. Roland, did you sniff the usb traffic and/or adjust the serial/ parallel setting yet? I happen to have a H5 rev 3 as well. Roland -- 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 -- Cheers, Mauro -- 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 -- 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
[PATCH] Add the usb id of the Trekstor DVB-T Stick Terres 2.0
It needs the e4000 tuner driver.
Signed-off-by: Philipp Dreimann phil...@dreimann.net
---
drivers/media/dvb-core/dvb-usb-ids.h|1 +
drivers/media/usb/dvb-usb-v2/rtl28xxu.c |2 ++
2 files changed, 3 insertions(+)
diff --git a/drivers/media/dvb-core/dvb-usb-ids.h
b/drivers/media/dvb-core/dvb-usb-ids.h
index 26c4481..fed6dcd 100644
--- a/drivers/media/dvb-core/dvb-usb-ids.h
+++ b/drivers/media/dvb-core/dvb-usb-ids.h
@@ -82,6 +82,7 @@
#define USB_PID_AFATECH_AF9035_10030x1003
#define USB_PID_AFATECH_AF9035_90350x9035
#define USB_PID_TREKSTOR_DVBT 0x901b
+#define USB_PID_TREKSTOR_TERRES_2_00xC803
#define USB_VID_ALINK_DTU 0xf170
#define USB_PID_ANSONIC_DVBT_USB 0x6000
#define USB_PID_ANYSEE 0x861f
diff --git a/drivers/media/usb/dvb-usb-v2/rtl28xxu.c
b/drivers/media/usb/dvb-usb-v2/rtl28xxu.c
index 88b5ea1..d0d23f2 100644
--- a/drivers/media/usb/dvb-usb-v2/rtl28xxu.c
+++ b/drivers/media/usb/dvb-usb-v2/rtl28xxu.c
@@ -1236,6 +1236,8 @@ static const struct usb_device_id rtl28xxu_id_table[] = {
rtl2832u_props, NOXON DAB/DAB+ USB dongle, NULL) },
{ DVB_USB_DEVICE(USB_VID_REALTEK, 0x2838,
rtl2832u_props, Realtek RTL2832U reference design, NULL) },
+ { DVB_USB_DEVICE(USB_VID_GTEK, USB_PID_TREKSTOR_TERRES_2_0,
+ rtl2832u_props, Trekstor DVB-T Stick Terres 2.0, NULL) },
{ }
};
MODULE_DEVICE_TABLE(usb, rtl28xxu_id_table);
--
1.7.9.5
--
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: uvcvideo issue with kernel 3.5-rc2 and 3
On 18 June 2012 12:41, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: This might be cause by a bug in the USB core or in the UVC driver. Would you be able to bisect the regression ? Are you aware of any tool to bisect such issues using kvm/virtualbox/..? I would like to bisect the issue but rebooting the system needs to be avoided. Or, alternatively, test the v3.4 uvcvideo driver on v3.5-rc3 ? Or the other way around, test the latest v4l tree on v3.4 (instructions regarding how to compile the v4l tree with a different kernel are available at http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L- DVB_Device_Drivers). I compiled the 3.4 module with 3.5-rc3. The error is still the same using usb2. I tried to connect the camera to an usb3 port and it worked as it should. -- The issue seems to be related to usb2 then. I'll inform the usb guys. Regards, Philipp Dreimann -- 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
uvcvideo issue with kernel 3.5-rc2 and 3
Hello, my external webcam from Logitech (I guess it's a c910) stopped working using kernel 3.5-rc3.( 3.4 worked fine.) uvcvideo: Found UVC 1.00 device unnamed (046d:0821) input: UVC Camera (046d:0821) as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.2/input/input14 usbcore: registered new interface driver uvcvideo USB Video Class driver (1.1.1) uvcvideo: Failed to query (GET_DEF) UVC control 2 on unit 2: -71 (exp. 2). uvcvideo: Failed to query (GET_DEF) UVC control 2 on unit 2: -71 (exp. 2). uvcvideo: Failed to query (GET_DEF) UVC control 3 on unit 2: -71 (exp. 2). uvcvideo: Failed to query (GET_DEF) UVC control 7 on unit 2: -71 (exp. 2). uvcvideo: Failed to query (GET_DEF) UVC control 11 on unit 2: -71 (exp. 1). uvcvideo: Failed to query (GET_DEF) UVC control 4 on unit 2: -71 (exp. 2). uvcvideo: Failed to query (GET_DEF) UVC control 5 on unit 2: -71 (exp. 1). uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -71 (exp. 1). uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 2: -71 (exp. 2). uvcvideo: Failed to query (GET_DEF) UVC control 1 on unit 2: -71 (exp. 2). uvcvideo: Failed to set UVC probe control : -71 (exp. 26). uvcvideo: Failed to set UVC probe control : -71 (exp. 26). uvcvideo: Failed to set UVC probe control : -71 (exp. 26). uvcvideo: Failed to set UVC probe control : -71 (exp. 26). (the last line is being repeated...) I used cheese to test the webcam. My other webcam is working fine: uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b217) input: Integrated Camera as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input13 Thanks, Philipp Dreimann -- 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
