From: Steven Toth <stoth@linuxtv.org>
To: Patrick Boettcher <patrick.boettcher@desy.de>,
linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] S2API - Code review and suggested changes (1)
Date: Thu, 11 Sep 2008 09:27:15 -0400 [thread overview]
Message-ID: <48C91CB3.50608@linuxtv.org> (raw)
In-Reply-To: <alpine.LRH.1.10.0809101111130.30794@pub2.ifh.de>
Patrick Boettcher wrote:
> Hi Steve,
>
> On Tue, 9 Sep 2008, Steven Toth wrote:
>> * I think it would be better to change TV_ to FE_ (because TV is by
>> * far not
>> * the only application for linux-dvb) , but this is a very unimportant
>> * detail.
>>
>> A few people prefer dtv_ and DTV_, rather than tv_ and TV_. is fe_
>> and FE_ still important to you?
>
> Expanding the term "dtv" to digital television and then translate
> television into "seeing something somewhere which takes/took place
> somewhere else" I can agree with the dtv-prefix.
>
> Still I think the term TV is used by a lot of people with different
> understandings. But except me nobody has seen the term dtv too
> restrictive, so I'm joining the majority.
>
> On thing I almost forgot: You should add a bandwidth-thing as an
> integer, like the frequency/symbolrate.
>
> For DVB-T we (DiBcom) can basicly run with any channel bandwidth, not
> only 5,6,7,8 MHz. And some people are even using it...
>
> Another example: DVB-SH is mentioning explicitly a 1.7 MHz bandwidth in
> the spec (default is 5MHz).
>
> Please consider adapting it.
I've added this to the list.
Thanks,
Steve
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-11 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 2:23 [linux-dvb] S2API - Code review and suggested changes (1) Steven Toth
2008-09-10 9:27 ` Patrick Boettcher
2008-09-11 13:27 ` Steven Toth [this message]
2008-09-11 13:35 ` Steven Toth
2008-09-12 5:17 ` Steven Toth
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=48C91CB3.50608@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=linux-dvb@linuxtv.org \
--cc=patrick.boettcher@desy.de \
/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