public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Maarten Vanraes <maarten@ba.be>
Cc: linux-kernel@vger.kernel.org, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: megaraid_sata vs megasr
Date: Mon, 26 May 2008 13:11:26 -0400	[thread overview]
Message-ID: <483AEF3E.5010309@garzik.org> (raw)
In-Reply-To: <200805261005.31015.maarten@ba.be>

Maarten Vanraes wrote:
> Hello, (can you CC me? i'm not on the list)
> 
> I have a LSI MegaRAID SAS 8204ELP card, and since it wasn't recognized by any 
> driver, i tried using the megasr driver supplied by LSI (it also supplies 
> open_source code with it), i had to modify the code a bit to get it to boot 
> with kernel-2.6.21 . but there's a very high iowait on it. i'm wondering if 
> the megaraid_sas driver is meant to be the driver for the same hardware as 
> megasr? would it help if i just added another PCI ID to the module and try 
> that one?
> 
> Sincerely,
> 
> Maarten Vanraes
> 
> [] # lspci -s 08:00.0 -vvvn
> 08:00.0 0100: 1000:0059 (rev 08)
>         Subsystem: 1000:3002
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ 
> Stepping- SERR+ FastB2B- DisINTx-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> <TAbort- <MAbort- >SERR+ <PERR- INTx-
>         Latency: 0, Cache Line Size: 32 bytes
>         Interrupt: pin A routed to IRQ 18
>         Region 0: I/O ports at 3000 [size=256]
>         Region 1: Memory at d8410000 (64-bit, non-prefetchable) [size=16K]
>         Region 3: Memory at d8400000 (64-bit, non-prefetchable) [size=64K]
>         [virtual] Expansion ROM at d8000000 [disabled] [size=2M]
>         Capabilities: [50] Power Management version 2
>         Capabilities: [68] Express (v1) Endpoint, MSI 00
>         Capabilities: [98] Message Signalled Interrupts: Mask- 64bit+ 
>         Capabilities: [b0] MSI-X: Enable- Mask- TabSize=1
>         Capabilities: [100] Advanced Error Reporting <?>

Yeah you can try drivers/scsi/megaraid/megaraid_sas.c or 
drivers/message/fusion/mptsas.c.

A URL to the megasr driver would be nice.

Also, please keep linux-scsi in CC (I added it), that's where this sort 
of things is usually discussed.

	Jeff




       reply	other threads:[~2008-05-26 17:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200805261005.31015.maarten@ba.be>
2008-05-26 17:11 ` Jeff Garzik [this message]
2008-05-27  9:55   ` megaraid_sata vs megasr Maarten Vanraes
2008-05-27 20:32     ` Moore, Eric
2008-05-28 14:17       ` Maarten Vanraes
2008-05-28 15:44         ` Moore, Eric
2008-05-28 16:31           ` Maarten Vanraes

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=483AEF3E.5010309@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=maarten@ba.be \
    /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