linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
	CrazyCat <crazycat69@yandex.ru>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	Manu Abraham <manu@linuxtv.org>
Subject: Re: [PATCH] DVB-S2 multistream support
Date: Sat, 11 Aug 2012 04:07:43 +0300	[thread overview]
Message-ID: <5025B05F.8090809@iki.fi> (raw)
In-Reply-To: <CAHFNz9KA1pHgxyjX5KdKgsy8nWgREkVFTVg38cox1TFNGJVqew@mail.gmail.com>

On 08/11/2012 03:31 AM, Manu Abraham wrote:
> On Sat, Aug 11, 2012 at 5:44 AM, Antti Palosaari <crope@iki.fi> wrote:
>> On 08/11/2012 01:12 AM, Mauro Carvalho Chehab wrote:
>>>
>>> Em 13-07-2012 20:15, CrazyCat escreveu:
>>
>>
>>>>    #define DTV_ISDBS_TS_ID               42
>>>>
>>>>    #define DTV_DVBT2_PLP_ID      43
>>>> +#define DTV_DVBS2_MIS_ID       43
>>>
>>>
>>> It would be better to define it as:
>>>
>>> #define DTV_DVBS2_MIS_ID        DTV_DVBT2_PLP_ID
>>>
>>> Even better, we should instead find a better name that would cover both
>>> DVB-T2 and DVB-S2 program ID fields, like:
>>>
>>> #define DTV_DVB_MULT            43
>>> #define DTV_DVBT2_PLP_ID        DTV_DVB_MULT
>>>
>>> And use the new symbol for both DVB-S2 and DVB-T2, deprecating the
>>> legacy symbol.
>>
>>
>> Also DTV_ISDBS_TS_ID means same. All these three DTV_ISDBS_TS_ID,
>> DTV_DVBT2_PLP_ID and DTV_DVBS2_MIS_ID are same thing - just named
>> differently between standards. I vote for common name TS ID (I have said
>> that already enough many times...).
>
> I agree, but a still more generic term like STREAM_ID would be more
> appropriate,

Ack. Since this stream could be something else than MPEG2-TS better to 
give more generic name.

> as it happens at different layers for different delivery
> systems.DVB-S2 additionally
> provides BBHEADER at Physical Layer. In any case setting PLP_ID for DVB-S2
> is completely confusing.
>
> Anyway, the demuxer part is also missing ..

Demuxer for MIS? I am not any familiar with MIS but I know there is 
"raw" demux payload used already for ATSC-M/H. It just passes all the 
data coming from demod "TS".

> If you look a bit more deeper, you will see that the framing structure
> with ISDB-T
> is exactly the same as with ISDB-S, which makes ISDB-T also no different, just
> that the frontend userspace header is just fucked up with junk.
>
> The major chunk for the ISDB-T stuff in the frontend header is
> completely redundant.
>
> Regards,
> Manu
>

regards
Antti

-- 
http://palosaari.fi/

  reply	other threads:[~2012-08-11  1:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 23:15 [PATCH] DVB-S2 multistream support CrazyCat
2012-08-10 22:12 ` Mauro Carvalho Chehab
2012-08-11  0:07   ` Manu Abraham
2012-08-11  0:14   ` Antti Palosaari
2012-08-11  0:31     ` Manu Abraham
2012-08-11  1:07       ` Antti Palosaari [this message]
2012-08-11  1:20         ` Manu Abraham
2012-08-11  1:22         ` CrazyCat
2012-08-11 22:55   ` CrazyCat
2012-08-12  0:00     ` Antti Palosaari
2012-08-12 18:33       ` CrazyCat
2012-08-12 18:50         ` Antti Palosaari
2012-08-12 19:12           ` Manu Abraham
2012-08-13 18:57           ` Mauro Carvalho Chehab
  -- strict thread matches above, loose matches on Subject: below --
2012-07-13 23:11 [PATCH]DVB-S2 " CrazyCat

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=5025B05F.8090809@iki.fi \
    --to=crope@iki.fi \
    --cc=abraham.manu@gmail.com \
    --cc=crazycat69@yandex.ru \
    --cc=linux-media@vger.kernel.org \
    --cc=manu@linuxtv.org \
    --cc=mchehab@redhat.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;
as well as URLs for NNTP newsgroup(s).