From owner-freebsd-multimedia  Sat Apr 18 16:43:00 1998
Return-Path: <owner-freebsd-multimedia@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA28461
          for freebsd-multimedia-outgoing; Sat, 18 Apr 1998 16:43:00 -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 XAA28456
          for <freebsd-multimedia@FreeBSD.ORG>; Sat, 18 Apr 1998 23:42:58 GMT
          (envelope-from rhh@ct.picker.com)
Received: from ct.picker.com by whqvax.picker.com with SMTP;
          Sat, 18 Apr 1998 19:41:53 -0400 (EDT)
Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1)
	id AA18895; Sat, 18 Apr 98 19:41:53 EDT
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id TAA04694; Sat, 18 Apr 1998 19:41:14 -0400
Message-Id: <19980418194114.B4622@ct.picker.com>
Date: Sat, 18 Apr 1998 19:41:14 -0400
From: Randall Hopper <rhh@ct.picker.com>
To: Alex Nash <nash@mcs.net>
Cc: freebsd-multimedia@FreeBSD.ORG
Subject: Re: Bt848: no IRQ
Mail-Followup-To: Alex Nash <nash@mcs.net>, freebsd-multimedia@FreeBSD.ORG
References: <19980418140222.B3440@ct.picker.com> <199804182334.SAA04345@nash.pr.mcs.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199804182334.SAA04345@nash.pr.mcs.net>; from Alex Nash on Sat, Apr 18, 1998 at 06:34:42PM -0500
Sender: owner-freebsd-multimedia@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Alex Nash:
 |>  |not being sent by the bt848 interrupt handler, and that furthermore,
 |>  |the interrupt handler isn't ever being called itself.
 |> ...
 |> 
 |> Hmm.  Wonder if anyone else is having trouble with their FR1236 WinTV cards
 |> with the latest driver/-current?  
 |> 
 |> Many could be and would never know, if they're running XFree86, since DGA
 |> mode doesn't require interrupts to work.
 |
 |ACK.  Do you remember the last time you saw the driver working with
 |XImages?  I can try and dig up the old driver to test this theory out.

Ok, and I'll fetch the latest from the current tree and give them a shot
here in another window.  Together with your test with an older version,
that should help confirm or rule out the driver changes as the culprit for
this interrupt problem.

I'll get back to ya.

Randall

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-multimedia" in the body of the message