From owner-freebsd-multimedia  Sat Feb 22 14:06:50 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA22240
          for multimedia-outgoing; Sat, 22 Feb 1997 14:06:50 -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 OAA22229
          for <multimedia@FreeBSD.org>; Sat, 22 Feb 1997 14:06:46 -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 OAA09711; Sat, 22 Feb 1997 14:06:46 -0800 (PST)
Message-Id: <199702222206.OAA09711@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Randall Hopper <rhh@ct.picker.com>
cc: multimedia@FreeBSD.org
Subject: Re: New BT848 driver 0.2 
In-reply-to: Your message of "Sat, 22 Feb 1997 16:44:18 EST."
             <19970222164418.44306@ct.picker.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 22 Feb 1997 14:06:46 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-multimedia@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk


Good info!

I will concentrate on the CAP_CONTINOUS functionality.

A cursory analysis of the interrupt status info that you send us seems to
indicate that you are getting excessive PCI errors.

Memory mapped location 0x100 (BKTR_INT_STAT) :
bit 15  Set when a parity error is detected while the initiator is 
        reading RISC instructions.


Here is a sample output from my P100:
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000206 30701c 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000a04 3077a4 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000a04 3077a4 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 c000206 30601c 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 c000206 30601c 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 c000a04 3067a4 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 c000a04 3067a4 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000206 30701c 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000206 30701c 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000a04 3077a4 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000a04 3077a4 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 c000206 30601c 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 c000206 30601c 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 c000a04 3067a4 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 c000a04 3067a4 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000206 30701c 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000206 30701c 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000a04 3077a4 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 d000a04 3077a4 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 c000206 30601c 
Feb 22 05:51:20 cioloco /kernel:  STATUS 0 c000206 30601c 
                                           ^^^^^^^  BKTR_INT_STAT
BKTR_INT_STAT is the second value in the output as you can see 
bit 15 is never set which means that the Bt848 is not having
problems accessing the host memory.



>From The Desk Of Randall Hopper :
> Amancio Hasty:
>  |Has the driver been always this unstable with you or is it just this
>  |version?
> 
> I got some freezes with 0.1, but they were pretty sporatic.  With 0.2, I
> can get regular freezes when 1) doing CAP_CONTINOUS and 2) DMAing straight
> to the video card.  Disk I/O brings the lock-ups on sooner.  But with 0.2,
> if I flip into CAP_SINGLE, the regular freezes go away.
> 
> Randall
> 
> 
>