public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic TEMPORELLI <frederic.temporelli@ext.bull.net>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Fw: SAS1068 PCI-X Fusion-MPT SAS 1000:0055
Date: Mon, 05 Feb 2007 07:49:04 +0100	[thread overview]
Message-ID: <45C6D360.7050206@ext.bull.net> (raw)
In-Reply-To: <45BF6CDC.1080102@ext.bull.net>

Eric,


Do you have more information about 'megasr' module, which seems able to
manage 'MegaRAID' on LSI 1068 ?

This module is also named 'megaswr'

Here's modinfo output for this module (binary for RH4, but can also be
found for SLES9)
==========================================================
[root@iotiger2 x86_64]# modinfo megaswr.ko
filename:       megaswr.ko
parm:           low_mem_g:Set to 1 to simulate low mem condition
parm:           dbglvl_g:driver-wide debug flag
license:        GPL
description:    LSI Logic SofrRAID Driver
author:         LSI Logic Corporation
alias:          pci:v00000000d00000000sv00000000sd00000000bc*sc*i*
alias:          pci:v00000000d00000000sv00000000sd00000000bc*sc*i*
alias:          pci:v00000000d00000000sv00000000sd00000000bc*sc*i*
...
alias:          pci:v00000000d00000000sv00000000sd00000000bc*sc*i*
alias:          pci:v00000000d00000000sv00000000sd00000000bc*sc*i*
depends:        scsi_mod
vermagic:       2.6.9-22.ELsmp SMP gcc-3.4
==========================================================


=> the module is provided by LSI (I get it from the web from supermicro)
=> the module is under GPL (but sources aren't shipped, nor the GPL
license )
=> the module is shipped with a 'pci.ids' file, with following content:
==========================================================
0x8086 0x2652   "megaswr"       "MegaSWR|INTEL-ICH6R"
0x8086 0x2682   "megaswr"       "MegaSWR|INTEL-ESB2"
0x8086 0x27C1   "megaswr"       "MegaSWR|INTEL-ICH7R"
0x8086 0x27C3   "megaswr"       "MegaSWR|INTEL-ICH7R"
0x1000 0x0030   "megaswr"       "MegaSWR|LSILogic-1030"
0x1000 0x0050   "megaswr"       "MegaSWR|LSILogic-1064"
0x1000 0x0054   "megaswr"       "MegaSWR|LSILogic-1068"
0x1000 0x0055   "megaswr"       "MegaSWR|LSILogic-1068"
0x1000 0x0057   "megaswr"       "MegaSWR|LSILogic-1064E"
0x1000 0x0059   "megaswr"       "MegaSWR|LSILogic-1068E"
==========================================================
(note the chip with id 1000:0055)

Hope that you can give us more details...

regards
--
Frederic TEMPORELLI




Frederic TEMPORELLI a écrit :
> Hi,
> 
> Also seen on a NEC server, a 1068 chip with a jumper used to switch chip
> PCI ID and its BIOS:
> - PCI ID = 0054 => 'MPT Fusion' BIOS
> - PCI ID = 0055 => 'MegaRAID' BIOS
> 
> I'm feeling that I submit this unusual chip ID to pciid DB some month ago...
> 
> More important: there's a driver for this chip when it is used in
> 'MegaRAID' mode (standard 'mptsas' driver may be used for MPT Fusion
> mode) . This driver is named 'megasr' and is available (binaries) from
> several server vendors (Intel/Supermicro/Hitachi...) for standard distro
> (RH,Suse).
> Seems that this driver is provided by LSI (modinfo)...
> 
> regards
> --
> Fred
> 
> 
> Moore, Eric a écrit :
>> On Friday, January 26, 2007 12:53 PM, Jun'ichi Nomura wrote: 
>>> Hi,
>>>
>>>> I have new NEC server with SAS1068 PCI-X Fusion-MPT SAS
>>>> pciid: 1000:0055
>>>> mptsas form 2.6.20-rc5 don't recognize it ;(
>>>>
>>>> I see that driver support only 1000:0054 and 1000:0058 devices.
>>> It might be that the device has software RAID feature and changes
>>> device ID based on setup. (1000:0055 when software RAID is enabled
>>> and 1000:0054 or something for normal SAS)
>>>
>>> If so, there is a chance you can disable the software RAID
>>> via BIOS setup utility.
>>>
>>> Thanks,
>>> -- 
>>> Jun'ichi Nomura, NEC Corporation of America
>>>
>> You probably want to talk to the megaraid folks and see
>> if the have a driver for that.
>>
>> I didn't submit a device id of 0055 to sourceforge.
>>
>> The only 1068 ids that are clamied by mptsas is 0054 and 0058
>> which are the pcix and pcie solutions.   I notice that 0055 is
>> listed in repository, but it was not me that submitted that.
>> http://pci-ids.ucw.cz/iii/?i=1000 
>>
>> Eric Moore
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-02-05  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29 16:14 Fw: SAS1068 PCI-X Fusion-MPT SAS 1000:0055 Moore, Eric
2007-01-30 16:05 ` Frederic TEMPORELLI
2007-02-05  6:49   ` Frederic TEMPORELLI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-05 17:04 Moore, Eric
2007-01-26 10:19 Andrew Morton
2007-01-26 19:53 ` Jun'ichi Nomura
2007-01-29 20:20   ` Arkadiusz Patyk

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=45C6D360.7050206@ext.bull.net \
    --to=frederic.temporelli@ext.bull.net \
    --cc=Eric.Moore@lsi.com \
    --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