From: Manu Abraham <abraham.manu@gmail.com>
To: crow <crow@linux.org.ba>
Cc: linux-media@vger.kernel.org
Subject: Re: Re : [linux-dvb] Technotrend Budget S2-3200 Digital artefacts on HDchannels
Date: Wed, 28 Jan 2009 23:48:18 +0400 [thread overview]
Message-ID: <4980B682.4010406@gmail.com> (raw)
In-Reply-To: <3c031ccc0901280907i46d8c7b2i5e92581b265ba7c9@mail.gmail.com>
crow wrote:
> Hi,
> I have also TT-3200 and would like to have driver which are not able
> to burn anything, but to WORK as they should. I am currently using
> liplianindvb repository, because it seems only one working with my
> card. To bad that they have code which "can burn demodulator" in some
> case, as i don't wanna that. Well till now i have had luck then seems
> so, but....
> I can use multiproto driver to but they should work OK with tt-3200 (i
> can test them to if needed) have only Astra 19.2E and Hotbird 13.0.
You can use either multiproto or S2API according to your desire.
The S2API based driver is found here: http://jusst.de/hg/v4l-dvb
If you want to try the multiproto version the driver is found here:
http://jusst.de/hg/multiproto
Please do a vanilla test of the v4l-dvb tree (from jusst.de),
whether you see any further difference.
Please try the changes that which i posted on top of the multiproto
or the v4l-dvb tree and test your changes.
You can test with loading the modules with the verbose=5 option,
such that you can see what's happening internally.
To test, rather than doing a scan, you should try doing a szap,
since it is better for testing and to find issues. Testing with scan
will not help much as there will be other issues involved in it as
well.
Regards,
Manu
next prev parent reply other threads:[~2009-01-28 19:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 14:40 [linux-dvb] Technotrend Budget S2-3200 Digital artefacts on HDchannels Newsy Paper
2009-01-26 15:39 ` Chris Silva
2009-01-26 15:41 ` Chris Silva
2009-01-26 15:44 ` Alex Betis
2009-01-26 15:51 ` Chris Silva
2009-01-26 16:08 ` Chris Silva
2009-01-26 16:19 ` Alex Betis
2009-01-26 17:50 ` Manu Abraham
2009-01-26 18:18 ` Faruk A
2009-01-26 19:07 ` Alex Betis
2009-01-27 20:14 ` Manu Abraham
2009-01-27 20:40 ` Alex Betis
2009-01-27 21:27 ` Manu Abraham
2009-01-27 21:45 ` Manu Abraham
2009-01-27 22:02 ` Alex Betis
2009-01-27 23:02 ` Manu Abraham
2009-01-28 11:03 ` n37
2009-01-28 16:19 ` Re : " Manu
2009-01-28 17:07 ` crow
2009-01-28 19:48 ` Manu Abraham [this message]
2009-01-28 18:04 ` Goga777
2009-01-28 19:52 ` Manu Abraham
2009-01-28 21:32 ` Re : " Manu
2009-01-28 22:43 ` Manu
2009-01-26 19:30 ` Manu
2009-01-26 20:12 ` Chris Silva
2009-01-26 20:28 ` Ales Jurik
2009-01-27 20:05 ` Manu Abraham
[not found] ` <1232998154.24736.2@manu-laptop>
2009-01-27 19:56 ` [linux-dvb] Re : " Manu Abraham
2009-01-27 20:37 ` Alex Betis
2009-01-27 21:13 ` Manu Abraham
2009-01-27 21:31 ` Alex Betis
2009-02-02 16:44 ` Jonas Kvinge
2009-02-02 22:43 ` Chris Silva
2009-02-02 23:46 ` Re : " Manu
2009-02-05 13:08 ` Manu
2009-02-05 23:50 ` Manu Abraham
2009-02-06 15:22 ` Re : " Manu
[not found] ` <157f4a8c0902141355w3872bc0eif7796679f7f5323f@mail.gmail.com>
2009-02-14 22:34 ` Chris Silva
2009-02-14 22:46 ` Chris Silva
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=4980B682.4010406@gmail.com \
--to=abraham.manu@gmail.com \
--cc=crow@linux.org.ba \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox