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 1LBbQK-0003MT-Dx for linux-dvb@linuxtv.org; Sat, 13 Dec 2008 21:49:16 +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 mBDC9gob010929 for ; Sat, 13 Dec 2008 13:09:42 +0100 Message-ID: <4943A606.5060502@cadsoft.de> Date: Sat, 13 Dec 2008 13:09:42 +0100 From: Klaus Schmidinger MIME-Version: 1.0 To: linux-dvb@linuxtv.org Subject: [linux-dvb] DiSEqC handling 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: While adapting VDR to the S2API driver, I saw that there are also facilities to handle DiSEqC via the new API, like DTV_VOLTAGE and DTV_TONE. However, I can't seem to find out how the "legacy" FE_DISEQC_SEND_BURST and FE_DISEQC_SEND_MASTER_CMD could be handled with S2API. Is this not implemented? Klaus _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb