From owner-freebsd-stable@FreeBSD.ORG  Tue Apr  3 22:33:25 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 29F16106564A;
	Tue,  3 Apr 2012 22:33:25 +0000 (UTC)
	(envelope-from marius@alchemy.franken.de)
Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214])
	by mx1.freebsd.org (Postfix) with ESMTP id AE7288FC14;
	Tue,  3 Apr 2012 22:33:24 +0000 (UTC)
Received: from alchemy.franken.de (localhost [127.0.0.1])
	by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id
	q33MXMAe052013; Wed, 4 Apr 2012 00:33:22 +0200 (CEST)
	(envelope-from marius@alchemy.franken.de)
Received: (from marius@localhost)
	by alchemy.franken.de (8.14.4/8.14.4/Submit) id q33MXMY4052012;
	Wed, 4 Apr 2012 00:33:22 +0200 (CEST) (envelope-from marius)
Date: Wed, 4 Apr 2012 00:33:22 +0200
From: Marius Strobl <marius@alchemy.franken.de>
To: Andrew Pantyukhin <infofarmer@FreeBSD.org>
Message-ID: <20120403223322.GP93449@alchemy.franken.de>
References: <CA+qFSQ6nHXidbD2z+95E9a+qkMVyg4TU4Hac+G0qBU197-K5QQ@mail.gmail.com>
	<20120403082927.GH93449@alchemy.franken.de>
	<20120403122858.GA48373@alchemy.franken.de>
	<B2FD678A64EAAD45B089B123FDFC3ED72B96EF8E14@inbmail01.lsi.com>
	<A5E537D8E1B0EF499D49E9AE3E3458FE012DC44A6D@cosmail03.lsi.com>
	<20120403215714.GO93449@alchemy.franken.de>
	<CA+qFSQ5=yBmGPqoDFRdW8nsJ=QzC=zQa3OLoJ=jusdyV_btL7Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+qFSQ5=yBmGPqoDFRdW8nsJ=QzC=zQa3OLoJ=jusdyV_btL7Q@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Cc: "stable@freebsd.org" <stable@FreeBSD.org>, "zvqops@di.vc" <zvqops@di.vc>,
	"ken@freebsd.org" <ken@FreeBSD.org>, "Desai,
	Kashyap" <Kashyap.Desai@lsi.com>, "McConnell,
	Stephen" <Stephen.McConnell@lsi.com>
Subject: Re: r232411 breaks onboard 1068 detection
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2012 22:33:25 -0000

On Wed, Apr 04, 2012 at 02:26:38AM +0400, Andrew Pantyukhin wrote:
> On Wed, Apr 4, 2012 at 1:57 AM, Marius Strobl <marius@alchemy.franken.de> wrote:
> > On Tue, Apr 03, 2012 at 03:52:14PM -0600, McConnell, Stephen wrote:
> >> Marius,
> >>
> >> Since the 0x59 device is a MegaRAID device, shouldn't you be using the MegaRAID driver. ??Why is the MPT driver being used in this case? ??The problem is that the MPT driver was wrongly attaching to some MegaRAID controllers and that was causing conflict problems, so that was fixed by removing MegaRAID ID's from the MPT driver.
> >
> > Apparently, the 0x59 devices worked just fine using mpt(4) before r232411.
> > Are MegaRAID devices backwards-compatible so they can alternatively be
> > driven by MPT drivers?
> 
> The device in question is a built-in 1068-based controller on a
> SuperMicro X8ST3 board.
> 
> It can be converted to MegaRAID mode with a special addon "button"
> (AOC-IButton68).
> 
> http://www.supermicro.com/products/motherboard/Xeon3000/X58/X8ST3-F.cfm

Okay, so unless these devices also can be driven by mfi(4) when not
in MegaRAID mode, we need a way to tell both modes apart in the probe
functions of both drivers.

Marius