From: Christoph Pfister <christophpfister@gmail.com>
To: linux-dvb@linuxtv.org
Cc: Andrea <mariofutire@googlemail.com>
Subject: Re: [linux-dvb] [PATCH] 2 patches for dvb-apps gnutv
Date: Fri, 18 Jul 2008 22:46:17 +0200 [thread overview]
Message-ID: <200807182246.17897.christophpfister@gmail.com> (raw)
In-Reply-To: <g5llos$b75$1@ger.gmane.org>
Am Mittwoch 16 Juli 2008 22:28:33 schrieb Andrea:
> Hi,
>
> I would like to repost 2 patches for gnutv, part of dvb-apps.
>
> http://www.linuxtv.org/pipermail/linux-dvb/2008-July/027177.html
>
> They both try to make gnutv more robust when the system/destination file
> system are temporary slow.
>
> 1) http://www.linuxtv.org/pipermail/linux-dvb/2008-July/027176.html
> Once the dvb ringbuffer overflows, it is pointless to stop gnutv. I think
> it should continue and get the rest of the signal.
> What has been lost has been lost, let's not loose the future stream
>
> 2) http://www.linuxtv.org/pipermail/linux-dvb/2008-July/027177.html
> Allow to set a bigger (than default = 2MB) dvb ringbuffer to cope with
> temporary bottlenecks.
>
> Is anybody interested in reviewing them?
Guess no.
But I'll rework the first patch a bit (the sequence of revents <--> errno
check is already bogus) and commit them. And I really suggest you to use an
application like dvbstream which does its own buffering (at least I hope
so ;) - because it has never happened to me yet that the ringbuffer
overflowed (and it shouldn't with sane applications).
> Andrea
Christoph
_______________________________________________
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-18 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 20:28 [linux-dvb] [PATCH] 2 patches for dvb-apps gnutv Andrea
2008-07-18 20:46 ` Christoph Pfister [this message]
2008-07-19 21:09 ` Andrea
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=200807182246.17897.christophpfister@gmail.com \
--to=christophpfister@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=mariofutire@googlemail.com \
/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