From owner-freebsd-hackers  Fri Nov  1 09:38:52 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA03037
          for hackers-outgoing; Fri, 1 Nov 1996 09:38:52 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA02995;
          Fri, 1 Nov 1996 09:38:45 -0800 (PST)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.6/8.7.3) with ESMTP id JAA19083; Fri, 1 Nov 1996 09:38:39 -0800 (PST)
Message-Id: <199611011738.JAA19083@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: hackers@freebsd.org
cc: multimedia@freebsd.org
Subject: Matrox Meteor  and PPRO problem found
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 01 Nov 1996 09:38:39 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Article 106503 (8593 more) in comp.sys.intel:
From: Bob_Cline@ccm.sc.intel.com (Bob Cline)
Subject: Re: Matrox adaptors & 440FX PCIset systems
Date: Fri, 01 Nov 96 08:44:37 PST
Organization: Online Relations
Lines: 16
NNTP-Posting-Host: rcline.sc.intel.com
Mime-Version: 1.0
X-Newsreader: WinVN 0.93.9

>We anticipate making additional data and information available in the
>near future.


Intel and Matrox have jointly confirmed the cause of the recently reported
issue between the Matrox Meteor graphics adapter board and the Intel 440FX
chipset.   The root cause is an illegal PCI signal generated by the PCI
interface chip on the adapter board.  This is not an Intel Pentium(R) Pro
processor or an Intel 440FX chipset issue.

For further information on this issue or Matrox products, please contact
your local Matrox sales representative, Matrox office or Matrox headquarters.

Bob Cline
Intel Corporation

----------

The question now is when is Matrox, OmniMedia or  Philips going to fix
the problem. For that I don't have an answer except to just wait because
I know both Matrox and OmniMedia are working on a solution to the problem.


	Amancio