From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Antti Palosaari <crope@iki.fi>
Cc: Georgi Chorbadzhiyski <gf@unixsol.org>, linux-media@vger.kernel.org
Subject: Re: DVB-S2 multistream support
Date: Sun, 25 Dec 2011 08:17:48 -0200 [thread overview]
Message-ID: <4EF6F84C.3000307@redhat.com> (raw)
In-Reply-To: <4EF6DD91.2030800@iki.fi>
On 25-12-2011 06:23, Antti Palosaari wrote:
> On 12/25/2011 03:06 AM, Georgi Chorbadzhiyski wrote:
>> Guys are there any news on DVB-S2 multistream support. I have
>> found test patches at http://www.tbsdtv.com/forum/viewtopic.php?f=26&t=1874
>> and judging by report on dvblast-devel ML they seem to work.
>>
>> What is holding them back, perhaps nobody submitted them?
I don't remember seeing any patches submitted for it.
The patch "budget-omicom.patch" seems to be a hack that will likely break support
for other supported devices.
The patch stv090x-mis.patch also seems wrong, as "props->dvbs2_mis_id" is probably
initialized with 0 by the core, so, by default, the MIS filter will be enabled.
That's said, the approach there assumes that just one mis can be filtered. I'm wandering
if it wouldn't be better to use the same approach taken inside dvb-core for PIP filtering.
In any case, the dvb properties cache should be initialized to have the MIS filter
disabled, and only enable it if userspace requests it via FE_SET_PROPERTY.
> Ok, there seems to be now TS IDs for ISDB-S, DVB-T2 and DVB-S2. I wonder who those are
> defined in our DVB API as own parameter for each standard...
The per-standard parameters were introduced by ISDB-T. It probably makes sense for
the ISDB specific parameters, as no other delivery system looks like that, but we should
avoid propagating it for other delivery systems, expecially DVB-*, as the new parameters
may be used on other delivery systems on that family.
It would be great to fix this as soon as possible, in order to avoid propagating it.
The fix should be simple: just rename the parameter, and create an alias to the
previous name.
Regards,
Mauro
>
> Antti
>
>
next prev parent reply other threads:[~2011-12-25 10:18 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 [this message]
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
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=4EF6F84C.3000307@redhat.com \
--to=mchehab@redhat.com \
--cc=crope@iki.fi \
--cc=gf@unixsol.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;
as well as URLs for NNTP newsgroup(s).