From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from crow.cadsoft.de ([217.86.189.86] helo=raven.cadsoft.de) by www.linuxtv.org with esmtp (Exim 4.63) (envelope-from ) id 1L3udb-0004ZO-PS for linux-dvb@linuxtv.org; Sat, 22 Nov 2008 16:43:13 +0100 Received: from [192.168.100.10] (hawk.cadsoft.de [192.168.100.10]) by raven.cadsoft.de (8.14.3/8.14.3) with ESMTP id mAMFh7Kc003575 for ; Sat, 22 Nov 2008 16:43:08 +0100 Message-ID: <4928288B.1050306@cadsoft.de> Date: Sat, 22 Nov 2008 16:43:07 +0100 From: Klaus Schmidinger MIME-Version: 1.0 To: linux-dvb@linuxtv.org Subject: [linux-dvb] How to determine DVB-S2 capability in S2API? List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: linux-dvb-bounces@linuxtv.org Errors-To: linux-dvb-bounces+mchehab=infradead.org@linuxtv.org List-ID: 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. Clearly I must be missing something, since S2API is said to be "technically superior" than the "multiproto" API (where, BTW, this was no problem at all ;-). Klaus _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb