> Identifiers and names of target ports and of logical units (per SAM-2 and > later, Annex A) --- whether they are persistent, in which scope they are > unique, how they look like, and how they can be obtained --- are transport > specific. > > Neither the INQUIRY command (per SPC) nor any other command is generally > useful to obtain e.g. logical unit identifiers. Any tool that needs to > obtain identifiers or names of target ports and of logical units must talk > with the transport driver through driver-specific interfaces. Inquiry page 0x83 has been mandatory for a while now, and while the name/id assignments are all over the place, it is getting better. Page 0x80 is also supported on nearly every device manufactured in the last 10 years. Parsing a few common cases covers the majority of the devices. Of course, the returned information may not be helpful (even when supported), but we are mostly just talking about messages being displayed to the user. Some of this information is already being stored in the kernel, printing something like "s[dgt]X (man/model/serial/portinfo)" instead of just a "sda" via sd_printk/etc would probably be quite helpful in a lot of situations. Finally, printing this information provides encouragement to the device manufactures to make sure its available and correct. -- To unsubscribe from this list: 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
