From: Marco Schindler <marco.schindler@gmail.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Eric.Moore@lsi.com, DL-MPTFusionLinux@lsi.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Intel SASMF8I
Date: Sat, 20 Mar 2010 00:04:16 +0100 [thread overview]
Message-ID: <4BA402F0.1040501@gmail.com> (raw)
In-Reply-To: <87d699441003191546v6c0f0b89t64ab93c4e3207f37@mail.gmail.com>
On 19.03.10 23:46, Ilia Mirkin wrote:
> On Fri, Mar 19, 2010 at 6:39 PM, Marco Schindler
> <marco.schindler@gmail.com> 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?
next prev parent reply other threads:[~2010-03-19 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 22:39 Intel SASMF8I Marco Schindler
2010-03-19 22:46 ` Ilia Mirkin
2010-03-19 23:04 ` Marco Schindler [this message]
2010-03-20 13:55 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BA402F0.1040501@gmail.com \
--to=marco.schindler@gmail.com \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=Eric.Moore@lsi.com \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.