From: Artem Makhutov <artem@makhutov.org>
To: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] Add missing S2 caps flag to S2API
Date: Mon, 24 Nov 2008 08:12:04 +0100 [thread overview]
Message-ID: <492A53C4.5030509@makhutov.org> (raw)
In-Reply-To: <49293640.10808@cadsoft.de>
Hello,
Klaus Schmidinger schrieb:
> The attached patch adds a capability flag that allows an application
> to determine whether a particular device can handle "second generation
> modulation" transponders. This is necessary in order for applications
> to be able to decide which device to use for a given channel in
> a multi device environment, where DVB-S and DVB-S2 devices are mixed.
>
> It is assumed that a device capable of handling "second generation
> modulation" can implicitly handle "first generation modulation".
> The flag is not named anything with DVBS2 in order to allow its
> use with future DVBT2 devices as well (should they ever come).
>
> Signed-off by: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
Wouldn't it be better to add something like this:
FE_CAN_8PSK
FE_CAN_16APSK
FE_CAN_32APSK
or
FE_CAN_DVBS2
Instead of FE_CAN_2ND_GEN_MODULATION ? It is too generic for me.
Regards, Artem
_______________________________________________
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-11-24 7:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 10:53 [linux-dvb] [PATCH] Add missing S2 caps flag to S2API Klaus Schmidinger
2008-11-23 11:47 ` [PATCH] Add Compro VideoMate E650F (DVB-T part only) Igor M. Liplianin
2008-11-24 7:12 ` Artem Makhutov [this message]
2008-11-24 8:24 ` [linux-dvb] [PATCH] Add missing S2 caps flag to S2API BOUWSMA Barry
2008-11-24 9:06 ` Klaus Schmidinger
2008-11-24 13:37 ` vdr
2008-11-24 15:12 ` Artem Makhutov
2008-12-22 13:39 ` Thomas Creutz
2008-11-26 21:56 ` Udo Richter
2008-11-27 7:13 ` Alex Betis
2008-11-27 12:35 ` Artem Makhutov
2008-11-27 14:08 ` VDR User
2008-11-27 15:21 ` Andy Walls
2008-11-27 17:19 ` VDR User
2008-11-27 19:20 ` CityK
2008-11-28 2:34 ` hermann pitton
2008-11-28 7:58 ` VDR User
2008-11-28 2:05 ` hermann pitton
2008-11-28 2:10 ` Andy Walls
2008-11-27 19:29 ` Igor M. Liplianin
2008-12-22 16:33 ` Udo Richter
2008-12-25 9:44 ` Helmut Auer
[not found] ` <1230219306.2336.25.camel@pc10.localdom.local>
2008-12-31 11:13 ` Mauro Carvalho Chehab
[not found] ` <495B5CE6.9010902@cadsoft.de>
2008-12-31 12:50 ` Mauro Carvalho Chehab
[not found] ` <495B6C25.9010307@cadsoft.de>
2008-12-31 17:28 ` Mauro Carvalho Chehab
2008-12-31 13:45 ` Gregoire Favre
2008-12-18 15:48 ` Steven Toth
-- strict thread matches above, loose matches on Subject: below --
2008-11-24 15:55 Niels Wagenaar
2008-11-24 15:59 ` VDR User
2008-11-24 16:25 ` Klaus Schmidinger
2008-11-24 19:33 ` Manu Abraham
2008-11-25 8:35 ` Klaus Schmidinger
2008-11-24 16:14 Niels Wagenaar
2008-11-24 16:26 ` Klaus Schmidinger
2008-11-24 16:50 ` VDR User
2008-11-25 8:46 Niels Wagenaar
2008-11-25 9:05 ` Klaus Schmidinger
2008-11-25 16:32 ` VDR User
2008-11-25 18:34 ` Morgan Tørvolt
2008-11-25 18:48 ` Alex Betis
2008-11-26 19:45 ` Seppo Ingalsuo
2008-11-26 20:10 ` Christophe Thommeret
2008-11-26 1:44 ` hermann pitton
2008-11-25 9:15 jean-paul
2008-11-25 10:31 ` Manu Abraham
2008-11-25 12:33 ` jean-paul
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=492A53C4.5030509@makhutov.org \
--to=artem@makhutov.org \
--cc=Klaus.Schmidinger@cadsoft.de \
--cc=linux-dvb@linuxtv.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.