--- Jeff Garzik <jgarzik@xxxxxxxxx> wrote: > scans as well as no-LUN targets. My vague preference would be to use > scsi_scan_target() unless there is a strong reason not to... This sounds good too. I'd like to move sas_do_lu_discovery(struct domain_device *dev) into SCSI Core (as the comment therein says), for _new_ (non-legacy) devices, i.e. with newer FW. It also handles devices who do not even respond to REPORT LUNS on either LU 0 or RL WLUN (like early prototype SES FW), in which case it would register LU 0 for them since this is where tasks are sent. Example of those is seen in the domain sysfs tree here: http://marc.theaimsgroup.com/?l=linux-scsi&m=112629509826900&w=2 The code is at drivers/scsi/sas/sas_discover.c http://linux.adaptec.com/sas/ . Luben P.S. REPORT LUNS is Mandatory as per SPC, so newer devices (SAS) support it. Furthermore if their LUs are sparse they (really) support REPORT LUNS. - : 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
