From owner-freebsd-smp  Tue Dec 17 18:39:02 1996
Return-Path: <owner-smp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id SAA11064
          for smp-outgoing; Tue, 17 Dec 1996 18:39:02 -0800 (PST)
Received: from cs.utah.edu (cs.utah.edu [128.110.4.21])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA11051
          for <freebsd-smp@freebsd.org>; Tue, 17 Dec 1996 18:38:58 -0800 (PST)
Received: from fast.cs.utah.edu by cs.utah.edu (8.8.4/utah-2.21-cs)
	id TAA22836; Tue, 17 Dec 1996 19:38:50 -0700 (MST)
Received: by fast.cs.utah.edu (8.6.10/utah-2.15-leaf)
	id TAA00379; Tue, 17 Dec 1996 19:38:49 -0700
Date: Tue, 17 Dec 1996 19:38:49 -0700
From: vanmaren@fast.cs.utah.edu (Kevin Van Maren)
Message-Id: <199612180238.TAA00379@fast.cs.utah.edu>
To: freebsd-smp@freebsd.org, smp@ilsa.systemsix.com
Subject: Re: AMI Merlin DP Motherboard
Sender: owner-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>Do these motherboards cause the same problems with other (Sun, SCO) SMP
>>implementations?

>The issue is "Intel MP spec motherboards".  this means among other things
>ONLY Intel CPU's (P5/P6).  In otherwords its strictly a hardware issue, NOT
>an OS issue.

I think the question was does Solaris for the x86 have problems
with EISA motherboards.  I know NT works fine; I assume
Solaris does as well.