From owner-freebsd-multimedia Sun Feb 23 18:36:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA19783 for multimedia-outgoing; Sun, 23 Feb 1997 18:36:25 -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 SAA19775 for ; Sun, 23 Feb 1997 18:36:22 -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 SAA00859; Sun, 23 Feb 1997 18:36:20 -0800 (PST) Message-Id: <199702240236.SAA00859@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Randall Hopper cc: multimedia@FreeBSD.org Subject: Re: New BT848 driver 0.2 In-reply-to: Your message of "Sun, 23 Feb 1997 21:21:07 EST." <19970223212107.37259@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Feb 1997 18:36:20 -0800 From: Amancio Hasty Sender: owner-multimedia@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Sorry about that .. I counted wrong. > STATUS 0 dd000206 2b901c > STATUS 0 dd000a04 2b9f24 The suspect in your case is ^^^^^^^ That value should be current PC address of the risc program which the Bt848 is executing. That value seems too low . To verify that indeed is the correct value. In get_bktr_mem , print the value returned by vm_page_alloc_contig. So before the "return addr", add this: printf("get_bktr_mem %s \n", addr); Tnks, Amancio >From The Desk Of Randall Hopper : > Amancio Hasty: > |A cursory analysis of the interrupt status info that you send us seems to > |indicate that you are getting excessive PCI errors. > ... > |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 > ... > | ^^^^^^^ 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. > > A piece of my output: > STATUS 0 dc000206 100001c > STATUS 0 dc000a04 1000f24 > STATUS 0 dd000206 2b901c > STATUS 0 dd000a04 2b9f24 > > > Bit 15? Are some bytes swapped in the port mapping? It looks to my like > your low-order word (bits 15->0) is the same as mine. The differences look > like your bits 28,30, and 31 which are in the RISCS field. > > I guess I might be missing something. > > Randall >