From owner-freebsd-multimedia Thu Apr 15 19:51: 2 1999 Delivered-To: freebsd-multimedia@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 3918414DE9 for ; Thu, 15 Apr 1999 19:50:59 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ts9-75-ppp.ipass.net [208.209.104.75]) by pluto.ipass.net (8.9.1a/8.9.1) with ESMTP id WAA14929; Thu, 15 Apr 1999 22:48:33 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.1/8.8.8) id WAA26138; Thu, 15 Apr 1999 22:48:48 -0400 (EDT) (envelope-from rhh) Date: Thu, 15 Apr 1999 22:48:48 -0400 From: Randall Hopper To: Scott Donovan Cc: multimedia@freebsd.org Subject: Re: BT848/winTV/Teletext/video4linux etc. Message-ID: <19990415224848.B22102@ipass.net> References: <3.0.5.32.19990414123641.02548550@nico.telstra.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <3.0.5.32.19990414123641.02548550@nico.telstra.net>; from Scott Donovan on Wed, Apr 14, 1999 at 12:36:41PM +1000 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org |1. Does anyone know of a teletext program that works with the bt848 driver ? Hmm. Seems like Luigi wrote one of these. We had a discussion back in March 98 on if/how to use teletext info for channel/program info. You might drop him some mail (Luigi Rizzo ), though he'll probably catch your post now that it's on -multimedia. |2. Given that it is likely there may be other chipset drivers for FreeBSD |has anyone thought of pulling together a standard API etc (ala video4linux). I'm sure a number of folks have, but I think we only have support for two now (is the meteor still supported?). So the desire never really reached critical mass. The driver folks (Amancio, Roger, et. all) have worked toward standarization in the driver interface, but a higher-level library interface would be useful to hide the nuts-and-bolts and make it easier to cook TV/capture apps. Maybe we should start tossing around ideas for a template API (?) |4. Given that the latest bt848 driver appears to have the appropriate |defines to cope with the wintv IR remote, will that support be included in |fxtv? I don't know anything about this functionality. Does the driver now pass back keys from the remote, or how does this work exactly? |5. Can a "Frequency Set" be included for australia (to add to nabcst etc) |to the existing bt848 distribution (saves me patching each time I get the |latest driver)? Sounds like a good idea. You might want to drop Roger Hardiman some mail (roger@cs.strath.ac.uk) and send him your Australian freq set patch. (This is another area where that C lib layer would be useful. We shouldn't be stuffing frequency sets in the driver/kernel. This belongs in a lib or server interface above the driver below the app.) |6. Could the bt848 frequency set information be dynamically included during |boot time (ala pnp style commands)? The definition itself? I don't believe so. ...but someone will surely speak up if I'm wrong :-) Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message