From owner-freebsd-multimedia  Mon Mar 17 22:16:08 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA06374
          for multimedia-outgoing; Mon, 17 Mar 1997 22:16:08 -0800 (PST)
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA06369
          for <multimedia@FreeBSD.ORG>; Mon, 17 Mar 1997 22:16:04 -0800 (PST)
Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.5/8.7.3) with SMTP id BAA00471; Tue, 18 Mar 1997 01:15:57 -0500 (EST)
Message-Id: <199703180615.BAA00471@whizzo.transsys.com>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Amancio Hasty <hasty@rah.star-gate.com>
cc: multimedia@FreeBSD.ORG
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: latest bt848 code 
References: <199703180543.VAA07396@rah.star-gate.com> 
In-reply-to: Your message of "Mon, 17 Mar 1997 21:43:43 PST."
             <199703180543.VAA07396@rah.star-gate.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 18 Mar 1997 01:15:57 -0500
Sender: owner-multimedia@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


I've rebooted the system with the PCI bus latency timer set to 32, and
it seems to be running pretty well so far.  I also added a change to
short-circuit the interrupt service routine in the driver when interrupts
are masked, but that shouldn't affect anything when the bt848 board is
open - only when it's not in use, and that's not been a problem.

So, I guess the bus latency timer may be the cause of the problems I've
had - I'll know more after it's been running for a while.

FYI, I noticed that with the driver open and doing a continuous capture
with fxtv, it's generating 120 interrupts per second.  In the "tv in a window"
case, where the user doesn't need to be notified, it would be nice not to
suffer the interrupt overhead.  I don't know if that's possible or not - I
need to dig in deeper to understand how the driver fits together to see if
that's reasonable.

Foo, I missed seeing Letterman tonight fiddling around with this.  Now that
it seems to be working, that won't be a problem any more.  Just tune in the
show from a cron job :-)

louie