From owner-freebsd-multimedia@FreeBSD.ORG Mon Oct 16 07:31:39 2006 Return-Path: X-Original-To: freebsd-multimedia@freebsd.org Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4902816A40F for ; Mon, 16 Oct 2006 07:31:39 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB4F543D55 for ; Mon, 16 Oct 2006 07:31:38 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (0sti49yw034bx650@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k9G7VRbG033656; Mon, 16 Oct 2006 00:31:27 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k9G7VPas033655; Mon, 16 Oct 2006 00:31:25 -0700 (PDT) (envelope-from jmg) Date: Mon, 16 Oct 2006 00:31:25 -0700 From: John-Mark Gurney To: usleepless@gmail.com Message-ID: <20061016073124.GD23971@funkthat.com> Mail-Followup-To: usleepless@gmail.com, rick-freebsd@kiwi-computer.com, freebsd-multimedia@freebsd.org, B Briggs References: <45317970.5000508@bellsouth.net> <20061015064102.8780.qmail@web30310.mail.mud.yahoo.com> <20061016015911.GC57865@keira.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-multimedia@freebsd.org, B Briggs , rick-freebsd@kiwi-computer.com Subject: Re: New port: pvrxxx for Hauppauge PVR150/500 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2006 07:31:39 -0000 usleepless@gmail.com wrote this message on Mon, Oct 16, 2006 at 08:40 +0200: > On 10/16/06, Rick C. Petty wrote: > >I think it's timing-critical, although an I2C bus has clock and data lines, > >so I can't see any reason the kernel needs to block during the download. > >Feel free (anyone) to look into the iic code and pull it out from under > >GIANT. > > will that help? reason i ask is because with the i2c, the cpu is > responsible for every bit-switch/line-switch in the protocol. so > through the pci-interface, it tells the card to pull the line up, you > wait a very short time, and tell it to pull the i2c-line down. etc... It depends upon the interface... Some things like the bktr have the ability to drive the i2c bus in hardware.. only if you use the iicbb (iic bit bang) driver, does the software do all the work... (though it appears that bktr uses iicbb instead of the hardware).. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."