From owner-freebsd-multimedia  Mon Mar 17 21:24:54 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA03312
          for multimedia-outgoing; Mon, 17 Mar 1997 21:24:54 -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 VAA03290
          for <multimedia@freebsd.org>; Mon, 17 Mar 1997 21:24:50 -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 AAA01636; Tue, 18 Mar 1997 00:24:43 -0500 (EST)
Message-Id: <199703180524.AAA01636@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: <199703180408.UAA06973@rah.star-gate.com> 
In-reply-to: Your message of "Mon, 17 Mar 1997 20:08:00 PST."
             <199703180408.UAA06973@rah.star-gate.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 18 Mar 1997 00:24:43 -0500
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Hi
> 
> You are getting lots of errors on your data streams trying playing with
> your bios for intance your PCI latency timer should be 32.

Hmmm.. I'll give that a try.

> Also Trying disabling shared IRQs

Well, this isn't gonna work.  There are not enough IRQs for this to
work, and shared interrupts are a feature of PCI peripherals.  I really
don't want to have to do this.

Shouldn't the driver check to see if the board is even enabled to generate
interrupts before falling into the service routine?  How about checking
the INT_MASK register at 0x104 to see if we've even enabled interrupts?
I don't seem to see a simple interrupt asserted bit in any of the status
registers, which is too bad.  I guess a mask of the appropriate bits in
the interrupt status register would do it.


louie