From: AlexW <HondaNSX@gmx.de>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] RFC - Flexcop Streaming watchdog (VDSB)
Date: Fri, 16 Jan 2009 19:39:32 +0100 [thread overview]
Message-ID: <4970D464.5070509@gmx.de> (raw)
In-Reply-To: <alpine.LRH.1.10.0901161548460.28478@pub2.ifh.de>
Patrick Boettcher wrote:
> Hi lists,
>
> For years there has been the Video Data Stream Borken-error with VDR and
> Technisat cards: The error occured randomly and unfrequently. A
> work-around for that problem was to restart VDR and let the driver
> reset the pid-filtering and streaming interface.
>
> In fact it turned out, that the problem is worse with setups not based
> on VDR and the "VDSB-error" could be really easily reproduced (I'm not
> sure if this applies to all generations on SkyStar2-card). I'm
> skipping the description of the problem here...
>
>
Which generation of cards have this problem? I did not see any VDSB with
my two Skystar 2.6D.
BR,
Walter
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2009-01-16 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 15:03 RFC - Flexcop Streaming watchdog (VDSB) Patrick Boettcher
2009-01-16 18:39 ` AlexW [this message]
2009-01-16 23:40 ` [linux-dvb] " BOUWSMA Barry
2009-01-17 8:29 ` Patrick Boettcher
2009-01-17 10:50 ` BOUWSMA Barry
2009-01-17 12:36 ` BOUWSMA Barry
2009-01-17 13:18 ` Andy Walls
2009-01-17 18:28 ` Luca Olivetti
2009-01-17 3:37 ` Andy Walls
2009-01-25 21:17 ` Matthias Schwarzott
2009-01-26 15:05 ` Patrick Boettcher
2009-02-09 15:13 ` Patrick Boettcher
2009-04-25 16:08 ` [linux-dvb] " BOUWSMA Barry
2009-04-25 17:21 ` Luca Olivetti
2009-05-07 11:53 ` BOUWSMA Barry
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=4970D464.5070509@gmx.de \
--to=hondansx@gmx.de \
--cc=linux-dvb@linuxtv.org \
--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