Message ID | 4FA232CE.8010404@gmail.com (mailing list archive) |
---|---|
State | Superseded, archived |
Headers |
Received: from mail.tu-berlin.de ([130.149.7.33]) by www.linuxtv.org with esmtp (Exim 4.72) (envelope-from <linux-media-owner@vger.kernel.org>) id 1SPqPZ-0000TL-RY for patchwork@linuxtv.org; Thu, 03 May 2012 09:25:13 +0200 X-tubIT-Incoming-IP: 209.132.180.67 Received: from vger.kernel.org ([209.132.180.67]) by mail.tu-berlin.de (exim-4.75/mailfrontend-4) with esmtp for <patchwork@linuxtv.org> id 1SPqPY-0000Ac-AU; Thu, 03 May 2012 09:25:13 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755522Ab2ECHZJ (ORCPT <rfc822;patchwork@linuxtv.org>); Thu, 3 May 2012 03:25:09 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:60208 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755324Ab2ECHZH (ORCPT <rfc822; linux-media@vger.kernel.org>); Thu, 3 May 2012 03:25:07 -0400 Received: by bkcji2 with SMTP id ji2so1075592bkc.19 for <linux-media@vger.kernel.org>; Thu, 03 May 2012 00:25:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=GJLhzq1F59IGnp7kivFuLbM0FrLtLx89E58uygWe27Q=; b=fcY6ozJjNcRxVVvlS0VS5Ca9lU9iNFKNDU+mVFKmO8TNMWR1vc2slDrjxRmYpWsW8g FHXJvWeh2zMZ00rp2wR5j0TMVHntD1MTr0rmGImgBJAX+WEFaaoS6m56HvwK6BTNwG4L f4o6zH9OrENbqsTT0UqNP87vcUtcF5ZxRxFmotx+GFMelFjbEb1K5CnsQs7A5zkH/j+U fu5gF9ih43Ox93F2GdEkbns16UjwcNRl7uhjCsVn0nUVti4H4H79xaImwLfOVpHf+0W4 YL116Xk3RbmEsz+S7cqenC9CAF7DczZciHY8VJO3KnoyIZfgp9TdKP8iSLOL7WnX05OW oWwA== Received: by 10.204.152.73 with SMTP id f9mr394667bkw.3.1336029906329; Thu, 03 May 2012 00:25:06 -0700 (PDT) Received: from nuna.dma (iskon6400.duo.carnet.hr. [31.147.121.0]) by mx.google.com with ESMTPS id zx16sm8176618bkb.13.2012.05.03.00.25.03 (version=SSLv3 cipher=OTHER); Thu, 03 May 2012 00:25:05 -0700 (PDT) Message-ID: <4FA232CE.8010404@gmail.com> Date: Thu, 03 May 2012 09:25:02 +0200 From: poma <pomidorabelisima@gmail.com> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120424 Thunderbird/12.0 MIME-Version: 1.0 To: linux-media@vger.kernel.org CC: gennarone@gmail.com, Zdenek Styblik <stybla@turnovfree.net>, fermio.kll@hotmail.com, julianjm@gmail.com, thomas.mair86@googlemail.com, Antti Palosaari <crope@iki.fi> Subject: Re: [PATCH v2] add support for DeLOCK-USB-2.0-DVB-T-Receiver-61744 References: <4F9E5D91.30503@gmail.com> <1335800374-22012-2-git-send-email-thomas.mair86@googlemail.com> <4F9F8752.40609@gmail.com> In-Reply-To: <4F9F8752.40609@gmail.com> Content-Type: multipart/mixed; boundary="------------030400080705000002000502" Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: <linux-media.vger.kernel.org> X-Mailing-List: linux-media@vger.kernel.org X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.3.71223 X-PMX-Spam: Gauge=IIIIIIIII, Probability=9%, Report=' FORGED_FROM_GMAIL 0.1, MULTIPLE_RCPTS 0.1, FROM_NAME_ONE_WORD 0.05, HTML_00_01 0.05, HTML_00_10 0.05, KNOWN_FREEWEB_URI 0.05, MIME_TEXT_ONLY_MP_MIXED 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_10000_PLUS 0, TXT_ATTACHED 0, URI_ENDS_IN_HTML 0, __ANY_URI 0, __BAT_BOUNDARY 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_URI_IN_BODY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_MIXED 0, __FRAUD_BODY_WEBMAIL 0, __FRAUD_WEBMAIL 0, __FRAUD_WEBMAIL_FROM 0, __FROM_GMAIL 0, __HAS_MSGID 0, __HAS_X_MAILING_LIST 0, __HIGHBITS 0, __INT_PROD_TV 0, __KNOWN_FREEWEB_URI1 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __MULTIPLE_RCPTS_CC_X2 0, __PHISH_SPEAR_STRUCTURE_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_NS , __USER_AGENT 0' |
Commit Message
poma
May 3, 2012, 7:25 a.m. UTC
[?…] Hi there, These two patches - 'dvb-usb-ids-v2-rtl2832-fc0012.patch' and 'rtl28xxu-v2-rtl2832-fc0012.patch' adds nine devices based on FC0012 tuner, altogether eleven. Gianluca, please inform forum fellows to test&reply. Zdenek, fermio - there is a note on http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:start at "Other DVB-T Sticks" regarding 'af4d:a803' device. Is it based on RTL2832 with FC0012 tuner? Julian, Thomas, Antii cheers mates! ;) poma ps. modinfo dvb_usb_rtl28xxu filename: /lib/modules/3.3.2-6.fc16.x86_64/kernel/drivers/media/dvb/dvb-usb/dvb-usb-rtl28xxu.ko license: GPL author: Thomas Mair <thomas.mair86@googlemail.com> author: Antti Palosaari <crope@iki.fi> description: Realtek RTL28xxU DVB USB driver alias: usb:v1F4DpD803d*dc*dsc*dp*ic*isc*ip* alias: usb:v1F4DpC803d*dc*dsc*dp*ic*isc*ip* alias: usb:v1B80pD399d*dc*dsc*dp*ic*isc*ip* alias: usb:v1B80pD395d*dc*dsc*dp*ic*isc*ip* alias: usb:v1B80pD394d*dc*dsc*dp*ic*isc*ip* alias: usb:v1B80pD393d*dc*dsc*dp*ic*isc*ip* alias: usb:v1B80pD39Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v0458p707Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp2838d*dc*dsc*dp*ic*isc*ip* alias: usb:v1F4DpB803d*dc*dsc*dp*ic*isc*ip* alias: usb:v0CCDp00A9d*dc*dsc*dp*ic*isc*ip* alias: usb:v14AAp0161d*dc*dsc*dp*ic*isc*ip* alias: usb:v14AAp0160d*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp2831d*dc*dsc*dp*ic*isc*ip* depends: dvb-usb,rtl2830,rc-core vermagic: 3.3.2-6.fc16.x86_64 SMP mod_unload parm: debug:set debugging level (int) parm: adapter_nr:DVB adapter numbers (array of short) 0bda:2838 *USB_VID_REALTEK 0x0bda USB_PID_EZCAP_EZTV646 0x2838 EzCAP EzTV646 http://www.szforwardvideo.com/product/Pro_18_7.html http://ubuntuforums.org/showthread.php?t=1532934 RTL2832U_0BDA_2838 0ccd:00a9 *USB_VID_TERRATEC 0x0ccd *USB_PID_TERRATEC_CINERGY_T_STICK_BLACK 0x00a9 TERRATEC Cinergy T Stick Black - "Rev.1" http://linux.terratec.de/tv_en.html http://www.terratec.net/en/products/Cinergy_T_Stick_Black_107611.html *RTL2832U_0CCD_00A9 0458:707f *USB_VID_KYE 0x0458 USB_PID_GENIUS_TVGO_DVB_T03_2 0x707f Genius TVGo DVB-T03 - "Ver.B" http://www.linuxtv.org/wiki/index.php/Genius_TVGo_DVB-T03 http://www.abclinuxu.cz/hardware/pridavne-karty/televizni-karty/dvb-t/usb/genius-tvgo-dvb-t03-hw-z-2011 RTL2832U_0458_707F 1b80:d39d *USB_VID_KWORLD_2 0x1b80 USB_PID_SVEON_STV20_2 0xd39d Sveon STV20 http://www.sveon.com/fichaSTV20.html https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0/issues/4 RTL2832U_1B80_D39D 1b80:d393 *USB_VID_KWORLD_2 0x1b80 USB_PID_KWORLD_D393 0xd393 Ardata MyVision DVB-T TV http://www.ardata.pl/tuner-telewizyjny-ardata-myvision-dvb-t-tv Gigabyte U7300 USB DVB-T http://www.gigabyte.com/products/product-page.aspx?pid=3493#sp http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:gigabyte-u7300-usb-dvb-t-tuner NILOX DVB-T Stick N15 http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:nilox-dvb-t_stick_n15 Twintech UT-30 USB2.0 DVB-T Stick with FM Radio http://www.twintech3d.com/products_features.asp?num=300 RTL2832U_1B80_D393 1b80:d394 *USB_VID_KWORLD_2 0x1b80 USB_PID_HU394 0xd394 DIKOM USB-DVBT HD http://twitter.com/#!/spin877/status/188265508401979392 http://xgazza.altervista.org/Linux/DVB/dikom_dvbt.JPG RTL2832U_1B80_D394 1b80:d395 *USB_VID_KWORLD_2 0x1b80 USB_PID_KWORLD_D395 0xd395 MaxMedia HU394-T USB DVB-T Multi (FM, DAB, DAB+) http://www.maxmediatek.com/pd-page/DVB-T_USB.htm PEAK Hardware 102569AGPK DVB-T Digital TV USB Stick http://ubuntuforums.org/showthread.php?t=1678094 RTL2832U_1B80_D395 1b80:d399 DVB-T TV Stick D399 *USB_VID_KWORLD_2 0x1b80 USB_PID_KWORLD_D399 0xd399 http://ubuntuforums.org/showthread.php?t=1678094&page=2 RTL2832U_1B80_D399 1f4d:b803 *USB_VID_GTEK 0x1f4d *USB_PID_GTEK 0xb803 DeLOCK USB 2.0 DVB-T Receiver 61744 http://www.delock.com/produkte/gruppen/Multimedia/Delock_USB_20_DVB-T_Receiver_61744.html G-Tek T803 MyGica T803 DVB-T USB TV Stick http://www.mygica.com/product.asp?id=149 *RTL2832U_1F4D_B803 1f4d:c803 *USB_VID_GTEK 0x1f4d USB_PID_NOT_ONLY_LV5TDELUXE 0xc803 LifeView/Not Only TV DVB-T USB DELUXE LV5TDELUXE http://notonlytv.net/p_lv5tdeluxe.html RTL2832U_1F4D_C803 1f4d:d803 *USB_VID_GTEK 0x1f4d USB_PID_PROLECTRIX_DV107669 0xd803 PROlectrix USB DVB-T & DAB Dongle DV107669 http://www.reddit.com/user/GrahamM242 RTL2832U_1F4D_D803 https://github.com/tmair/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0/blob/master/README http://www.reddit.com/r/RTLSDR/comments/s6ddo/rtlsdr_compatibility_list_v2_work_in_progress/
Comments
Hi poma, I have a 0BDA:2838 (Easycap EZTV646) and a 0BDA:2832 (no name 20x20mm mini DVB-T stick) and both are based on the E4000 tuner, which is not supported in the kernel at the moment. I have no idea if there are sticks with the same USB PID and the fc0012 tuner. Regards, Gianluca Il 03/05/2012 09:25, poma ha scritto: > > [?…] > > Hi there, > > These two patches - 'dvb-usb-ids-v2-rtl2832-fc0012.patch' and > 'rtl28xxu-v2-rtl2832-fc0012.patch' adds nine devices based on FC0012 > tuner, altogether eleven. > Gianluca, please inform forum fellows to test&reply. > Zdenek, fermio - there is a note on > http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:start at > "Other DVB-T Sticks" regarding 'af4d:a803' device. > Is it based on RTL2832 with FC0012 tuner? > > Julian, Thomas, Antii > cheers mates! > ;) > poma > > ps. > modinfo dvb_usb_rtl28xxu > filename: > /lib/modules/3.3.2-6.fc16.x86_64/kernel/drivers/media/dvb/dvb-usb/dvb-usb-rtl28xxu.ko > license: GPL > author: Thomas Mair <thomas.mair86@googlemail.com> > author: Antti Palosaari <crope@iki.fi> > description: Realtek RTL28xxU DVB USB driver > alias: usb:v1F4DpD803d*dc*dsc*dp*ic*isc*ip* > alias: usb:v1F4DpC803d*dc*dsc*dp*ic*isc*ip* > alias: usb:v1B80pD399d*dc*dsc*dp*ic*isc*ip* > alias: usb:v1B80pD395d*dc*dsc*dp*ic*isc*ip* > alias: usb:v1B80pD394d*dc*dsc*dp*ic*isc*ip* > alias: usb:v1B80pD393d*dc*dsc*dp*ic*isc*ip* > alias: usb:v1B80pD39Dd*dc*dsc*dp*ic*isc*ip* > alias: usb:v0458p707Fd*dc*dsc*dp*ic*isc*ip* > alias: usb:v0BDAp2838d*dc*dsc*dp*ic*isc*ip* > alias: usb:v1F4DpB803d*dc*dsc*dp*ic*isc*ip* > alias: usb:v0CCDp00A9d*dc*dsc*dp*ic*isc*ip* > alias: usb:v14AAp0161d*dc*dsc*dp*ic*isc*ip* > alias: usb:v14AAp0160d*dc*dsc*dp*ic*isc*ip* > alias: usb:v0BDAp2831d*dc*dsc*dp*ic*isc*ip* > depends: dvb-usb,rtl2830,rc-core > vermagic: 3.3.2-6.fc16.x86_64 SMP mod_unload > parm: debug:set debugging level (int) > parm: adapter_nr:DVB adapter numbers (array of short) > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello poma, I'm sorry, but that's all info I've been "given". :-\ Best regards, Z. On 05/03/12 09:25, poma wrote: > > [?…] > > Hi there, > > These two patches - 'dvb-usb-ids-v2-rtl2832-fc0012.patch' and > 'rtl28xxu-v2-rtl2832-fc0012.patch' adds nine devices based on > FC0012 tuner, altogether eleven. Gianluca, please inform forum > fellows to test&reply. Zdenek, fermio - there is a note on > http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:start at > "Other DVB-T Sticks" regarding 'af4d:a803' device. Is it based on > RTL2832 with FC0012 tuner? > > Julian, Thomas, Antii cheers mates! ;) poma > > ps. modinfo dvb_usb_rtl28xxu filename: > /lib/modules/3.3.2-6.fc16.x86_64/kernel/drivers/media/dvb/dvb-usb/dvb-usb-rtl28xxu.ko > > license: GPL > author: Thomas Mair <thomas.mair86@googlemail.com> author: > Antti Palosaari <crope@iki.fi> description: Realtek RTL28xxU DVB > USB driver alias: usb:v1F4DpD803d*dc*dsc*dp*ic*isc*ip* > alias: usb:v1F4DpC803d*dc*dsc*dp*ic*isc*ip* alias: > usb:v1B80pD399d*dc*dsc*dp*ic*isc*ip* alias: > usb:v1B80pD395d*dc*dsc*dp*ic*isc*ip* alias: > usb:v1B80pD394d*dc*dsc*dp*ic*isc*ip* alias: > usb:v1B80pD393d*dc*dsc*dp*ic*isc*ip* alias: > usb:v1B80pD39Dd*dc*dsc*dp*ic*isc*ip* alias: > usb:v0458p707Fd*dc*dsc*dp*ic*isc*ip* alias: > usb:v0BDAp2838d*dc*dsc*dp*ic*isc*ip* alias: > usb:v1F4DpB803d*dc*dsc*dp*ic*isc*ip* alias: > usb:v0CCDp00A9d*dc*dsc*dp*ic*isc*ip* alias: > usb:v14AAp0161d*dc*dsc*dp*ic*isc*ip* alias: > usb:v14AAp0160d*dc*dsc*dp*ic*isc*ip* alias: > usb:v0BDAp2831d*dc*dsc*dp*ic*isc*ip* depends: > dvb-usb,rtl2830,rc-core vermagic: 3.3.2-6.fc16.x86_64 SMP > mod_unload parm: debug:set debugging level (int) parm: > adapter_nr:DVB adapter numbers (array of short) >
On 05/03/2012 11:03 AM, Gianluca Gennari wrote: > Hi poma, > I have a 0BDA:2838 (Easycap EZTV646) and a 0BDA:2832 (no name 20x20mm > mini DVB-T stick) and both are based on the E4000 tuner, which is not > supported in the kernel at the moment. > I have no idea if there are sticks with the same USB PID and the fc0012 > tuner. OK, second one - no name device is "Realtek RTL2832U reference design"**. First one: Once upon a time there was a "EasyCAP"… "After while crocodile!" …and "EzCAP" was born. http://szforwardvideo.en.alibaba.com/aboutus.html Obviously Easycap EZTV646 != EzCAP EzTV646 http://www.reddit.com/r/RTLSDR/comments/s6ddo/rtlsdr_compatibility_list_v2_work_in_progress/ ezcap EzTV646 0BDA:2838 RTL2832U/FC0012 Some revisions may have the E4000* http://i.imgur.com/mFD1X.jpg (Generic) 0BDa:2838 RTL2832U/E4000* … And, in addition: http://sdr.osmocom.org/trac/wiki/rtl-sdr 0x0bda 0x2832 all of them Generic RTL2832U (e.g. hama nano)** 0x0bda 0x2838 E4000 ezcap USB 2.0 DVB-T/DAB/FM dongle … Maybe? https://sites.google.com/site/myrtlsdr/ "EzCap EZTV646 has got RTL2832U/FC0012. However rtl-sdr must be tweaked to force FC0012 tuner because it has the same PID as EZTV668 (PID: 0x2838) so running it whithout a tweak will select Elonics E4000 tuner. Works, not so good at filtering." … Conclusion: At least two devices share same vid/pid with different tuners - fc0012 vs e4000. How to resolve this from a drivers perspective in a proper way? Beside, there is GPL'ed 'e4k' tuner source code aka 'e4000 improved'*** (Elonics E4000) by Harald Welte http://cgit.osmocom.org/cgit/osmo-sdr/tree/firmware/src/tuner_e4k.c http://sdr.osmocom.org/trac/ http://sdr.osmocom.org/trac/wiki/rtl-sdr http://wiki.spench.net/wiki/RTL2832U*** regards, poma -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 05/03/2012 08:17 PM, Zdenek Styblik wrote: > Hello poma, > > I'm sorry, but that's all info I've been "given". :-\ It is as it is. ;) regards, poma > On 05/03/12 09:25, poma wrote: >> >> [?…] >> >> Hi there, >> >> These two patches - 'dvb-usb-ids-v2-rtl2832-fc0012.patch' and >> 'rtl28xxu-v2-rtl2832-fc0012.patch' adds nine devices based on >> FC0012 tuner, altogether eleven. Gianluca, please inform forum >> fellows to test&reply. Zdenek, fermio - there is a note on >> http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:start at >> "Other DVB-T Sticks" regarding 'af4d:a803' device. Is it based on >> RTL2832 with FC0012 tuner? >> >> Julian, Thomas, Antii cheers mates! ;) poma >> >> ps. modinfo dvb_usb_rtl28xxu filename: >> /lib/modules/3.3.2-6.fc16.x86_64/kernel/drivers/media/dvb/dvb-usb/dvb-usb-rtl28xxu.ko >> >> > license: GPL >> author: Thomas Mair <thomas.mair86@googlemail.com> author: >> Antti Palosaari <crope@iki.fi> description: Realtek RTL28xxU DVB >> USB driver alias: usb:v1F4DpD803d*dc*dsc*dp*ic*isc*ip* >> alias: usb:v1F4DpC803d*dc*dsc*dp*ic*isc*ip* alias: >> usb:v1B80pD399d*dc*dsc*dp*ic*isc*ip* alias: >> usb:v1B80pD395d*dc*dsc*dp*ic*isc*ip* alias: >> usb:v1B80pD394d*dc*dsc*dp*ic*isc*ip* alias: >> usb:v1B80pD393d*dc*dsc*dp*ic*isc*ip* alias: >> usb:v1B80pD39Dd*dc*dsc*dp*ic*isc*ip* alias: >> usb:v0458p707Fd*dc*dsc*dp*ic*isc*ip* alias: >> usb:v0BDAp2838d*dc*dsc*dp*ic*isc*ip* alias: >> usb:v1F4DpB803d*dc*dsc*dp*ic*isc*ip* alias: >> usb:v0CCDp00A9d*dc*dsc*dp*ic*isc*ip* alias: >> usb:v14AAp0161d*dc*dsc*dp*ic*isc*ip* alias: >> usb:v14AAp0160d*dc*dsc*dp*ic*isc*ip* alias: >> usb:v0BDAp2831d*dc*dsc*dp*ic*isc*ip* depends: >> dvb-usb,rtl2830,rc-core vermagic: 3.3.2-6.fc16.x86_64 SMP >> mod_unload parm: debug:set debugging level (int) parm: >> adapter_nr:DVB adapter numbers (array of short) >> > > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi poma, thanks for the very interesting links. Il 04/05/2012 03:27, poma ha scritto: > On 05/03/2012 11:03 AM, Gianluca Gennari wrote: >> Hi poma, >> I have a 0BDA:2838 (Easycap EZTV646) and a 0BDA:2832 (no name 20x20mm >> mini DVB-T stick) and both are based on the E4000 tuner, which is not >> supported in the kernel at the moment. >> I have no idea if there are sticks with the same USB PID and the fc0012 >> tuner. > > OK, second one - no name device is "Realtek RTL2832U reference design"**. > > First one: > Once upon a time there was a "EasyCAP"? > "After while crocodile!" > ?and "EzCAP" was born. > http://szforwardvideo.en.alibaba.com/aboutus.html > Obviously Easycap EZTV646 != EzCAP EzTV646 > http://www.reddit.com/r/RTLSDR/comments/s6ddo/rtlsdr_compatibility_list_v2_work_in_progress/ > ezcap EzTV646 0BDA:2838 RTL2832U/FC0012 Some revisions may have the E4000* > http://i.imgur.com/mFD1X.jpg > (Generic) 0BDa:2838 RTL2832U/E4000* > ? > And, in addition: > http://sdr.osmocom.org/trac/wiki/rtl-sdr > 0x0bda 0x2832 all of them Generic RTL2832U (e.g. hama nano)** > 0x0bda 0x2838 E4000 ezcap USB 2.0 DVB-T/DAB/FM dongle > ? > Maybe? > https://sites.google.com/site/myrtlsdr/ That's it. Opening the device enclosure, I can read this on the PCB: "EzTV668 1.0" and it looks identical to the picture posted there. > "EzCap EZTV646 has got RTL2832U/FC0012. However rtl-sdr must be tweaked > to force FC0012 tuner because it has the same PID as EZTV668 (PID: > 0x2838) so running it whithout a tweak will select Elonics E4000 tuner. > Works, not so good at filtering." > ? > Conclusion: > At least two devices share same vid/pid with different tuners - fc0012 > vs e4000. > How to resolve this from a drivers perspective in a proper way? This is not a big problem: the rtl2832 driver should read the tuner type from an internal register and load the proper module (or exit with an error message if the tuner is unsupported). > Beside, > there is GPL'ed 'e4k' tuner source code aka 'e4000 improved'*** (Elonics > E4000) > by Harald Welte > http://cgit.osmocom.org/cgit/osmo-sdr/tree/firmware/src/tuner_e4k.c > http://sdr.osmocom.org/trac/ > http://sdr.osmocom.org/trac/wiki/rtl-sdr > http://wiki.spench.net/wiki/RTL2832U*** Very nice. So we should ask Harald Welte if he is willing to have his driver merged in the kernel. > regards, > poma > Regards, Gianluca -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Il 04/05/2012 03:27, poma ha scritto: > On 05/03/2012 11:03 AM, Gianluca Gennari wrote: >> Hi poma, >> I have a 0BDA:2838 (Easycap EZTV646) and a 0BDA:2832 (no name 20x20mm >> mini DVB-T stick) and both are based on the E4000 tuner, which is not >> supported in the kernel at the moment. >> I have no idea if there are sticks with the same USB PID and the fc0012 >> tuner. > > OK, second one - no name device is "Realtek RTL2832U reference design"**. Just for reference, the "no name device" I bought on ebay is exactly this one: http://i01.i.aliimg.com/photo/v0/513925059/Mini_notebook_USB_DVB_T_Stick_receiver.jpg Tuner: E4000 USB PID: 0BDA:2832 It is listed as "Unikoo UK001T (P160)" on the RTL SDR compatibility list: http://www.reddit.com/r/RTLSDR/comments/s6ddo/rtlsdr_compatibility_list_v2_work_in_progress/ Best regards, Gianluca > > First one: > Once upon a time there was a "EasyCAP"? > "After while crocodile!" > ?and "EzCAP" was born. > http://szforwardvideo.en.alibaba.com/aboutus.html > Obviously Easycap EZTV646 != EzCAP EzTV646 > http://www.reddit.com/r/RTLSDR/comments/s6ddo/rtlsdr_compatibility_list_v2_work_in_progress/ > ezcap EzTV646 0BDA:2838 RTL2832U/FC0012 Some revisions may have the E4000* > http://i.imgur.com/mFD1X.jpg > (Generic) 0BDa:2838 RTL2832U/E4000* > ? > And, in addition: > http://sdr.osmocom.org/trac/wiki/rtl-sdr > 0x0bda 0x2832 all of them Generic RTL2832U (e.g. hama nano)** > 0x0bda 0x2838 E4000 ezcap USB 2.0 DVB-T/DAB/FM dongle > ? > Maybe? > https://sites.google.com/site/myrtlsdr/ > "EzCap EZTV646 has got RTL2832U/FC0012. However rtl-sdr must be tweaked > to force FC0012 tuner because it has the same PID as EZTV668 (PID: > 0x2838) so running it whithout a tweak will select Elonics E4000 tuner. > Works, not so good at filtering." > ? > Conclusion: > At least two devices share same vid/pid with different tuners - fc0012 > vs e4000. > How to resolve this from a drivers perspective in a proper way? > > Beside, > there is GPL'ed 'e4k' tuner source code aka 'e4000 improved'*** (Elonics > E4000) > by Harald Welte > http://cgit.osmocom.org/cgit/osmo-sdr/tree/firmware/src/tuner_e4k.c > http://sdr.osmocom.org/trac/ > http://sdr.osmocom.org/trac/wiki/rtl-sdr > http://wiki.spench.net/wiki/RTL2832U*** > > regards, > poma > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 05/04/2012 08:50 AM, Thomas Mair wrote: > Am 04.05.2012 03:27 schrieb "poma" <pomidorabelisima@gmail.com>: >> >> On 05/03/2012 11:03 AM, Gianluca Gennari wrote: >>> Hi poma, >>> I have a 0BDA:2838 (Easycap EZTV646) and a 0BDA:2832 (no name 20x20mm >>> mini DVB-T stick) and both are based on the E4000 tuner, which is not >>> supported in the kernel at the moment. >>> I have no idea if there are sticks with the same USB PID and the fc0012 >>> tuner. >> >> OK, second one - no name device is "Realtek RTL2832U reference design"**. >> >> First one: >> Once upon a time there was a "EasyCAP"… >> "After while crocodile!" >> …and "EzCAP" was born. >> http://szforwardvideo.en.alibaba.com/aboutus.html >> Obviously Easycap EZTV646 != EzCAP EzTV646 >> > http://www.reddit.com/r/RTLSDR/comments/s6ddo/rtlsdr_compatibility_list_v2_work_in_progress/ >> ezcap EzTV646 0BDA:2838 RTL2832U/FC0012 Some revisions > may have the E4000* >> http://i.imgur.com/mFD1X.jpg >> (Generic) 0BDa:2838 RTL2832U/E4000* >> … >> And, in addition: >> http://sdr.osmocom.org/trac/wiki/rtl-sdr >> 0x0bda 0x2832 all of them Generic RTL2832U (e.g. hama nano)** >> 0x0bda 0x2838 E4000 ezcap USB 2.0 DVB-T/DAB/FM dongle >> … >> Maybe? >> https://sites.google.com/site/myrtlsdr/ >> "EzCap EZTV646 has got RTL2832U/FC0012. However rtl-sdr must be tweaked >> to force FC0012 tuner because it has the same PID as EZTV668 (PID: >> 0x2838) so running it whithout a tweak will select Elonics E4000 tuner. >> Works, not so good at filtering." >> … >> Conclusion: >> At least two devices share same vid/pid with different tuners - fc0012 >> vs e4000. >> How to resolve this from a drivers perspective in a proper way? > The handling of the different tuners of devices with the same vid/pid > should not be a problem, because rtl28xxu driver probes for the tuner when > the device is initialized. > Thanks for clarifying! rtl28xxu.c: … * Probe used tuner. We need to know used tuner before demod attach * since there is some demod params needed to set according to tuner. … /* check FC0012 ID register; reg=00 val=a1 */ … >> Beside, >> there is GPL'ed 'e4k' tuner source code aka 'e4000 improved'*** (Elonics >> E4000) >> by Harald Welte >> http://cgit.osmocom.org/cgit/osmo-sdr/tree/firmware/src/tuner_e4k.c >> http://sdr.osmocom.org/trac/ >> http://sdr.osmocom.org/trac/wiki/rtl-sdr >> http://wiki.spench.net/wiki/RTL2832U*** > So what is missing is the e4000 tuner driver. > True. > Btw i do have a list of devices that include the Rtl2832 demod. I will send > that list on the weekend. > Groovy! > Regards > Thomas > regards, poma -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 05/04/2012 03:49 PM, Gianluca Gennari wrote: > Hi poma, > thanks for the very interesting links. > ;) > Il 04/05/2012 03:27, poma ha scritto: >> On 05/03/2012 11:03 AM, Gianluca Gennari wrote: >>> Hi poma, >>> I have a 0BDA:2838 (Easycap EZTV646) and a 0BDA:2832 (no name 20x20mm >>> mini DVB-T stick) and both are based on the E4000 tuner, which is not >>> supported in the kernel at the moment. >>> I have no idea if there are sticks with the same USB PID and the fc0012 >>> tuner. >> >> OK, second one - no name device is "Realtek RTL2832U reference design"**. >> >> First one: >> Once upon a time there was a "EasyCAP"? >> "After while crocodile!" >> ?and "EzCAP" was born. >> http://szforwardvideo.en.alibaba.com/aboutus.html >> Obviously Easycap EZTV646 != EzCAP EzTV646 >> http://www.reddit.com/r/RTLSDR/comments/s6ddo/rtlsdr_compatibility_list_v2_work_in_progress/ >> ezcap EzTV646 0BDA:2838 RTL2832U/FC0012 Some revisions may have the E4000* >> http://i.imgur.com/mFD1X.jpg >> (Generic) 0BDa:2838 RTL2832U/E4000* >> ? >> And, in addition: >> http://sdr.osmocom.org/trac/wiki/rtl-sdr >> 0x0bda 0x2832 all of them Generic RTL2832U (e.g. hama nano)** >> 0x0bda 0x2838 E4000 ezcap USB 2.0 DVB-T/DAB/FM dongle >> ? >> Maybe? >> https://sites.google.com/site/myrtlsdr/ > > That's it. Opening the device enclosure, I can read this on the PCB: > "EzTV668 1.0" > and it looks identical to the picture posted there. > Groovy! >> "EzCap EZTV646 has got RTL2832U/FC0012. However rtl-sdr must be tweaked >> to force FC0012 tuner because it has the same PID as EZTV668 (PID: >> 0x2838) so running it whithout a tweak will select Elonics E4000 tuner. >> Works, not so good at filtering." >> ? >> Conclusion: >> At least two devices share same vid/pid with different tuners - fc0012 >> vs e4000. >> How to resolve this from a drivers perspective in a proper way? > > This is not a big problem: the rtl2832 driver should read the tuner type > from an internal register and load the proper module (or exit with an > error message if the tuner is unsupported). > Ack, thanks! >> Beside, >> there is GPL'ed 'e4k' tuner source code aka 'e4000 improved'*** (Elonics >> E4000) >> by Harald Welte >> http://cgit.osmocom.org/cgit/osmo-sdr/tree/firmware/src/tuner_e4k.c >> http://sdr.osmocom.org/trac/ >> http://sdr.osmocom.org/trac/wiki/rtl-sdr >> http://wiki.spench.net/wiki/RTL2832U*** > > Very nice. So we should ask Harald Welte if he is willing to have his > driver merged in the kernel. > Undoubtedly! Please ping Thomas and Antti, accordingly. >> regards, >> poma >> > > Regards, > Gianluca regards, poma -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
I am currently finishing up the work at the demod driver and will probably send a new version to the list tomorrow. As I don't own a device with a different tuner than the fc0012 I will include an error message about the unsupported tuner and print its type. So It is easier to get the information about the tuners. Right now I am writing the signal_strength callback and stumbled upon the following problem: The signal strength is read from the fc0012 tuner (only for fc0012). How should the driver implement this situation. Is there a callback I could implement within the tuner or should I just read the tuner registers from the demodulator? Regards Thomas 2012/5/5 poma <pomidorabelisima@gmail.com>: > On 05/04/2012 03:49 PM, Gianluca Gennari wrote: >> Hi poma, >> thanks for the very interesting links. >> > ;) > >> Il 04/05/2012 03:27, poma ha scritto: >>> On 05/03/2012 11:03 AM, Gianluca Gennari wrote: >>>> Hi poma, >>>> I have a 0BDA:2838 (Easycap EZTV646) and a 0BDA:2832 (no name 20x20mm >>>> mini DVB-T stick) and both are based on the E4000 tuner, which is not >>>> supported in the kernel at the moment. >>>> I have no idea if there are sticks with the same USB PID and the fc0012 >>>> tuner. >>> >>> OK, second one - no name device is "Realtek RTL2832U reference design"**. >>> >>> First one: >>> Once upon a time there was a "EasyCAP"? >>> "After while crocodile!" >>> ?and "EzCAP" was born. >>> http://szforwardvideo.en.alibaba.com/aboutus.html >>> Obviously Easycap EZTV646 != EzCAP EzTV646 >>> http://www.reddit.com/r/RTLSDR/comments/s6ddo/rtlsdr_compatibility_list_v2_work_in_progress/ >>> ezcap EzTV646 0BDA:2838 RTL2832U/FC0012 Some revisions may have the E4000* >>> http://i.imgur.com/mFD1X.jpg >>> (Generic) 0BDa:2838 RTL2832U/E4000* >>> ? >>> And, in addition: >>> http://sdr.osmocom.org/trac/wiki/rtl-sdr >>> 0x0bda 0x2832 all of them Generic RTL2832U (e.g. hama nano)** >>> 0x0bda 0x2838 E4000 ezcap USB 2.0 DVB-T/DAB/FM dongle >>> ? >>> Maybe? >>> https://sites.google.com/site/myrtlsdr/ >> >> That's it. Opening the device enclosure, I can read this on the PCB: >> "EzTV668 1.0" >> and it looks identical to the picture posted there. >> > Groovy! > >>> "EzCap EZTV646 has got RTL2832U/FC0012. However rtl-sdr must be tweaked >>> to force FC0012 tuner because it has the same PID as EZTV668 (PID: >>> 0x2838) so running it whithout a tweak will select Elonics E4000 tuner. >>> Works, not so good at filtering." >>> ? >>> Conclusion: >>> At least two devices share same vid/pid with different tuners - fc0012 >>> vs e4000. >>> How to resolve this from a drivers perspective in a proper way? >> >> This is not a big problem: the rtl2832 driver should read the tuner type >> from an internal register and load the proper module (or exit with an >> error message if the tuner is unsupported). >> > Ack, thanks! > >>> Beside, >>> there is GPL'ed 'e4k' tuner source code aka 'e4000 improved'*** (Elonics >>> E4000) >>> by Harald Welte >>> http://cgit.osmocom.org/cgit/osmo-sdr/tree/firmware/src/tuner_e4k.c >>> http://sdr.osmocom.org/trac/ >>> http://sdr.osmocom.org/trac/wiki/rtl-sdr >>> http://wiki.spench.net/wiki/RTL2832U*** >> >> Very nice. So we should ask Harald Welte if he is willing to have his >> driver merged in the kernel. >> > Undoubtedly! > Please ping Thomas and Antti, accordingly. > >>> regards, >>> poma >>> >> >> Regards, >> Gianluca > > regards, > poma > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majordomo@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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
la 5.5.2012 19:01 Thomas Mair kirjoitti: > I am currently finishing up the work at the demod driver and will > probably send a new version to the list tomorrow. Nice! I will try to review it on Monday... I looked quickly your old patch last week and tuner driver was done by Hans-Frieder Vogt. I think he should send tuner patch first and then your rtl2832 applied top of that. > As I don't own a device with a different tuner than the fc0012 I will > include an error message about the unsupported tuner and print its > type. So It is easier to get the information about the tuners. Sounds good. > Right now I am writing the signal_strength callback and stumbled upon > the following problem: > The signal strength is read from the fc0012 tuner (only for fc0012). > How should the driver implement this situation. Is there a callback I > could implement within the tuner or should I just read the tuner > registers from the demodulator? Demod should report signal strength, normally based IF AGC. But that estimation is very poor, tuner could report it more accurate. On optimal situation you should implement demod callback for signal strength and if there is tuner callback then override demod callback in order to get better reports. IMHO that override should be done in DVB-USB driver, in that case dvb-usb-rtl2832u. So when you attach rtl2832u just after that override demod callback with tuner. regards Antti -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
--- rtl28xxu.c.bcp 2012-05-03 06:44:32.958461395 +0200 +++ rtl28xxu.c 2012-05-03 08:11:57.463559065 +0200 @@ -1052,6 +1052,15 @@ RTL2831U_14AA_0161, RTL2832U_0CCD_00A9, RTL2832U_1F4D_B803, + RTL2832U_0BDA_2838, + RTL2832U_0458_707F, + RTL2832U_1B80_D39D, + RTL2832U_1B80_D393, + RTL2832U_1B80_D394, + RTL2832U_1B80_D395, + RTL2832U_1B80_D399, + RTL2832U_1F4D_C803, + RTL2832U_1F4D_D803, }; static struct usb_device_id rtl28xxu_table[] = { @@ -1068,6 +1077,24 @@ USB_DEVICE(USB_VID_TERRATEC, USB_PID_TERRATEC_CINERGY_T_STICK_BLACK)}, [RTL2832U_1F4D_B803] = { USB_DEVICE(USB_VID_GTEK, USB_PID_GTEK)}, + [RTL2832U_0BDA_2838] = { + USB_DEVICE(USB_VID_REALTEK, USB_PID_EZCAP_EZTV646)}, + [RTL2832U_0458_707F] = { + USB_DEVICE(USB_VID_KYE, USB_PID_GENIUS_TVGO_DVB_T03_2)}, + [RTL2832U_1B80_D39D] = { + USB_DEVICE(USB_VID_KWORLD_2, USB_PID_SVEON_STV20_2)}, + [RTL2832U_1B80_D393] = { + USB_DEVICE(USB_VID_KWORLD_2, USB_PID_KWORLD_D393)}, + [RTL2832U_1B80_D394] = { + USB_DEVICE(USB_VID_KWORLD_2, USB_PID_HU394)}, + [RTL2832U_1B80_D395] = { + USB_DEVICE(USB_VID_KWORLD_2, USB_PID_KWORLD_D395)}, + [RTL2832U_1B80_D399] = { + USB_DEVICE(USB_VID_KWORLD_2, USB_PID_KWORLD_D399)}, + [RTL2832U_1F4D_C803] = { + USB_DEVICE(USB_VID_GTEK, USB_PID_NOT_ONLY_LV5TDELUXE)}, + [RTL2832U_1F4D_D803] = { + USB_DEVICE(USB_VID_GTEK, USB_PID_PROLECTRIX_DV107669)}, {} /* terminating entry */ }; @@ -1181,7 +1208,7 @@ .i2c_algo = &rtl28xxu_i2c_algo, - .num_device_descs = 2, + .num_device_descs = 11, .devices = { { .name = "Terratec Cinergy T Stick Black", @@ -1195,6 +1222,60 @@ &rtl28xxu_table[RTL2832U_1F4D_B803], }, }, + { + .name = "EzCAP EzTV646", + .warm_ids = { + &rtl28xxu_table[RTL2832U_0BDA_2838], + }, + }, + { + .name = "Genius TVGo DVB-T03 2", + .warm_ids = { + &rtl28xxu_table[RTL2832U_0458_707F], + }, + }, + { + .name = "Sveon STV20 2", + .warm_ids = { + &rtl28xxu_table[RTL2832U_1B80_D39D], + }, + }, + { + .name = "DVB-T TV Stick D393", + .warm_ids = { + &rtl28xxu_table[RTL2832U_1B80_D393], + }, + }, + { + .name = "DIKOM USB-DVBT HD - HU394", + .warm_ids = { + &rtl28xxu_table[RTL2832U_1B80_D394], + }, + }, + { + .name = "DVB-T TV Stick D395", + .warm_ids = { + &rtl28xxu_table[RTL2832U_1B80_D395], + }, + }, + { + .name = "DVB-T TV Stick D399", + .warm_ids = { + &rtl28xxu_table[RTL2832U_1B80_D399], + }, + }, + { + .name = "Not Only TV DVB-T USB DELUXE LV5TDELUXE", + .warm_ids = { + &rtl28xxu_table[RTL2832U_1F4D_C803], + }, + }, + { + .name = "PROlectrix USB DVB-T & DAB Dongle DV107669", + .warm_ids = { + &rtl28xxu_table[RTL2832U_1F4D_D803], + }, + }, } },