Date: Mon, 9 Oct 2006 19:39:03 -0400 From: Jonathan Chen <jon@freebsd.org> To: freebsd-hackers@freebsd.org Cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu> Subject: Re: bktr(4) risk? Message-ID: <20061009233903.GB20969@porthos.spock.org> 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
On Mon, Oct 09, 2006 at 04:26:50PM -0700, John-Mark Gurney wrote: > Jonathan Chen wrote this message on Mon, Oct 09, 2006 at 17:37 -0400: > > 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... Yes, how stupid of me to not think of people wanting to just watch a live feed from their capture card... > > doesn't seem too useful a task for a video capture card to be doing. > > Perhaps we should put a test for write access in there or just eliminate > > the ioctl altogether. It should be noted that the meteor driver had this > > ioctl ifdef'ed out prior to its removal. > > Hmmm... I think I'll go ahead and put in a compatibility ioctl based > on the way I did the zoran driver, and schedule the removal of the > ioctl.. Zoran driver? Can I have a pointer or a summary of what you did there so I can do the same to meteor(4)? -Jon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061009233903.GB20969>