The lun field is ignored in SCSI-3 (not just FC). The 64-bit lun is
also not FC specific.
A generic field name like scsi3_hba might be a better alternative,
-prasenjit
Frank Zago <[EMAIL PROTECTED]>@vger.kernel.org on 02/05/2001
07:19:35 PM
Sent by: [EMAIL PROTECTED]
To: Eric Youngdale <[EMAIL PROTECTED]>
cc: <[EMAIL PROTECTED]>
Subject: Re: Scan past lun 7 in 2.4.0
> The second question has to do with the correct setting for the 2nd
> command byte. This is typically set to something like:
>
> scsi_cmd[1] = (lun << 5) & 0xe0;
>
> which is obviously broken in the event that the number of luns is > 8.
> This patch starts to clean this up by forcing scsi_cmd[1] to 0 in such
> instances. The actual change came from someone else - my question is
what
> is the appropriate setting for scsi_cmd[1]? A value of 0 seems
> reasonable, I guess.
For fibre channel, this field should be ignored by the devices. You might
also add a new flag to Scsi_Host
unsigned int fc_hba:1; /* 0=scsi, 1=fc adapter */
and use that field to fill the scsi_cmd[1]. This can be set by the driver
during initialization.
Also a fibre channel lun is 64 bits.
--
Frank Zago - Gresham Enterprise Storage - www.greshamstorage.com
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]