From owner-freebsd-current  Tue Aug 22 13:03:46 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id NAA14347
          for current-outgoing; Tue, 22 Aug 1995 13:03:46 -0700
Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.35.13])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id NAA14341
          for <current@freebsd.org>; Tue, 22 Aug 1995 13:03:45 -0700
Received: (from james@localhost) by miller.cs.uwm.edu (8.6.10/8.6.10) id PAA26113; Tue, 22 Aug 1995 15:03:43 -0500
Date: Tue, 22 Aug 1995 15:03:43 -0500
From: Jim Lowe <james@miller.cs.uwm.edu>
Message-Id: <199508222003.PAA26113@miller.cs.uwm.edu>
To: rgrimes@gndrsh.aac.dev.com, se@ZPR.Uni-Koeln.DE
Subject: Re: Matrox Meteor Video Capture Card Driver
Cc: current@freebsd.org, tinguely@plains.nodak.edu
Sender: current-owner@freebsd.org
Precedence: bulk

> > Since I'm currently maintaining the PCI and NCR code,
> > we might try to get the Matrox Meteor supported on 
> > more motherboards ...
> 
> I doubt you are going to fix the ``hardware'' bugs in the Mercury
> chipset that causes the problems with boards like the Meteor.

I just tried the meteor card in an ASUS triton box with the NCR controller in
it.  The machine locked up on large frame transfers.  It seemed to work
just fine as long as I kept the PCI data transfer down with small frame
sizes.  If I remove the NCR controller and use a different one, the
machine works just fine.

For some reason, the NCR seems to lock up when the PCI bus gets real
busy.  I am not sure why.

	-Jim