On Tue, Jan 25, 2011 at 09:14:14AM -0500, James Bottomley wrote: > On Tue, 2011-01-25 at 04:07 +0100, Herbert Poetzl wrote: >> On Mon, Jan 17, 2011 at 06:24:15PM +0100, Tejun Heo wrote: >>> On Mon, Jan 17, 2011 at 11:21:46AM -0600, James Bottomley wrote: >>>> Expanders aren't SCSI devices either ... that means they don't >>>> appear as visible to standard SCSI mechanisms like INQUIRY (SMP >>>> isn't a SCSI protocol it's a SAS extension). They just appear as >>>> part of the topology in the device tree. >>> Ah, okay. Then, things would be much simpler. I was worrying about >>> how it would map to SCSI layer including INQUIRY emulations and all >>> those stuff. Thanks for the info. >> So, any thoughts on how and where to add the PMP to the devices >> available for sending SCSI or ATA commands to? >> I'm willing to try to add the required code, but I'm sure I'll >> benefit from a few hints from the experts ... > Well, I'm not sure I'd count as an expert on this piece: > I haven't read the relevant ATA standards. > From what I understand, SES packets are encapsulated over > an ATA command for SEMB. correct, just that it can be any protocol (it's just another bus, usually i2c) with the common protocols being SES and SAF_TE AFAIK > In that case, it should be fairly simple to recognise > this and present a SCSI device which simply encapsulates > everything sent to it over this protocol. do you have any pointers for me how that is done for SCSI? > That would allow the ses ULD to attach seamlessly. any pointers to such an SES ULD (maybe for testing)? thanks in advance, Herbert > James > -- > To unsubscribe from this list: send the line "unsubscribe linux-ide" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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
