From owner-freebsd-multimedia@FreeBSD.ORG Tue Apr 12 20:53:28 2005 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE0E816A4CE for ; Tue, 12 Apr 2005 20:53:28 +0000 (GMT) Received: from email.aon.at (warsl404pip6.highway.telekom.at [195.3.96.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id D889743D55 for ; Tue, 12 Apr 2005 20:53:27 +0000 (GMT) (envelope-from c47g@gmx.at) Received: (qmail 26021 invoked from network); 12 Apr 2005 20:53:24 -0000 Received: from n875p025.adsl.highway.telekom.at (HELO bones) ([62.47.53.89]) (envelope-sender ) by smarthub74.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 12 Apr 2005 20:53:24 -0000 From: Christian Gusenbauer To: freebsd-multimedia@freebsd.org Date: Tue, 12 Apr 2005 22:52:55 +0200 User-Agent: KMail/1.7.2 References: <425C18A2.8010807@elischer.org> <20050412193149.GA15619@puff.jakemsr.gom> <425C2C39.8050607@elischer.org> In-Reply-To: <425C2C39.8050607@elischer.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8309255.KypGZRHRvg"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200504122253.01522.c47g@gmx.at> cc: Julian Elischer Subject: Re: Anyone working on V4L2 for BSD? X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 20:53:28 -0000 --nextPart8309255.KypGZRHRvg Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi! On Tuesday, 12. April 2005 22:14, Julian Elischer wrote: > Jacob Meuser wrote: > >I'd much rather see the problems fixed than a shim added to it. > >how about working about multiple frame buffers? that's probably need > >for many V4L2 programs. IMO, it would be better (maybe even easier) > >to rewrite bktr with a V4L2 interface than to try to add V4L2 to it. > > I wasn't planning on either, but rather making a v4l2 framework to allow > drivers and utilities to hook to each other.. whether the bktr driver > gets rewritten > or shimmed is an orthogonal question :-) Well, that's exactly what I wrote some years ago. There's on one hand the v= 4l2=20 framework and on the other hand there's a driver (in my case, it's a bktr=20 one) which registers itself at the v4l2 framework. Then, the latter creates= =20 the device nodes and the applications use these nodes to get in contact wit= h=20 the driver. Julian, I think that's what you are looking for, isn't it? Ciao, Christian. --nextPart8309255.KypGZRHRvg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCXDUt73Wh/GTgh8wRAt6SAKDAWYKbfSajT/uMys8xo21igKwKTACfYUOR jTqcNml4ybWg+qkg8DEK1mw= =v4sO -----END PGP SIGNATURE----- --nextPart8309255.KypGZRHRvg--