From: Udo Richter <udo_richter@gmx.de>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] Add missing S2 caps flag to S2API
Date: Mon, 22 Dec 2008 17:33:32 +0100 [thread overview]
Message-ID: <494FC15C.6020400@gmx.de> (raw)
In-Reply-To: <492DC5F5.3060501@gmx.de>
On 26.11.2008 22:56, Udo Richter wrote:
> What does a DVB app need to know? A DVB app probably just needs to know
> "What devices are capable of tuning to channel XYZ?". The API could
> answer this the same way as it would tune to channel XYZ, just without
> actually doing it. Try-before-you-buy.
After some insights to S2API interface, this looks even better to me:
properties.num = 1;
properties.props[0].cmd = DTV_DELIVERY_SYSTEM;
properties.props[0].u.data = SYS_DVBS2;
if (ioctl(d, FE_CAP_SET_PROPERTY, &properties) >= 0) {
// has S2 capability
}
A generic frontend test function that delivers the necessary S2
capability information, and many other capabilities too. And there are a
lot more delivery systems that seem to be hard to detect, so a query
function 'can do SYS_XXXX' seems necessary anyway.
Cheers,
Udo
_______________________________________________
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-12-22 16:34 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 ` [linux-dvb] [PATCH] Add missing S2 caps flag to S2API Artem Makhutov
2008-11-24 8:24 ` 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 [this message]
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=494FC15C.6020400@gmx.de \
--to=udo_richter@gmx.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.