public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] How to determine DVB-S2 capability in S2API?
Date: Sun, 23 Nov 2008 11:59:09 +0100	[thread overview]
Message-ID: <4929377D.7070702@cadsoft.de> (raw)
In-Reply-To: <200811221837.58098.hftom@free.fr>

On 22.11.2008 18:37, Christophe Thommeret wrote:
> Le samedi 22 novembre 2008 16:43:07 Klaus Schmidinger, vous avez écrit :
>> I'm currently adopting the patch that makes VDR use S2API,
>> but I can't figure out how an application is supposed to find out
>> whether a DVB device is DVB-S or DVB-S2.
> 
> This bit is missing in current api.
> Will be added soon, i guess asa someone provides a patch :)
> A that time, i solve that with a user toggleable "S2 capable device" ui 
> option.

Considering that the "multiproto" API did think of handling this,
I really don't understand why the "technologically superior" *S2*API
didn't even think of this.

Requiring the user to configure this is a workaround that even
more disqualifies the decision to go S2API.

But anyway, it looks like we're stuck with this inferior API, so
I've posted a patch that adds this capability. Let's hope it gets
adopted - VDR 1.7.2 will require it, anyway.

Klaus

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-11-23 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22 15:43 [linux-dvb] How to determine DVB-S2 capability in S2API? Klaus Schmidinger
2008-11-22 17:37 ` Christophe Thommeret
2008-11-23 10:59   ` Klaus Schmidinger [this message]
2008-11-23  9:11 ` Michel Verbraak
2008-11-23 12:04   ` Andreas Oberritter

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=4929377D.7070702@cadsoft.de \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox