From owner-freebsd-multimedia Tue Mar 18 13:35:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA01692 for multimedia-outgoing; Tue, 18 Mar 1997 13:35:55 -0800 (PST) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA01632 for ; Tue, 18 Mar 1997 13:35:26 -0800 (PST) Received: from ct.picker.com by whqvax.picker.com with SMTP; Tue, 18 Mar 1997 16:34:36 -0500 (EST) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA20090; Tue, 18 Mar 97 16:34:34 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id QAA16928; Tue, 18 Mar 1997 16:31:53 -0500 Message-Id: <19970318163153.31441@ct.picker.com> Date: Tue, 18 Mar 1997 16:31:53 -0500 From: Randall Hopper To: Steve Passe Cc: multimedia@freebsd.org Subject: Re: latest bt848 code References: <19970318140646.02069@ct.picker.com> <199703182125.OAA18595@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.65 In-Reply-To: <199703182125.OAA18595@Ilsa.StevesCafe.com>; from Steve Passe on Tue, Mar 18, 1997 at 02:25:29PM -0700 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id NAA01675 Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Steve Passe: |I have identified the basic problem as being that fxtv closes the device |and then re-opens it every time the window is moved!. If you happen |to have it open with another client (such as xtvr) at the time you move |the window nothing bad happens, as the open routine ends early. But if |no other clients are active the close completes, and the open reinitializes |the hardware. this is where all the tuner values are lost. so the question |why the close/open calls for every re-draw? (i merely put printf()s in the |driver in both open and close to show this behaviour, am about to go look at |the fxtv source) Back before the driver-hang bug-fix, I close/open-cycled the driver for each capture stop to try and reduce the frequency of the lock-ups. It seemed like it helped some. However, I ripped that hack out last weekend when the bug was fixed so the last-close-cleanup behavior you describe won't kick-in anymore. I'll do some tests later to verify that brightness/contrast/etc. do in fact keep their values across stops/starts when the driver handle is held open. Thanks for looking into it. Randy