From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Akihiro TSUKADA <tskd2@yahoo.co.jp>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [RFC] dvb-apps ported for ISDB-T
Date: Fri, 25 Dec 2009 19:21:40 -0200 [thread overview]
Message-ID: <4B352CE4.7070103@redhat.com> (raw)
In-Reply-To: <4B34DB3C.6010805@yahoo.co.jp>
Em 25-12-2009 13:33, Akihiro TSUKADA escreveu:
>
> Hi Mauro,
>
>>> I wrote several patches those days in order to allow dvb-apps to properly
>>> parse ISDB-T channel.conf.
>
> I think it would be convenient if channel.conf allows
> the kind of format of PROPNAME=VALUE list, for readability and extensibility
> of the conf file.
>
> there are already so many parameters in ISDB-T,
> so it is a bit difficult for the users to remember and correctly specify
> all the field in the right order.
> besides they have to be careful in counting the delimiter character
> when some (most?) parameters can be omitted or be left to the device/region default.
>
> and when I consider extending this lib to ISDB-S (for example),
> I have to add "TS-id" parameter,
> which leads to the re-definition of the data structure and requires re-building.
> So, it would be convenient if I could write for example like,
> DTV_FREQUENCY=1049480:DTV_ISDBS_TS_ID=1
It shouldn't be hard to add it, by writing a new parser file and a new dump file.
Currently, there are two parser files and two dump files: one for vdr and one for
zap format.
I opted to not do it to avoid breaking compatibility with those two applications.
Cheers,
Mauro.
next prev parent reply other threads:[~2009-12-25 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 2:17 [RFC] dvb-apps ported for ISDB-T Mauro Carvalho Chehab
2009-12-25 3:09 ` Mauro Carvalho Chehab
2009-12-25 11:25 ` Patrick Boettcher
2009-12-25 21:19 ` Mauro Carvalho Chehab
2009-12-31 22:23 ` Mauro Carvalho Chehab
2010-01-04 16:49 ` Manu Abraham
2009-12-25 15:33 ` Akihiro TSUKADA
2009-12-25 21:21 ` Mauro Carvalho Chehab [this message]
2009-12-27 22:08 ` Manu Abraham
2009-12-28 3:49 ` Mauro Carvalho Chehab
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=4B352CE4.7070103@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=tskd2@yahoo.co.jp \
/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