From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752023Ab0CSXEW (ORCPT ); Fri, 19 Mar 2010 19:04:22 -0400 Received: from mail-bw0-f209.google.com ([209.85.218.209]:51855 "EHLO mail-bw0-f209.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751809Ab0CSXEU (ORCPT ); Fri, 19 Mar 2010 19:04:20 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=AkheqO0X0s/TQHKkTsPZkesJdu8x+0IDOA7fUsrHDNBLMUwzEijbYpiA6iFQrW5pBa 1MhD2iRl0TIAUH1mj1hN2cih+ovnnyzYbYGzcWJZJw2qizG28ic7nHT5Au3Hih86hbNe o3Q001BpLNbIhJSwEAXc5B8632ByEA7A82R3M= Message-ID: <4BA402F0.1040501@gmail.com> Date: Sat, 20 Mar 2010 00:04:16 +0100 From: Marco Schindler User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3 MIME-Version: 1.0 To: Ilia Mirkin CC: Eric.Moore@lsi.com, DL-MPTFusionLinux@lsi.com, linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Intel SASMF8I References: <4BA3FD3E.9070801@gmail.com> <87d699441003191546v6c0f0b89t64ab93c4e3207f37@mail.gmail.com> In-Reply-To: <87d699441003191546v6c0f0b89t64ab93c4e3207f37@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 19.03.10 23:46, Ilia Mirkin wrote: > On Fri, Mar 19, 2010 at 6:39 PM, Marco Schindler > wrote: >> Hello, >> this card (using LSISAS1068(E)) is not recognized by FUSION_SAS, after >> patching the device code it appears to work nicely. >> > > I was 99% of the way there to submit a similar patch (actually there's > a few more places where you want to add the new ID), but noticed a > previous discussion when a comparable patch was rejected. Turns out > there was a jumper on my motherboard (Supermicro X8DT3) which switches > between "raid" and "regular" mode (except they were called something > much fancier), and the regular mode switches the PCI ID to 0x58 which > in turn is recognized. [And the mptsas driver doesn't support the RAID > features anyways... there's a what appears to be proprietary driver > for that, megasr, which I did not need.] SASMF8I doesn't seem to have any jumpers for "regular" mode and I don't want to use the sw raid of the chip. As far as I remember megasr didn't let me access drives directly. Is there no option then, except patching locally?