These parse several SAS classes from /sys/class/
  - sas_host
  - sas_device
  - sas_end_device
  - sas_expander
  - sas_port
  - sas_phy

The included fixtures include examples of all of these.

Signed-off-by: Scott Laird <scott@sigkill.org>

… SAS device address to /dev/sd*.

Note that the fixtures for this rev are still *way* too big; fixtures.ttar went from ~300k to 11M.  Cleaning that up is next.

Signed-off-by: Scott Laird <scott@sigkill.org>

Still about 2x larger than before, but *much* better than the previous commit.  There's a lot of additional SAS data included in /sys/devices, and there's a limit to how much smaller it can get without a lot of work and lost data.

Signed-off-by: Scott Laird <scott@sigkill.org>

I refactored the 3 different /sys/class entries in class_sas_device, because they're almost exactly the same except for the directory name and which devices are included in the directory.

Signed-off-by: Scott Laird <scott@sigkill.org>

Signed-off-by: Scott Laird <scott@sigkill.org>

We weren't populating a couple fields due to dumb errors.  Also, I'd failed to add end_device to SASPort, which is needed for block device discovery.

Signed-off-by: Scott Laird <scott@sigkill.org>

…n code that uses this library.

Signed-off-by: Scott Laird <scott@sigkill.org>