mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: purpleidea@gmail.com, scsi <linux-scsi@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org, DL-MPTFusionLinux@lsi.com
Subject: Re: Status of the LSI 2108
Date: Thu, 20 Jan 2011 15:34:19 -0800	[thread overview]
Message-ID: <20110120153419.806d38e1.rdunlap@xenotime.net> (raw)
In-Reply-To: <1295411153.20086.81.camel@localhost>

On Tue, 18 Jan 2011 23:25:53 -0500 James Shubin wrote:

> Hi,
> 
> I've been trying to find out if the LSI 2108 is fully supported in the
> vanilla kernel, and any thoughts as to the quality/robustness.
> 
> This seems to be the correct source:
> ftp://ftp.supermicro.nl/driver/SAS/LSI/2108/Driver/Linux/v04.31/
> however I'm not sure at all if it's maintained, or what. I would
> outright test this myself, however I haven't bought the servers yet
> 
> Thanks for your help,
> Please cc-me on replies.

Hi,

Probably better to ask on the linux-scsi mailing list [added].
Also added the lsi.com email address.


drivers/scsi/mpt2sas/mpt2sas_scsih.c contains this:

	/* Liberator ~ 2108 */
	{ MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2108_1,
		PCI_ANY_ID, PCI_ANY_ID },
	{ MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2108_2,
		PCI_ANY_ID, PCI_ANY_ID },
	{ MPI2_MFGPAGE_VENDORID_LSI, MPI2_MFGPAGE_DEVID_SAS2108_3,
		PCI_ANY_ID, PCI_ANY_ID },

so it looks like there is at least some basic support for the 2108.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2011-01-20 23:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19  4:25 James Shubin
2011-01-20 23:28 ` [kernel] " Mr. James W. Laferriere
2011-01-20 23:34 ` Randy Dunlap [this message]
2011-01-20 23:57   ` James Shubin
2011-01-21 15:47     ` Unrein, Jason
2011-01-21 16:20       ` James Shubin

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=20110120153419.806d38e1.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=DL-MPTFusionLinux@lsi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=purpleidea@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®