Haiku OS support, add pt function list in sg_pt_dummy.c; add slices to sg_mrq_dd

git-svn-id: https://svn.bingwo.ca/repos/sg3_utils/trunk@905 6180dd3e-e324-4e3e-922d-17de1ae2f315

3 files changed, 38 insertions, 2 deletions

diff --git a/doc/Makefile.in b/doc/Makefile.in
index 81cdadb3..4b9b7476 100644
--- a/doc/Makefile.in
+++ b/doc/Makefile.in
@@ -267,6 +267,8 @@ localstatedir = @localstatedir@
 mandir = @mandir@
 mkdir_p = @mkdir_p@
 oldincludedir = @oldincludedir@
+os_cflags = @os_cflags@
+os_libs = @os_libs@
 pdfdir = @pdfdir@
 prefix = @prefix@
 program_transform_name = @program_transform_name@
diff --git a/doc/sg_inq.8 b/doc/sg_inq.8
index db591986..a0bfae94 100644
--- a/doc/sg_inq.8
+++ b/doc/sg_inq.8
@@ -1,4 +1,4 @@
-.TH SG_INQ "8" "March 2021" "sg3_utils\-1.46" SG3_UTILS
+.TH SG_INQ "8" "June 2021" "sg3_utils\-1.47" SG3_UTILS
 .SH NAME
 sg_inq \- issue SCSI INQUIRY command and/or decode its response
 .SH SYNOPSIS
@@ -492,6 +492,24 @@ pages (but not their contents) try:
 .PP
    sg_inq \-e /dev/sda
 .PP
+In Linux, binary images of some important VPD page responses (e.g. 0, 80h
+and 83h) are cached in files within the sysfs pseudo file system. Since
+VPD pages hardly ever change their contents, decoding those files will
+give the same output as probing the device with the added benefit that
+decoding those files doesn't need root permissions. If /dev/sg3 is a disk
+at 2:0:0:0 , then these three invocations should result in the same output:
+.PP
+   sg_inq \-\-raw \-\-inhex=/sys/class/scsi_generic/sg3/device/vpd_pg83
+.PP
+   sg_inq \-rI /sys/class/scsi_generic/sg3/device/vpd_pg83
+.PP
+   sg_inq \-r \-I /sys/class/scsi_disk/2:0:0:0/device/vpd_pg83
+.PP
+Without the \fI\-\-raw\fR option, the \fI\-\-inhex=FN\fR option would
+expect the contents of those files to be hexadecimal. vpd_pg83 contains
+the response (in binary) to the Device Identification VPD page whose page
+number is 83h (i.e. hexadecimal).
+.PP
 Some VPD pages can be read with the sg_inq utility but a newer utility
 called sg_vpd specializes in showing their contents. The sdparm utility
 can also be used to show the contents of VPD pages.
diff --git a/doc/sg_vpd.8 b/doc/sg_vpd.8
index 17d5f130..e1e19956 100644
--- a/doc/sg_vpd.8
+++ b/doc/sg_vpd.8
@@ -1,4 +1,4 @@
-.TH SG_VPD "8" "March 2021" "sg3_utils\-1.46" SG3_UTILS
+.TH SG_VPD "8" "June 2021" "sg3_utils\-1.47" SG3_UTILS
 .SH NAME
 sg_vpd \- fetch SCSI VPD page and/or decode its response
 .SH SYNOPSIS
@@ -314,6 +314,22 @@ excluding vendor specific VPD pages that start at page number 0xc0:
 .PP
    # sg_vpd \-\-all \-\-page=0xbf \-\-raw \-\-inhex=all_vpds.bin
 .PP
+In Linux, binary images of some important VPD page responses (e.g. 0, 80h
+and 83h) are cached in files within the sysfs pseudo file system. Since
+VPD pages hardly ever change their contents, decoding those files will
+give the same output as probing the device with the added benefit that
+decoding those files doesn't need root permissions. The long and short
+forms are shown:
+.PP
+   sg_vpd \-\-raw \-\-inhex=/sys/class/scsi_generic/sg3/device/vpd_pg83
+.PP
+   sg_vpd \-rI /sys/class/scsi_generic/sg3/device/vpd_pg83
+.PP
+If /dev/sg3 is a disk at 2:0:0:0 , then this invocation should give more
+verbose output but essentially the same as the previous two examples.
+.PP
+   sg_vpd \-v \-r \-I /sys/class/scsi_disk/2:0:0:0/device/vpd_pg83
+.PP
 Further examples can be found on the https://sg.danny.cz/sg/sg3_utils.html
 web page.
 .SH AUTHOR