On Tue, 2006-03-28 at 16:38 -0600, Brian King wrote: > My direction at this point has been to move away from > the virtual scsi host device for SATA devices attached > to SAS HBAs. This seemed to me to be the clearest implementation. > Then you have 1 SAS HBA = 1 struct scsi_host, no matter > how many SATA devices are attached underneath it either > via direct attach or via an expander. That's what a transport class implementation would allow you to do. As long as the representation of the host controller device (be it PCI, SCSI IDE or whatever) has an embedded generic device, the class can attach and carry attributes. 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
