From owner-freebsd-stable@FreeBSD.ORG Tue Apr 3 23:06:51 2012 Return-Path: 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 012AB106566C; Tue, 3 Apr 2012 23:06:51 +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 6AF1A8FC16; Tue, 3 Apr 2012 23:06:50 +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 q33N6m3M052115; Wed, 4 Apr 2012 01:06:48 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id q33N6mDd052114; Wed, 4 Apr 2012 01:06:48 +0200 (CEST) (envelope-from marius) Date: Wed, 4 Apr 2012 01:06:48 +0200 From: Marius Strobl To: Andrew Pantyukhin Message-ID: <20120403230648.GQ93449@alchemy.franken.de> References: <20120403082927.GH93449@alchemy.franken.de> <20120403122858.GA48373@alchemy.franken.de> <20120403215714.GO93449@alchemy.franken.de> <20120403223322.GP93449@alchemy.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: "stable@freebsd.org" , "zvqops@di.vc" , "ken@freebsd.org" , "Desai, Kashyap" , "McConnell, Stephen" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Apr 2012 23:06:51 -0000 On Wed, Apr 04, 2012 at 02:38:54AM +0400, Andrew Pantyukhin wrote: > On Wed, Apr 4, 2012 at 2:33 AM, Marius Strobl wrote: > > On Wed, Apr 04, 2012 at 02:26:38AM +0400, Andrew Pantyukhin wrote: > >> 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. > > mfi(4) obviously didn't attach, but if anyone is willing to provide a > quick patch listing the IDs in mfi(4), I'll try. > > I wouldn't welcome the change though, as we prefer the JBOD way. I still highly doubt that 0x59 will work with mfi(4) in non-MegaRAID mode. Looking at the source of the Linux megasr driver, that one attaches to several 0x59 devices but only in case of certain sub-vendor (amongst other Supermicro) and sub-device IDs, but not in case of a sub-vendor ID of LSI and a sub-device ID of 0x1000 like in your case. So this seems like a way to go to distinguish the modes if LSI can provide a complete list of sub-device IDs (and sub-vendor in case something besides LSI is used) in which case 0x59 should be treated in MPT mode. Marius