From owner-freebsd-multimedia  Tue Mar 18 10:23:12 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA15766
          for multimedia-outgoing; Tue, 18 Mar 1997 10:23:12 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA15757
          for <multimedia@freebsd.org>; Tue, 18 Mar 1997 10:23:09 -0800 (PST)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id KAA14137; Tue, 18 Mar 1997 10:23:06 -0800 (PST)
Message-Id: <199703181823.KAA14137@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: "Louis A. Mamakos" <louie@TransSys.COM>
cc: Steve Passe <smp@csn.net>, multimedia@freebsd.org
Subject: Re: latest bt848 code 
In-reply-to: Your message of "Tue, 18 Mar 1997 09:16:20 EST."
             <199703181416.JAA04347@whizzo.transsys.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 18 Mar 1997 10:23:06 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi Louis,

Tnks for the info. I will leave dtv running for extended period of 
time to see if I can duplicate what you are seeing. 

Also this weekend I will look into the problem with contrast, color
saturation values being forgotten by the driver.

	Regards,
	Amancio

>From The Desk Of "Louis A. Mamakos" :
> > Is probably more to do with the PCI code than the driver. What I am
> > doing is pretty harmless in attach. Besides, the interrupts are 
> > disabled. I would suspect more the 2940... I got one over here
> > and it has given me grief in the past.
> 
> I don't know how to explain it.  On my system, the disk controller doesn't
> even share the same interrupt, and it's very unlikely that the ethernet
> controller was generating 60 interrupts per seconds.  The video card shares
> the same interrupt, but I believe it's vertical refresh rate is 68 or 72 Hz.
> 
> Anyway, I left it running last night, and the system stayed up.  The capture
> stopped somewhere along the way, but started back up again right away when
> the window got tweaked.
> 
> One that that I have noticed is that the state of brightness, contrast, etc,
> seems to be lost whenever the frame capture starts up again after an expose,
> resize, etc.
> 
> I'll leave it running today while I'm at work, and see what happens...
> 
> louie
> 
>