From patchwork Sat Nov 27 15:59:12 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Andreas Brachold X-Patchwork-Id: 12844 Received: from mail.tu-berlin.de ([130.149.7.33]) by www.linuxtv.org with esmtp (Exim 4.69) (envelope-from ) id 1PMNBC-0000Hk-Oh for vdr@linuxtv.org; Sat, 27 Nov 2010 16:59:15 +0100 X-tubIT-Incoming-IP: 212.91.253.234 Received: from web3.dns-net.de ([212.91.253.234]) by mail.tu-berlin.de (exim-4.69/mailfrontend-d) with esmtps [TLSv1:AES256-SHA:256] for id 1PMNBC-0005gN-1a; Sat, 27 Nov 2010 16:59:14 +0100 Received: from ion.localnet (p5DCE537C.dip.t-dialin.net [93.206.83.124]) (authenticated bits=0) by web3.dns-net.de (8.13.1/8.13.1) with ESMTP id oARFxDdN003830 for ; Sat, 27 Nov 2010 16:59:13 +0100 Received: from pluto.localnet ([192.168.0.50]) by ion.localnet with esmtp (Exim 4.72) (envelope-from ) id 1PMNBB-0003bq-F5 for vdr@linuxtv.org; Sat, 27 Nov 2010 16:59:13 +0100 From: Andreas Brachold To: vdr@linuxtv.org Date: Sat, 27 Nov 2010 16:59:12 +0100 Message-ID: <1290873552.18375.21.camel@pluto> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2010.11.27.155115 X-PMX-Spam: Gauge=IIIIIIII, Probability=8%, Report=' MIME_TEXT_ONLY_MP_MIXED 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1800_1899 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, INVALID_MSGID_NO_FQDN 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_MIXED 0, __HAS_BLIZZARD_RCVD 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0' X-LSpam-Score: -3.6 (---) X-LSpam-Report: No, score=-3.6 required=5.0 tests=BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1 autolearn=ham Subject: [vdr] VDR-1.7.16 doesn't respect valid dvb device frequency ranges X-BeenThere: vdr@linuxtv.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: VDR Mailing List List-Id: VDR Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2010 15:59:15 -0000 Status: O X-Status: X-Keywords: X-UID: 23906 Hello, Any current vdr doesn't respect valid dvb device frequency ranges. Here on a EPG-Scan it's generate many messages on syslog, like : DVB: adapter 0 frontend 0 frequency 177500000 out of range (470000000..860000000) DVB: adapter 0 frontend 0 frequency 177500000 out of range (470000000..860000000) DVB: adapter 0 frontend 0 frequency 177500000 out of range (470000000..860000000) Any of my three DVB-T devices have different frequency ranges, and the primary device can't receive VHF-channels. frontend 0:0 frequency range 470000000..860000000 frontend 1:0 frequency range 51000000..858000000 frontend 2:0 frequency range 177000000..858000000 Therefore i attach a simple patch to check provided frequency ranges of used dvb-t device driver. Andreas --- dvbdevice.c.orig 2010-05-01 11:47:13.000000000 +0200 +++ dvbdevice.c 2010-11-27 16:53:43.000000000 +0100 @@ -911,6 +911,14 @@ { if (!ProvidesSource(Channel->Source())) return false; // doesn't provide source + + // check for supported frequency range + if(frontendType == SYS_DVBT + && (Channel->Frequency() < frontendInfo.frequency_min + || Channel->Frequency() > frontendInfo.frequency_max )) { + return false; + } + cDvbTransponderParameters dtp(Channel->Parameters()); if (dtp.System() == SYS_DVBS2 && frontendType == SYS_DVBS || dtp.Modulation() == QPSK && !(frontendInfo.caps & FE_CAN_QPSK) ||