linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@kvack.org>
To: linux-scsi@vger.kernel.org
Subject: [RFC/PATCH] add PCI id for HighPoint RocketRAID 2720 to mvsas
Date: Wed, 20 Oct 2010 18:31:10 -0400	[thread overview]
Message-ID: <20101020223110.GT2315@kvack.org> (raw)

Hi folks,

I recently built a system using the HighPoint 2720 SAS controller, which 
is based on the Marvell 88SE9485.  In my limited testing (read: it boots), 
the following patch is needed to get mvsas to recognize the board.  With 
this patch, the system boots without issue and SATA passthrough seems to 
work.  Note that I have not tested the board with any SAS drives, as I 
only have SATA drives at present.  Any thoughts/comments on if anything 
further is needed for this board?

Signed-off-by: Benjamin LaHaise <bcrl@kvack.org>
diff --git a/drivers/scsi/mvsas/mv_init.c b/drivers/scsi/mvsas/mv_init.c
index 19ad34f..4590faa 100644
--- a/drivers/scsi/mvsas/mv_init.c
+++ b/drivers/scsi/mvsas/mv_init.c
@@ -648,6 +648,15 @@ static struct pci_device_id __devinitdata mvs_pci_table[] = {
 	{ PCI_VDEVICE(MARVELL, 0x6320), chip_6320 },
 	{ PCI_VDEVICE(MARVELL, 0x6340), chip_6440 },
+	{	/* HighPoint RocketRAID 2720 */
+		.vendor 	= 0x1103,
+		.device 	= 0x2720,
+		.subvendor	= PCI_ANY_ID,
+		.subdevice	= 0x0000,
+		.class		= 0,
+		.class_mask	= 0,
+		.driver_data	= chip_1320,
+	},
 	{
 		.vendor 	= PCI_VENDOR_ID_MARVELL,
 		.device 	= 0x6440,
 		.subvendor	= PCI_ANY_ID,

             reply	other threads:[~2010-10-20 23:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 22:31 Benjamin LaHaise [this message]
2010-10-29  2:24 ` [RFC/PATCH] add PCI id for HighPoint RocketRAID 2720 to mvsas Benjamin LaHaise
2010-10-29  5:23   ` Ron Pitts
2010-10-29  5:37     ` Benjamin LaHaise

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=20101020223110.GT2315@kvack.org \
    --to=bcrl@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).