From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: CrazyCat <crazycat69@yandex.ru>
Cc: Antti Palosaari <crope@iki.fi>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH] dvb_frontend: Multistream support
Date: Fri, 17 Aug 2012 15:48:31 -0300 [thread overview]
Message-ID: <502E91FF.2090609@redhat.com> (raw)
In-Reply-To: <791451345225958@web24h.yandex.ru>
Em 17-08-2012 14:52, CrazyCat escreveu:
> 16.08.2012, 21:11, "Antti Palosaari" <crope@iki.fi>:
>> @Mauro, should we rename also DTV_ISDBS_TS_ID to DTV_ISDBS_TS_ID_LEGACY
>> to remind users ?
>
> Maybe leave DTV_ISDBS_TS_ID and convert DTV_DVBT2_PLP_ID to DTV_DVB_STREAM_ID ? and dvbt2_plp_id convert to dvb_stream_id.
>
> Because DVB and ISDB different standards and look like stream id for ISDB is 16 bit, for DVB-S2/T2 8 bit.
Well, Frequency range in satellite standards are in kHz, while the frequencies on
the other ones are in Hz. So, I don't think that the number of bits should limit
it. In a matter of fact, even on DVB-T/T2, DVB-S/S2, ... there are some fields
that gained more bits.
So, I don't see any issue on using DTV_DVB_STREAM_ID on all of them, even if
the number of bits are different.
Of course, the API documentation should be clear about the field differences.
Regards,
Mauro.
next prev parent reply other threads:[~2012-08-17 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 17:46 [PATCH] dvb_frontend: Multistream support CrazyCat
2012-08-16 18:11 ` Antti Palosaari
2012-08-16 23:14 ` Mauro Carvalho Chehab
2012-08-17 17:21 ` CrazyCat
2012-08-17 18:52 ` Antti Palosaari
2012-08-17 19:01 ` Mauro Carvalho Chehab
2012-08-21 0:42 ` CrazyCat
2012-08-21 20:42 ` Georgi Chorbadzhiyski
2012-09-11 18:18 ` Mauro Carvalho Chehab
2012-08-17 17:52 ` CrazyCat
2012-08-17 18:48 ` Mauro Carvalho Chehab [this message]
2012-08-17 1:11 ` Akihiro TSUKADA
-- strict thread matches above, loose matches on Subject: below --
2012-09-13 14:13 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=502E91FF.2090609@redhat.com \
--to=mchehab@redhat.com \
--cc=crazycat69@yandex.ru \
--cc=crope@iki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.