* Re: [ANNOUNCE] MPT Fusion driver 3.02.06 update
2004-10-25 23:32 [ANNOUNCE] MPT Fusion driver 3.02.06 update Moore, Eric Dean
@ 2004-10-26 8:09 ` Masao Fukuchi
2004-10-26 8:20 ` Douglas Gilbert
` (2 subsequent siblings)
3 siblings, 0 replies; 7+ messages in thread
From: Masao Fukuchi @ 2004-10-26 8:09 UTC (permalink / raw)
To: Moore, Eric Dean; +Cc: linux-scsi
Hi Eric,
I installed Fusion MPT driver 3.02.06 into my tiger4(SR870BN4).
But I have some problems.
1.compile error
When I compiled your driver with kernel 2.6.9, compile operation
failed with error.
I checked mptbase.c(and mptbase.h) and found your code shows:
#if (LINUX_VERSION_CODE > KERNEL_VERSION(2,6,8))
pci_save_state(pdev);
#else
pci_save_state(pdev, ioc->PciState);
#endif
But pci_save_state() in kernel 2.6.9 has two parameters.
(I don't know which kernel version has 1 parameter)
2.startup sequence fail
I fixed above problem temporarily and compiled it.
The compile operation finished with no error.
Then I started Linux, but the startup sequence failed with
following error.
>mptbase: Initiating ioc0 bringup
>mptbase: ioc0: ERROR - Diagnostic reset FAILED! (142h)
>mptbase: ioc0 NOT READY WARNING!
>mptbase: WARNING - ioc0 did not initialize properly! (-1)
>mptbase: probe of 0000:04:02.0 failed with error -1
This message shows, IOC didn't become ready.
The LSI53C1030 on Tiger4 has no flash ROM, I think the cause
of the problem was fusion MPT driver didn' execute Firmware
Download Boot operation.
If you have any questions or comments, please let me know.
Thanks,
M.Fukuchi
Moore, Eric Dean wrote:
>All,
>
>We are pleased to announce the MPT Fusion release candidate for lk 2.6
>
>Highlights of this release:
>キ SAS Support - 1064, 1066, 1068
>キ mpi headers v1.5.2
>キ csmi ioctl support
>キ MSI Support
>キ fc_transport support
>キ several patches incorporated from Christoph Hellwig
>
>
>This patch applied against bk://linux-scsi.bkbits.net/scsi-misc-2.6
>
>Here is a link to this patch:
>ftp://ftp.lsil.com/HostAdapterDrivers/linux/Fusion-MPT/2.6-kernel/3.02.06/mp
>tlinux-3.02.06.patch
>
>
>Full source and release notes are also provided at link above.
>
>Eric Moore
>LSI Logic Corporation
>
>
>
>-
>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
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [ANNOUNCE] MPT Fusion driver 3.02.06 update
2004-10-25 23:32 [ANNOUNCE] MPT Fusion driver 3.02.06 update Moore, Eric Dean
2004-10-26 8:09 ` Masao Fukuchi
@ 2004-10-26 8:20 ` Douglas Gilbert
2004-10-26 9:53 ` Christoph Hellwig
2004-10-26 10:38 ` Christoph Hellwig
3 siblings, 0 replies; 7+ messages in thread
From: Douglas Gilbert @ 2004-10-26 8:20 UTC (permalink / raw)
To: Moore, Eric Dean; +Cc: linux-scsi
Moore, Eric Dean wrote:
> All,
>
> We are pleased to announce the MPT Fusion release candidate for lk 2.6
>
> Highlights of this release:
> · SAS Support - 1064, 1066, 1068
Eric,
Perhaps this would be a good time to define a
generic sas_transport layer.
> · mpi headers v1.5.2
> · csmi ioctl support
> · MSI Support
> · fc_transport support
> · several patches incorporated from Christoph Hellwig
>
>
> This patch applied against bk://linux-scsi.bkbits.net/scsi-misc-2.6
>
> Here is a link to this patch:
> ftp://ftp.lsil.com/HostAdapterDrivers/linux/Fusion-MPT/2.6-kernel/3.02.06/mp
> tlinux-3.02.06.patch
>
>
> Full source and release notes are also provided at link above.
Doug Gilbert
-
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ANNOUNCE] MPT Fusion driver 3.02.06 update
2004-10-25 23:32 [ANNOUNCE] MPT Fusion driver 3.02.06 update Moore, Eric Dean
2004-10-26 8:09 ` Masao Fukuchi
2004-10-26 8:20 ` Douglas Gilbert
@ 2004-10-26 9:53 ` Christoph Hellwig
2004-10-26 10:38 ` Christoph Hellwig
3 siblings, 0 replies; 7+ messages in thread
From: Christoph Hellwig @ 2004-10-26 9:53 UTC (permalink / raw)
To: Moore, Eric Dean; +Cc: linux-scsi
On Mon, Oct 25, 2004 at 07:32:35PM -0400, Moore, Eric Dean wrote:
> All,
>
> We are pleased to announce the MPT Fusion release candidate for lk 2.6
>
> Highlights of this release:
> · SAS Support - 1064, 1066, 1068
> · mpi headers v1.5.2
> · csmi ioctl support
> · MSI Support
> · fc_transport support
> · several patches incorporated from Christoph Hellwig
Care to split it into small and reviewable per-topic patches that we have been
asking driver writers to provide for a long time?
-
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ANNOUNCE] MPT Fusion driver 3.02.06 update
2004-10-25 23:32 [ANNOUNCE] MPT Fusion driver 3.02.06 update Moore, Eric Dean
` (2 preceding siblings ...)
2004-10-26 9:53 ` Christoph Hellwig
@ 2004-10-26 10:38 ` Christoph Hellwig
2004-11-05 0:55 ` CSMI [was: Re: [ANNOUNCE] MPT Fusion driver 3.02.06 update] Douglas Gilbert
3 siblings, 1 reply; 7+ messages in thread
From: Christoph Hellwig @ 2004-10-26 10:38 UTC (permalink / raw)
To: Moore, Eric Dean; +Cc: linux-scsi
On Mon, Oct 25, 2004 at 07:32:35PM -0400, Moore, Eric Dean wrote:
> All,
>
> We are pleased to announce the MPT Fusion release candidate for lk 2.6
Some things that come to mind immediately:
>
>
> Highlights of this release:
> · SAS Support - 1064, 1066, 1068
there's still tons of ioc->chip_type checks for SPI vs FC vs SAS -
please always use the new bus_type member
> · csmi ioctl support
rejected, this ioctl interface is completely horrible, even worse than
the fc hbaapi. Please help to provide a proper sas transport class similar
to the fc one.
> · fc_transport support
please don't put this under all kinds of ifdefs, also it's not working with
current mainline anymore anyway.
Any reason there's no SPI transport attribute support, it's rather asymetric
this way..
-
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
^ permalink raw reply [flat|nested] 7+ messages in thread* CSMI [was: Re: [ANNOUNCE] MPT Fusion driver 3.02.06 update]
2004-10-26 10:38 ` Christoph Hellwig
@ 2004-11-05 0:55 ` Douglas Gilbert
2004-11-05 8:23 ` Christoph Hellwig
0 siblings, 1 reply; 7+ messages in thread
From: Douglas Gilbert @ 2004-11-05 0:55 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Moore, Eric Dean, linux-scsi
Christoph Hellwig wrote:
> On Mon, Oct 25, 2004 at 07:32:35PM -0400, Moore, Eric Dean wrote:
>
>>All,
>>
>>We are pleased to announce the MPT Fusion release candidate for lk 2.6
>
>
> Some things that come to mind immediately:
>
>
>>
>>Highlights of this release:
>>· SAS Support - 1064, 1066, 1068
>
>
> there's still tons of ioc->chip_type checks for SPI vs FC vs SAS -
> please always use the new bus_type member
>
>
>
>>· csmi ioctl support
>
>
> rejected, this ioctl interface is completely horrible, even worse than
> the fc hbaapi. Please help to provide a proper sas transport class similar
> to the fc one.
Christoph,
I'm not so sure why you want to reject this ioctl
at this stage when our existing infrastructure to handle
the 4 protocols that go through this SAS HBA is weak.
Those 4 protocols are:
a) SSP (SCSI over a SAS transport) we should be able to
handle this one *** ****
b) SMP is a packet like protocol meant mainly to probe
and control expanders (think device discovery). The
"target" is not necessarily a SCSI device and there
is no concept of luns. Nice candidate for the sg driver.
c) STP: ATA/ATAPI-7 tunnelled through a SAS transport with
a SAS/sATA bridge probably hiding in an expander
d) sATA: direct connect of a sATA disk to this SAS HBA
The t10 meeting next week will be considering the
"Common Storage Management Interface for SAS" (CSMI)
proposal. Here is a url for it:
ftp://ftp.t10.org/t10/document.04/04-284r0.pdf
This document names 3 target platforms: Windows, Linux
(2.4 and 2.6 series) and Netware.
This seems like a serious attempt to retrofit a control
(and passthrough) interface into existing OS SCSI stacks
at the LLD level. I have no information but I would expect
the Adaptec SAS HBA (when and if its Open source driver
becomes public) to follow the same (or a similar) route.
*** The primary SAS device identifier is a 64 bit SAS address
(naa 5, world wide unique). CSMI defines mapping functions
between the <h,c,t> like tuples that most OSes use in their
SCSI stacks (thanks to SPI) and SAS addresses. In short the CSMI
proposal looks like the distilled experience of writing real
SAS HBA drivers for several existing OSes.
**** Given the BCC (bridge controller commands) draft at t10
it would appear that SAS disk enclosure designers want to
command set convert ATA/ATAPI-7 into SPC in the enclosure.
That way sATA disks will appear as SAS disks (with a SCSI-ATA
pass-through command for awkward things like SMART). Such a
move would make the STP protocol superfluous.
Doug Gilbert
-
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
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: CSMI [was: Re: [ANNOUNCE] MPT Fusion driver 3.02.06 update]
2004-11-05 0:55 ` CSMI [was: Re: [ANNOUNCE] MPT Fusion driver 3.02.06 update] Douglas Gilbert
@ 2004-11-05 8:23 ` Christoph Hellwig
0 siblings, 0 replies; 7+ messages in thread
From: Christoph Hellwig @ 2004-11-05 8:23 UTC (permalink / raw)
To: Douglas Gilbert; +Cc: Christoph Hellwig, Moore, Eric Dean, linux-scsi
On Fri, Nov 05, 2004 at 10:55:27AM +1000, Douglas Gilbert wrote:
> Christoph,
> I'm not so sure why you want to reject this ioctl
> at this stage when our existing infrastructure to handle
> the 4 protocols that go through this SAS HBA is weak.
Rationale:
a) we're not gonna add another ioctl interface at this stage, especially
not a that clumsy one
b) things that are common for all SAS HBAs should not be in the LLDD but
in a transport class
^ permalink raw reply [flat|nested] 7+ messages in thread