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 wh
t; "MegaSWR|LSILogic-1064"
0x1000 0x0054 "megaswr" "MegaSWR|LSILogic-1068"
0x1000 0x0055 "megaswr" "MegaSWR|LSILogic-1068"
0x1000 0x0057 "megaswr" "MegaSWR|LSILogic-1064E"
0x1000 0x0059 "me
nformation about this driver ?
Seems that it is provided under GPL license.
Who can provide the sources for this module ?
(only binary are provided)
Regards
--
Frederic TEMPORELLI
Message original
Sujet: RE: Fw: SAS1068 PCI-X Fusion-MPT SAS 1000:0055
Date: Mon, 5 Feb 2007
Hello Sreenivas,
> We have already been alerted (by OEMs among others) that the modinfo on
> megaswr driver needlessly shows "GPL" as the license. Ours is a binary
> only proprietary driver. I have since corrected the MODULE_LICENSE label
> to "LSI Proprietary" and updated the OEM versions. If thi
may be SCSI to USB adapter ?
such adapters seen on commercial web sites...
(adaptec, belkin, ...)
but:
- USB2 mandatory
- driver for linux ?
regards
--
Frederic Temporelli
Christopher Allen Wing a écrit :
> Hello,
>
> I'm trying to connect some older SCSI devices to new serv
orting "") in sysfs ?
2/ now, how can we get the adapter module name from sysfs ?
=> I'm just thinking that .proc_name field has to be kept initialized and/or
something has to be changed to replace the confusing "proc" prefix.
Best regards
--
Frederic TEMPORELLI
Bull -
is reporting "mptscsih" string.
Any other ideas ?
Best regards.
Douglas Gilbert a écrit :
Patrick Mansfield wrote:
On Wed, Apr 06, 2005 at 01:40:04PM +0200, Frederic TEMPORELLI wrote:
2/ now, how can we get the adapter module name from sysfs ?
Why do you need it?
Anyway, try lsscsi, it wal
Hi,
Patrick Mansfield a écrit :
On Thu, Apr 07, 2005 at 08:35:16AM +0200, Frederic TEMPORELLI wrote:
Hi,
Sorry, no such "driver" directory in /sys/class/scsi_host/hostX/
Doug answered that.
thx, I've just try the script and it works...
(mea culpa, I should have look in details
modules.
hope that somebody knows...
Frederic TEMPORELLI wrote:
Hello,
When creating a workqueue, workqueue name is limited to 10 chars
(kernel/workqueue.c , function is __create_workqueue, test is done in a
BUG_ON).
Why has this length be limited to 10 chars ?
Can I safely increase this max
What (bad) side-effects can be expected if we increase SD_STATS (4096 should be
nice, may be 8192) ?
Best regards.
--
Frederic TEMPORELLI
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at h
nd the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Frederic TEMPORELLI
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [
Hello Hannes,
Aic79xx driver for Adaptec 39320 supports 64-bit addressing, but the
initialization code of the driver is wrong: it tests the available
memory size instead of testing the maximum available memory address.
This is necessary to support servers that provides 1 Terabyte of
physical memor
James Bottomley a écrit :
Well, but the other alternative is that we hit arbitrary BUG_ON() limits
in systems that create numbered workqueues which is rather contrary to
our scaleability objectives, isn't it?
I think I'd rather the name truncation than have to respond to kernel
BUG()'s. If som
13 matches
Mail list logo
