From: Antti Palosaari <crope@iki.fi>
To: Torsten Seyffarth <t.seyffarth@gmx.de>
Cc: poma <pomidorabelisima@gmail.com>, linux-media@vger.kernel.org
Subject: Re: Cinergy TStick RC rev.3 (rtl2832u) only 4 programs
Date: Mon, 03 Jun 2013 00:12:51 +0300 [thread overview]
Message-ID: <51ABB553.702@iki.fi> (raw)
In-Reply-To: <51AA00DD.4020201@gmx.de>
On 06/01/2013 05:10 PM, Torsten Seyffarth wrote:
>
> Am 30.05.2013 21:50, schrieb poma:
>> You've used the original driver provided by Realtek, 'dvb-usb-rtl2832'.
>> You are currently using GPL'd, 'dvb_usb_v2', 'dvb_usb_rtl28xxu' and
>> 'e4000' designed by Antti & Thomas.
>>
>
> So I will try to find another useful option for this stick.
> How do I prevent similar problems with the next stick I buy?
It is most likely e4000 bug. Some corner case. It is surely very easy to
find out, will take only 1-2 hours or so when you could reproduce it and
you know what to do.
Just take USB sniffs from working configuration, generate tuner register
write code and copy & paste that to the tuner driver until it starts
working. After that you could find out problematic registers quite seen
just trial and error method.
Lastly someone sends me non-working rtl2832u + e4000 device. I put just
same transmission parameters, which was said non-working, to my
modulator and it worked! Likely signal got from modulator was so perfect
that I was unable to reproduce issue.
Best thing what you could to is just to jump in and start fixing these
drivers yourself. There is only very few person who do these nowadays.
It is just lack of developers!
regards
Antti
--
http://palosaari.fi/
prev parent reply other threads:[~2013-06-02 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 11:39 Cinergy TStick RC rev.3 (rtl2832u) only 4 programs Torsten Seyffarth
2013-05-30 15:27 ` poma
2013-05-30 17:30 ` Torsten Seyffarth
2013-05-30 19:50 ` poma
2013-06-01 14:10 ` Torsten Seyffarth
2013-06-02 21:12 ` Antti Palosaari [this message]
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=51ABB553.702@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=pomidorabelisima@gmail.com \
--cc=t.seyffarth@gmx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).