From: Andrea <mariofutire@googlemail.com>
To: Thierry Lelegard <thierry.lelegard@tv-numeric.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] RE : Length of /dev/dvb/adapter0/dvr0's buffer.
Date: Sat, 01 Mar 2008 09:14:22 +0000 [thread overview]
Message-ID: <47C91E6E.3060006@googlemail.com> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAJf2pBr8u1U+Z+cArRcz8PAKHAAAQAAAAnIT3wzzVLUSYmPE4pB04JwEAAAAA@tv-numeric.com>
Thierry Lelegard wrote:
>> I'm trying to read from /dev/dvb/adapter0/dvr0.
>> The problem is that the process reading sometimes is not fast enough and after a while I get errno
>> 75 when I try to read from it.
>>
>> On average the speed is ok, so it should work.
>> There must be a buffer behind dvr0 that goes in error onece it is full.
>>
>> 1) how can I make it bigger?
>> 2) how can I check how full it is?
>
> You can set the *demux* buffer size, upstream from dvr, using ioctl DMX_SET_BUFFER_SIZE.
> The default value is 8 kB. Using 1 MB, I can do full TS capture without any loss.
>
>
I've noticed that there are 2 ioctl DMX_SET_BUFFER_SIZE, one for the demux, one for the dvr.
The second is not implemented.
switch (cmd) {
case DMX_SET_BUFFER_SIZE:
// FIXME: implement
ret = 0;
break;
Could you please help me:
1) how many ringbuffers are there?
2) I'm reading from dvr, which one do I need to set?
3) I can try to implement the above code if needed.
Cheers
Andrea
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-03-01 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 22:26 [linux-dvb] Length of /dev/dvb/adapter0/dvr0's buffer Andrea
2008-02-25 8:58 ` [linux-dvb] RE : " Thierry Lelegard
2008-03-01 9:14 ` Andrea [this message]
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=47C91E6E.3060006@googlemail.com \
--to=mariofutire@googlemail.com \
--cc=linux-dvb@linuxtv.org \
--cc=thierry.lelegard@tv-numeric.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