From owner-freebsd-multimedia Sun Apr 19 11:10:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06396 for freebsd-multimedia-outgoing; Sun, 19 Apr 1998 11:10:30 -0700 (PDT) (envelope-from owner-freebsd-multimedia@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA06347 for ; Sun, 19 Apr 1998 18:10:12 GMT (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sun, 19 Apr 1998 14:07:23 -0400 (EDT) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA08143; Sun, 19 Apr 98 14:07:22 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id OAA07584; Sun, 19 Apr 1998 14:06:39 -0400 Message-Id: <19980419140638.A7467@ct.picker.com> Date: Sun, 19 Apr 1998 14:06:38 -0400 From: Randall Hopper To: Luigi Rizzo , Jeremy Porter , Alex Nash Cc: multimedia@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: problem capturing video with BT848/Hauppauge Win/Tv Mail-Followup-To: Luigi Rizzo , Jeremy Porter , Alex Nash , multimedia@FreeBSD.ORG, hasty@rah.star-gate.com References: <199804191716.MAA01812@freeside.fc.net> <199804191550.RAA12180@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199804191550.RAA12180@labinfo.iet.unipi.it>; from Luigi Rizzo on Sun, Apr 19, 1998 at 05:50:10PM +0200 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luigi Rizzo: |Randall Hopper: |> >I suspect this is the "Bt848 driver isn't issuing frame completion |> >signals" problem that I'm helping Alex Nash with now. |> >Look in your -multimedia list mail for the thread labeled: "Re: Bt848: |> >no IRQ". | |I have been having the same problem for a long time, both on a |P5-133 and on a PPro200. I nailed down the problem to some too |restrictive test for errors on the status register of the brooktree |when it gets an interrupt. Hmmm. Pretty strange. This appears it might be hardware or system-configuration related to some extent. If it's a driver issue, it's likely in hardware-specific portions of the driver. I say this because I pulled the latest driver last night and had no problem with it (except for that 2 second tsleep in open() 8^). Never had any problems on any previous version either. It's unlikely its FreeBSD version-related. As I recall, you run 2.2.*. Jeremy's running 2.2.2. Alex is running 3.0-current. I'm running 3.0-971208-SNAP, and used to run 2.2.1. I don't think I've ever seen this no-signal problem on any driver version on either FreeBSD version, but all you guys are seeing it now. Sounds like it might be time to uncomment this printf in the driver: /* printf( " STATUS %x %x %x \n", dstatus, bktr_status, bt848->risc_count ); */ and see what everyone's seeing. Randall MY CONFIG: ASUS P55T2P4, Hauppauge Wincast/TVdbx (1yr old) FreeBSD 3.0-971208-SNAP, non-SMP, Fxtv 0.46, latest driver bktr0: rev 0x11 int a irq 9 on pci0.11.0 Hauppauge WinCast/TV, Philips NTSC tuner, dbx stereo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message