RE: Problem Adding Transport Class support to fusion

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



There doesn't appear to be any aync message return
after negotiation mentioned on the mpi spec.

Look at mptscsih_doDv to see how dv nego parameters
are beeing maintained between target/initiator.
SPI Device page0/1 are read/written here.
The hd->Targets[] structure is repository of nego params.

This function was coded prior to my time on this driver, and I
haven't spent too much time trying to decipher it.

Eric Moore

On Tuesday, May 31, 2005 11:41 AM, James Bottomley wrote:
> 
> 
> Well ... I seem to have got parameter getting and setting working just
> about OK (modulo a few coupling issues).
> 
> The fusion driver seems to have quite a big event subsystem.  Is there
> an event that will report a device transfer agreement change? (without
> this it's a bit difficult to keep track of where the device and the
> fusion core are with negotiation)
> 
> Thanks,
> 
> James
> 
> 
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux