From owner-freebsd-multimedia Thu Jun 28 0:40:25 2001 Delivered-To: freebsd-multimedia@freebsd.org Received: from beaver.core.de (beaver.core.de [212.44.167.2]) by hub.freebsd.org (Postfix) with ESMTP id DA6F437B409 for ; Thu, 28 Jun 2001 00:40:22 -0700 (PDT) (envelope-from coto@core.de) Received: from beaver.core.de (beaver.core.de [212.44.167.2]) by beaver.core.de (8.11.4/8.11.4) with ESMTP id f5S7eDf07262; Thu, 28 Jun 2001 09:40:13 +0200 (CEST) Date: Thu, 28 Jun 2001 09:40:12 +0200 (CEST) From: Thomas Runge To: Randall Hopper Cc: Subject: Re: Watching TV In-Reply-To: <20010627183454.A74330@nc.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 27 Jun 2001, Randall Hopper wrote: > others to improve upon later. It sets all the channels one-by-one and > prints the return of the TVTUNER_GETSTATUS to the console. However, it > doesn't work at all for me here in the US (all channels, there or not, > print the same values). > > I haven't played with this enough to know if that's the right way to do it, > or if the appropriate chip functionality is even exported through the > driver API. Xmradio uses the GETSTATUS ioctl to detect the signal strength. Unfortunately, the tuner chip has only 3 bits for that, so all you get is a value between 0 and 7 and it looks, as if it is even worse. You can't really depend on the reported values, but it's better then nothing. Funny thing is, that the windows radio shows values between 0 and 255, cheating a little bit ;) (With a Hauppauge WinTV/radio) > If anyone is interested in working with it, let me know and I'll mail you a > snapshot. Oh, please do. I'll have some time this weekend to look into it. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message