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@xxxxxxxxx>: > 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@xxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
