From: Newsy Paper <newspaperman_germany@yahoo.com>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] TT S2-3200 driver
Date: Thu, 17 Jul 2008 19:07:47 +0000 (GMT) [thread overview]
Message-ID: <168825.3161.qm@web23207.mail.ird.yahoo.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2007 bytes --]
Thanks very much for your patch. Channel switching is now really much faster (even ondvb-s(1) channels).
Unfortunately transponders with 8PSK 30000-3/4 aren't working correctly. I can lock them when choosing a SR of 29998. Still part of the stream is lost.. Only 6 Mbit/s of Video data (instead of 12 Mbit/s) and I can only see some pixels.
kind regards
Newsy
--- Ales Jurik <ajurik@quick.cz> schrieb am Do, 17.7.2008:
Von: Ales Jurik <ajurik@quick.cz>
Betreff: [linux-dvb] TT S2-3200 driver
An: linux-dvb@linuxtv.org
Datum: Donnerstag, 17. Juli 2008, 0:23
Hi,
please try attached patch. With this patch I'm able to get lock
on channels
before it was impossible. But not at all problematic channels and the
reception is not without errors. Also it seems to me that channel switching is
quicklier.
Within investigating I've found some problems, I've tried to compare
data with
data sent by BDA drivers under Windows (by monitoring i2c bus between stb0899
and stb6100):
- under Windows stb6100 reports not so wide bandwith. (23-31MHz, 21-22MHz and
so on).
- under Windows the gain is set by 1 or 2 higher.
When setting those parameters constantly to values used under Windows nothing
change. So maybe some cooperation with stb0899 part of driver is necessary.
Also it is interesting that clock speed of i2c bus is 278kHz, not 400kHz
(measured with digital oscilloscope). But this should not have any influence.
Maybe somebody will be so capable to
continue?
BR,
Ales_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Unglücklich mit Ihrer Mail-Adresse?
Registrieren Sie Ihre Wunschmailadresse@ymail.com
Millionen neuer Mail-Adressen - jetzt bei Yahoo!
__________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com
[-- Attachment #1.2: Type: text/html, Size: 3171 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next reply other threads:[~2008-07-17 19:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 19:07 Newsy Paper [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-09 14:31 [linux-dvb] TT S2-3200 driver lucian orasanu
2008-07-17 11:36 lucian orasanu
2008-07-16 22:23 Ales Jurik
2008-07-17 9:18 ` ChaosMedia > WebDev
2008-07-17 10:20 ` Remy Bohmer
2008-07-17 11:37 ` Ales Jurik
2008-07-17 15:16 ` Remy Bohmer
2008-07-17 11:56 ` ChaosMedia > WebDev
2008-07-17 20:11 ` Remy Bohmer
2008-07-17 13:20 ` Daniel Hellström
2008-07-18 13:02 ` Daniel Hellström
2008-07-20 12:27 ` Meysam Hariri
[not found] ` <265474.68505.qm@web23207.mail.ird.yahoo.com>
2008-07-21 16:23 ` Meysam Hariri
2008-07-22 7:53 ` HSS-NOC
2008-07-24 10:06 ` Newsy Paper
2008-09-07 20:53 ` Manu Abraham
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=168825.3161.qm@web23207.mail.ird.yahoo.com \
--to=newspaperman_germany@yahoo.com \
--cc=linux-dvb@linuxtv.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