libata: Support SATA attached via SAS
Status from this message: applied to #upstream
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | libata: Setup nbytes in ata_sg_init_onedrivers/ | +1 | 1 reply | |
| 2/6 | libata: Add host lock to struct ata_portdrivers/ drivers/ drivers/ +2 more | +47 | 1 reply | |
| 3/6 | libata: Add ata_scsi_dev_disableddrivers/ | +31 | 0 replies | |
| 4/6 | libata: Add ata_host_flagsdrivers/ include/ | +10 | 4 replies | |
| 5/6 | libata: Per device max command length checkingdrivers/ drivers/ | +7 | 2 replies | |
| 6/6 | libata: Add support for SATA attachment to SAS adaptersdrivers/ drivers/ drivers/ +1 more | +177 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] libata: Support SATA attached via SAS
Jeff,
Here is a refresh of my patchset to allow SAS HBAs to use libata to control attached SATA devices. It should apply cleanly to #upstream.
James,
After our discussion at the storage summit I think I have
a better idea what you are looking for with a SATA transport class. Unfortunately, the problem I am facing is that I am dealing with a firmware stack (ipr) which does not expose the physical transport to the host. The ipr firmware does all the device discovery and reports a configuration table describing the attached devices, but does not export any physical topology information. At some point in the future I hope to be able to extract this information from the ipr firmware stack and convert ipr to be able to utilize the sas/sata transport class, but, unfortunately, the firmware interfaces to accomplish this aren't available at this time.
Brian
Signature · 3 lines
Brian King eServer Storage I/O IBM Linux Technology Center