From: Marek Ochaba <ochaba@maindata.sk>
To: "Christian Prähauser" <cpraehaus@cosy.sbg.ac.at>
Cc: linux-media@vger.kernel.org,
Konstantin Dimitrov <kosio.dimitrov@gmail.com>,
"statelov@maindata.sk" <statelov@maindata.sk>
Subject: Re: DVB-S2 multistream support
Date: Mon, 23 Jan 2012 14:58:43 +0100 [thread overview]
Message-ID: <4F1D6793.8090605@maindata.sk> (raw)
In-Reply-To: <FD47BCF3-7867-4296-A3CB-FB31DA6021E0@cosy.sbg.ac.at>
Hello Christian & Konstantin,
we look forward for your patch. Here are some hints, what we want to do.
Now we read TS packets from standard userspace API (/dev/dvb/adapter0/dvr0,
for video data processing) or use libdvbapi/dvbnet.h (for IP over DVB data,
MPE decapsulation). In future we want to receive ACM/GSE data. So we plan
to read whole BBFrame data and decapsulate it. But if there will be GSE
decapsulation in linuxtv.org kernel layer, then we don't need whole BBFrame.
It would be nice to have acces to some usefull data from BBF headers
particularly: TS/GS field, SIS/MIS flag, CCM/ACM flag, it should be
statical value throught several BBF. Other usefull data which is diffrent
from more BBF is Imput stream ID (ISI). Can it be accesible as list of
received values ?
This values could be accessible throught standard S2API sytem call
ioctl(FE_GET_PROPERTY, struct dtv_property)
or if whole BBFrame/BBFheader will be accessible, we can read it ourself
from BBF header.
BTW: We have GPL source code for GSE decapsulation from Karsten Siebert. If
you don't have implement yet, this one can be used, it is in "kernel space"
compatible format.
--
Marek Ochaba
next prev parent reply other threads:[~2012-01-23 13:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 1:06 DVB-S2 multistream support Georgi Chorbadzhiyski
2011-12-25 8:23 ` Antti Palosaari
2011-12-25 10:17 ` Mauro Carvalho Chehab
2011-12-25 10:55 ` Konstantin Dimitrov
2011-12-25 11:18 ` Mauro Carvalho Chehab
2011-12-25 12:37 ` Konstantin Dimitrov
2011-12-27 10:12 ` Christian Prähauser
2011-12-27 16:08 ` Antti Palosaari
2012-01-19 13:34 ` Marek Ochaba
2012-01-21 10:29 ` Christian Prähauser
2012-01-23 13:58 ` Marek Ochaba [this message]
2012-01-22 2:13 ` Mauro Carvalho Chehab
2012-01-22 12:44 ` Christian Prähauser
[not found] ` <CAF0Ff2mf0tYs3UG3M6Cahep+_kMToVaGgPhTqR7zhRG0UXWuig@mail.gmail.com>
[not found] ` <85A7A8FC-150C-4463-B09C-85EED6F851A8@cosy.sbg.ac.at>
[not found] ` <CAF0Ff2ncv0PJWSOOw=7WeGyqX3kKiQitY52uEOztfC8Bwj6LgQ@mail.gmail.com>
2012-01-25 13:12 ` Christian Prähauser
2012-02-01 18:49 ` Konstantin Dimitrov
2012-02-18 19:06 ` Christian Prähauser
2012-02-19 23:12 ` Konstantin Dimitrov
2012-03-07 16:33 ` Bob Winslow
2012-03-13 9:36 ` Marek Ochaba
2012-03-13 12:30 ` Bob W
2012-03-13 15:22 ` Konstantin Dimitrov
2012-03-13 15:47 ` Bob W
2012-03-15 9:40 ` Christian Prähauser
2012-03-19 8:46 ` Christian Prähauser
2012-03-19 15:19 ` Konstantin Dimitrov
2012-04-24 22:18 ` Bob W
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=4F1D6793.8090605@maindata.sk \
--to=ochaba@maindata.sk \
--cc=cpraehaus@cosy.sbg.ac.at \
--cc=kosio.dimitrov@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=statelov@maindata.sk \
/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;
as well as URLs for NNTP newsgroup(s).