From owner-freebsd-hackers@FreeBSD.ORG  Mon Oct  9 23:39:46 2006
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0F7E016A412
	for <freebsd-hackers@freebsd.org>; Mon,  9 Oct 2006 23:39:46 +0000 (UTC)
	(envelope-from jon@porthos.spock.org)
Received: from porthos.spock.org (porthos.spock.org [204.97.176.45])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 954C543DBA
	for <freebsd-hackers@freebsd.org>; Mon,  9 Oct 2006 23:39:04 +0000 (GMT)
	(envelope-from jon@porthos.spock.org)
Received: from porthos.spock.org (localhost [127.0.0.1])
	by porthos.spock.org  with ESMTP serial EF600Q3T-B7F;
	Mon, 9 Oct 2006 19:39:03 -0400 (EDT)
	(envelope-from jon@porthos.spock.org)
Received: (from jon@localhost)
	by porthos.spock.org (8.13.8/8.13.6/Submit) id k99Nd3CW025771;
	Mon, 9 Oct 2006 19:39:03 -0400 (EDT) (envelope-from jon)
Date: Mon, 9 Oct 2006 19:39:03 -0400
From: Jonathan Chen <jon@freebsd.org>
To: freebsd-hackers@freebsd.org
Message-ID: <20061009233903.GB20969@porthos.spock.org>
References: <20061009213733.GC15088@porthos.spock.org>
	<20061009232649.GT793@funkthat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20061009232649.GT793@funkthat.com>
User-Agent: Mutt/1.5.12-2006-07-14
X-Scanned-By: MIMEDefang 2.56 on 204.97.176.45
Cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Subject: Re: bktr(4) risk?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Oct 2006 23:39:46 -0000

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