Date: Sun, 4 Feb 2007 15:30:41 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Luigi Rizzo <rizzo@icir.org> Cc: cvs-ports@FreeBSD.ORG, Luigi Rizzo <luigi@FreeBSD.ORG>, cvs-all@FreeBSD.ORG, ports-committers@FreeBSD.ORG Subject: Re: cvs commit: ports/multimedia/linux-ov511-kmod Makefile distinfo pkg-descr pkg-plist ports/multimedia/linux-ov511-kmod/files Makefile.kld patch-ov511-1 Message-ID: <20070204153040.GC76191@FreeBSD.org> In-Reply-To: <20070204071245.A23186@xorpc.icir.org> References: <200702021825.l12IPRcV076387@repoman.freebsd.org> <20070204150438.GB76191@FreeBSD.org> <20070204071245.A23186@xorpc.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 04, 2007 at 07:12:45AM -0800, Luigi Rizzo wrote: > On Sun, Feb 04, 2007 at 03:04:38PM +0000, Alexey Dokuchaev wrote: > > > > Could you please describe the benefits of using these drivers instead of > > tools like `graphics/spcaview' or `graphics/vid'? > > these (same as multimedia/pwcbsd) are kernel drivers, so they provide > data through /dev/video using the Video4linux api. As such they should > be compatible with apps that use that API to talk to the camers > (e.g. ekiga/gnomemeeting, and hopefully others as time goes). > > Conversely, the other tools you mentions are ad hoc apps that talk > to the cameras through /dev/ugen. They do what they do, but > do nothing to help other apps use the cameras. > > Kernel drivers should also work better than the corresponding > userland apps because there are some time-critical things (such as > grabbing frames from the camera, etc.) where the userland apps have > a hard time because they cannot control well when they will be > scheduled. Thanks for detailed answer! ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070204153040.GC76191>