Date: Tue, 10 Oct 2006 10:10:28 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: freebsd-hackers@freebsd.org, John-Mark Gurney <gurney_j@resnet.uoregon.edu> Cc: Jonathan Chen <jon@freebsd.org> Subject: Re: bktr(4) risk? Message-ID: <200610101010.29188.doconnor@gsoft.com.au> In-Reply-To: <20061009232649.GT793@funkthat.com> References: <20061009213733.GC15088@porthos.spock.org> <20061009232649.GT793@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Tuesday 10 October 2006 08:56, John-Mark Gurney wrote: > > The only reason I can think of to use this ioctl would be if you wanted > > the image you're capturing to be directly dumped into video memory. This > > This is very common... It allows the bktr driver to dump the frames > directly to the memory of your video card... This makes watching live > tv watchable... Maybe it could be restricted to the root user. In any case it's more efficient to read YUV data and then use Xv.. It certainly spams the PCI bus way less, unfortunately you do become acceptable to load related frame drops. It would be really nice if you could connect bktr to your video card more directly (instead of cap. card -> bktr -> TV app -> X server -> video card) but in practice it seems to work fine. mplayer can do this, and I have a trivial app which also does it (I wrote it before mplayer grew support for bktr) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFKuv95ZPcIHs/zowRAjwSAJ0a3sjVUE9mDOYmRel4e1OkbpUaRgCfZQxd A3MYB3PQ37+Xrj1cmcKR0gY= =W650 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610101010.29188.doconnor>