From: poma <pomidorabelisima@gmail.com>
To: linux-media@vger.kernel.org, gennarone@gmail.com
Subject: Re: [PATCH v2] add support for DeLOCK-USB-2.0-DVB-T-Receiver-61744
Date: Fri, 04 May 2012 03:27:32 +0200 [thread overview]
Message-ID: <4FA33084.7050204@gmail.com> (raw)
In-Reply-To: <4FA249DE.7000702@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?
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
next prev parent reply other threads:[~2012-05-04 1:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 21:42 [PATCH] Driver for RTL2832 demodulator chip Thomas Mair
2012-04-30 9:38 ` poma
2012-04-30 15:39 ` [PATCH v2] add support for DeLOCK-USB-2.0-DVB-T-Receiver-61744 Thomas Mair
2012-05-01 6:48 ` poma
2012-05-03 7:25 ` poma
2012-05-03 9:03 ` Gianluca Gennari
2012-05-04 1:27 ` poma [this message]
2012-05-04 13:49 ` Gianluca Gennari
2012-05-05 0:33 ` poma
2012-05-05 16:01 ` Thomas Mair
2012-05-05 16:54 ` Hans-Frieder Vogt
2012-05-05 17:02 ` Antti Palosaari
2012-05-04 13:57 ` Gianluca Gennari
[not found] ` <CAKZ=SG8SjH1C0E38iGjQfJvzi+uTy=dL_9jOxAetgOhkUp5t7g@mail.gmail.com>
2012-05-05 0:18 ` poma
2012-05-03 18:17 ` Zdenek Styblik
2012-05-04 1:34 ` poma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FA33084.7050204@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=gennarone@gmail.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.