Re: [PATCH] minimal SAS transport class

[Luben Tuikov <luben_tuikov@adaptec.com>]

> +void sas_add_target(struct sas_port *port, struct sas_identify *attached,
> +		uint channel, uint target)
> +{
> +	if (attached->target_port_protocols &
> +	    (SAS_PROTOCOL_SSP|SAS_PROTOCOL_STP|SAS_PROTOCOL_SATA))
> +		scsi_scan_target(&port->dev, channel, target, ~0, 0, attached);
> +}

I've a few questions:

1. What kind of device does the Fusion driver export?
   Is this a true end device, or is this the LU in the SSP end device?

   I.e. since the Fusion card firmware does everything about SAS there is,
   is also LU discovery done in the firmware, or does the firmware export
   only the SSP end devices and leave LU discovery to SCSI Core
   (as the code suggests)?

2. Since I saw that (end) devices bind to ports, what is the maximum
   number of ports that the Fusion firmware export?

3. Will control of SATA and STP devices be given to libata or will
   the Fision firmware make those look like SCSI devices?

Thanks,
	Luben