Date: Tue, 15 Jul 2003 22:45:56 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: John-Mark Gurney <gurney_j@efn.org> Cc: multimedia@freebsd.org Subject: Re: Looking at darwin? (was: Re: BSD video capture emulation question) Message-ID: <20030715223802.C21327@carver.gumbysoft.com> In-Reply-To: <20030715215454.GL35337@funkthat.com> References: <20030714064137.GT35337@funkthat.com> <20030715075307.GD17691@cobweb.example.org> <200307151502.14625.mupi@mknet.org> <20030715215454.GL35337@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 15 Jul 2003, John-Mark Gurney wrote: > > This description does sound pretty much like what I've seen discussed here, > > except that the discussion here has focussed specifically on Video drivers, > > not "all" IO devices (and note that not necessarily all devices have (or > > need) userland access) > > Too many people are thinking physical instead of logical. We already > have the physical side of things, the driver talking to the hardware to > control it. What we don't have is the logical glue to glue the parts of > the driver together into one easy piece. This is what the code I would > like to see do. That stuff is in QuickTime, which Apple cannot and will not ever release code to, as good chunks of it are licensed from third parties, and its the crown jewels :) QT takes care of repackaging the device driver outputs and inputs into APIs that programs hook. Your average Mac webcam app just looks at the list of available QuickTime video capture devices; it doesn't care if its USB or FireWire or whatnot. The audio system does the same thing; this way all audio capture devices look the same, even if its the onboard sound or USB, or a program masquerading as an input device. On the other hand, the QuickTime APIs are published. You could use those as a starting point. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715223802.C21327>