From: Ales Jurik <ajurik@quick.cz>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Re : Re : Re : problems with multiproto & dvb-s2 with high SR, losing parts of stream
Date: Tue, 15 Jul 2008 14:59:04 +0200 [thread overview]
Message-ID: <200807151459.05223.ajurik@quick.cz> (raw)
In-Reply-To: <1216090536l.1474l.2l@manu-laptop>
On Tuesday 15 of July 2008, manu wrote:
> Le 14.07.2008 16:14:16, Goga777 a écrit :
> > > > > And you could retrieve the stream with no problemn even watch
> >
> > it?
> >
> > > > do you mean H264/ffmpeg decoding problem ? Ah, I can't open these
> > > > encrypted channels
> > >
> > > Is it a card problem? I mean my TT-3200 has problems to tune on
> >
> > some
> >
> > > channels, but when it tunes the CI/CAM works perfectly (here almost
> > > every channel is encrypted). Does HVR-4000 has a good CI?
> >
> > I don't have the card, that's why I can't open these channels. We
> > have
> > spoken about LOCK :)
>
> Hmm OK I understand now ;-)
> I was just trying to see if someone around here has found a good dvb-S2
> card with perfect recpetion and good cam support...
> Thx
> Bye
> Manu
Hi,
I'm still thinking that problem is in driver - under Windows everything seems
to be ok. So I've tried to capture i2c bus between stb0899 and stb6100 and
got things like this:
Start of driver - linux
Monitoring completed
0uS: 63 r 48
339uS: 63 W 01
115uS: 66 W -nak-
96uS: 51 r 78 01 00 . .
279uS: 06 r -nak-
130uS: 61 W A0 85 .
202uS: 43 W 90
607uS: 47 W -nak-
124uS: 50 W 40 00 .
326uS: 44 W 80 01 .
204uS: 43 r -nak-
276uS: 43 r -nak-
131uS: 52 r 00 00 .
329uS: 65 W 05 53 S
812uS: 51 r -nak-
125uS: 50 W 40 00 .
353uS: 02 W
Done
Start if driver - Windows
Monitoring completed
0uS: 68 W F0 A0 32 . 2
383uS: 68 W F0 A1 80 . .
382uS: 68 W F0 A4 04 . .
381uS: 68 W F0 A5 00 . .
381uS: 68 W F0 A6 00 . .
383uS: 68 W F0 A7 00 . .
382uS: 68 W F0 A8 20 .
383uS: 68 W F0 A9 8C . .
381uS: 68 W F0 AA 9A . .
381uS: 68 W F1 01 0B . .
382uS: 68 W F1 10 11 . .
382uS: 68 W F1 11 0A . .
383uS: 68 W F1 12 05 . .
382uS: 68 W F1 13 00 . .
381uS: 68 W F1 14 00 . .
384uS: 68 W F1 1C 00 . .
382uS: 68 W F1 1D 00 . .
382uS: 68 W F1 20 FE .
382uS: 68 W F1 21 80 ! .
384uS: 68 W F1 22 BC " .
381uS: 68 W F1 23 F4 # .
383uS: 68 W F1 24 F3 $ .
381uS: 68 W F1 25 FC % .
384uS: 68 W F1 26 FF & .
381uS: 68 W F1 27 FF ' .
382uS: 68 W F1 28 00 ( .
383uS: 68 W F1 29 88 ) .
381uS: 68 W F1 2A 5C * \
Done
More captures are available - if somebody is interesting in, I'm ready to post
it.
All captures are done within the same hw environment with i2c monitoring
interface from http://ivtv.writeme.ch/tiki-index.php?page=Monitoring+I2C+Bus.
BR,
Ales
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-07-15 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 8:45 [linux-dvb] problems with multiproto & dvb-s2 with high SR, losing parts of stream Newsy Paper
2008-07-14 12:26 ` Goga777
2008-07-14 13:46 ` [linux-dvb] Re : " manu
2008-07-14 17:51 ` Goga777
2008-07-14 19:16 ` [linux-dvb] Re : " manu
2008-07-14 20:14 ` Goga777
2008-07-15 2:55 ` [linux-dvb] Re : " manu
2008-07-15 12:59 ` Ales Jurik [this message]
2008-07-15 11:43 ` [linux-dvb] " Newsy Paper
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=200807151459.05223.ajurik@quick.cz \
--to=ajurik@quick.cz \
--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