From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtpauth02.csee.siteprotect.eu ([83.246.86.181]) by www.linuxtv.org with esmtp (Exim 4.63) (envelope-from ) id 1Kbabz-0006hH-Ci for linux-dvb@linuxtv.org; Fri, 05 Sep 2008 14:40:27 +0200 Received: from [192.168.10.241] (unknown [81.168.109.249]) (Authenticated sender: roger@beardandsandals.co.uk) by smtpauth02.csee.siteprotect.eu (Postfix) with ESMTP id 1A196C68028 for ; Fri, 5 Sep 2008 14:39:54 +0200 (CEST) Message-ID: <48C1289D.90607@beardandsandals.co.uk> Date: Fri, 05 Sep 2008 13:39:57 +0100 From: Roger James MIME-Version: 1.0 To: linux-dvb@linuxtv.org Subject: [linux-dvb] Frontends and phase locked loops List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1286492970==" Mime-version: 1.0 Sender: linux-dvb-bounces@linuxtv.org Errors-To: linux-dvb-bounces+mchehab=infradead.org@linuxtv.org List-ID: --===============1286492970== Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I have a question about the dvb api architecture and hardware that has been puzzling me for some time.

I had thought the idea of a phase locked loop was that it locked onto and tracked a frequency compensating for drift in the sending and receiving apparatus. I had also assumed that most frontends would use PLL technology. So why do we need to have a in kernel thread to keep the frontend tuned. I ask this out of curiosity only. I assume that it is something to do with the nature of the dvb signal (is it spread spectrum?).

Roger

--===============1286492970== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb --===============1286492970==--