diff options
Diffstat (limited to 'examples')
-rw-r--r-- | examples/forwarded_sense.txt | 16 | ||||
-rw-r--r-- | examples/nvme_dev_self_test.hex | 20 | ||||
-rw-r--r-- | examples/nvme_identify_ctl.hex | 27 | ||||
-rw-r--r-- | examples/nvme_read_ctl.hex | 38 | ||||
-rw-r--r-- | examples/nvme_write_ctl.hex | 38 | ||||
-rw-r--r-- | examples/ref_sense.txt | 7 |
6 files changed, 0 insertions, 146 deletions
diff --git a/examples/forwarded_sense.txt b/examples/forwarded_sense.txt deleted file mode 100644 index 98d8ab42..00000000 --- a/examples/forwarded_sense.txt +++ /dev/null @@ -1,16 +0,0 @@ -# Test forwarded sense data. Values are in hex. -# Invocation: 'sg_decode_sense -f forwarded_sense.txt' [dpg 20110209] - -# descriptor header -72 6 18 7 0 0 0 1c - -# Forwarded sense [len=12] -c a 1 2 -72 6 18 7 0 0 0 0 - -# Information [len=12] -0 a 80 0 11 22 33 44 55 66 77 88 - -# FRU [len=4] -3 2 0 - 99 diff --git a/examples/nvme_dev_self_test.hex b/examples/nvme_dev_self_test.hex deleted file mode 100644 index 1ef87c62..00000000 --- a/examples/nvme_dev_self_test.hex +++ /dev/null @@ -1,20 +0,0 @@ -# 64 byte NVMe Device Self Test command (an Admin command) that is suitable -# for: -# sg_raw --cmdfile=<this_file_name> <nvme_device> -# -# There is no data-in or data-out associated with this command. This command -# is optional so check the Identify controller command response to see if -# it is supported. -# -# The following invocation will self test the controller and all its -# namespaces (since nsid=0xffffffff) and does a "short" self test on each -# one (since CDW10 is 0x1). - -14 00 00 00 ff ff ff ff 00 00 00 00 00 00 00 00 -00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 -00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - -# A typical invocation in Linux and FreeBSD would look like this: -# sg_raw --cmdfile=nvme_dev_self_test.hex /dev/nvme0 -# diff --git a/examples/nvme_identify_ctl.hex b/examples/nvme_identify_ctl.hex deleted file mode 100644 index f22141e2..00000000 --- a/examples/nvme_identify_ctl.hex +++ /dev/null @@ -1,27 +0,0 @@ -# 64 byte NVMe Identify controller command (an Admin command) that is -# suitable for: -# sg_raw --cmdfile=<this_file_name> --request=4096 <nvme_device> -# -# The address field (at byte offset 24, 8 bytes and little endian) gives -# special meaning to the highest address pointers: -# ffffffff fffffffe use address of data-in buffer -# ffffffff fffffffd use address of data-out buffer -# -# The data length field (at byte offset 36, 4 bytes and little endian) -# gives special meaning to the highest block counts: -# fffffffe use byte length of data-in buffer -# fffffffd use byte length of data-out buffer -# -# Since The Identify command reads data "in" from the device, then the -# data-in buffer is appropriate. - -06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -00 00 00 00 00 00 00 00 fe ff ff ff ff ff ff ff -00 00 00 00 fe ff ff ff 01 00 00 00 00 00 00 00 -00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - -# A typical invocation in Linux and FreeBSD would look like this: -# sg_raw --cmdfile=nvme_identify_ctl.hex -r 4k /dev/nvme0 -# -# NVMe likes "4k" (4096 bytes) buffer size, preferably aligned to -# a 4096 byte (or "page") boundary. diff --git a/examples/nvme_read_ctl.hex b/examples/nvme_read_ctl.hex deleted file mode 100644 index 397072d8..00000000 --- a/examples/nvme_read_ctl.hex +++ /dev/null @@ -1,38 +0,0 @@ -# 64 byte NVMe, Read command (a NVM command) that is suitable for: -# sg_raw --cmdfile=<this_file_name> --nvm --request=2048 <nvme_device> -# -# The address field (at byte offset 24, 8 bytes and little endian) gives -# special meaning to the highest address pointers: -# ffffffff fffffffe use address of data-in buffer -# ffffffff fffffffd use address of data-out buffer -# -# The data length field (at byte offset 36, 4 bytes and little endian) -# gives special meaning to the highest block counts: -# fffffffe use byte length of data-in buffer -# fffffffd use byte length of data-out buffer -# -# 512 byte logical block size is assumed. Read 4 blocks hence 2048bytes. -# The first LBA read is 0x12345 and the namespace is 1. If successful -# the four blocks will be read into the data-in buffer. Submission queu -# 0 is used (the same queue that Admin commands use). The NVM opcode for -# the Read command is 0x2 and appears in the first command byte. - -02 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 -00 00 00 00 00 00 00 00 fe ff ff ff ff ff ff ff -00 00 00 00 fe ff ff ff 45 23 01 00 00 00 00 00 -03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - -# Notice NVMe uses its quirky "0's based" number of blocks so -# 03 appears at byte offset 48 to mean "read 4 blocks". -# -# A typical invocation in Linux and FreeBSD would look like this: -# sg_raw --cmdfile=nvme_read_ctl.hex --nvm -r 2048 -# --outfile=t.bin /dev/nvme0 -# -# Notice the '--nvm' option which is needed to distiguish a NVM -# command from an Admin command as Admin commands are the default -# in this utility. -# -# This utility (and most others in the package) aligns data-in and -# data-out buffers to the beginning of pages which are 4096 bytes -# long at a minimum. This is the way NVMe likes things as well. diff --git a/examples/nvme_write_ctl.hex b/examples/nvme_write_ctl.hex deleted file mode 100644 index 02b5a377..00000000 --- a/examples/nvme_write_ctl.hex +++ /dev/null @@ -1,38 +0,0 @@ -# 64 byte NVMe, Write command (a NVM command) that is suitable for: -# sg_raw --cmdfile=<this_file_name> --nvm --request=2048 <nvme_device> -# -# The address field (at byte offset 24, 8 bytes and little endian) gives -# special meaning to the highest address pointers: -# ffffffff fffffffe use address of data-in buffer -# ffffffff fffffffd use address of data-out buffer -# -# The data length field (at byte offset 36, 4 bytes and little endian) -# gives special meaning to the highest block counts: -# fffffffe use byte length of data-in buffer -# fffffffd use byte length of data-out buffer -# -# 512 byte logical block size is assumed. Write 4 blocks hence 2048 bytes. -# The first LBA written is 0x12345 and the namespace is 1. If successful the -# four blocks will be written out of the data-out buffer. Submission queue -# is used (the same queue that Admin commands use). The NVM opcode for the -# Write command is 0x1 and appears in the first command byte. - -01 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 -00 00 00 00 00 00 00 00 fd ff ff ff ff ff ff ff -00 00 00 00 fd ff ff ff 45 23 01 00 00 00 00 00 -03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - -# Notice NVMe uses its quirky "0's based" number of blocks so -# 03 appears at byte offset 48 to mean "write 4 blocks". -# -# A typical invocation in Linux and FreeBSD would look like this: -# sg_raw --cmdfile=nvme_write_ctl.hex --nvm -s 2048 -# --infile=t.bin /dev/nvme0 -# -# Notice the '--nvm' option which is needed to distiguish a NVM -# command from an Admin command as Admin commands are the default -# in this utility. -# -# This utility (and most others in the package) aligns data-in and -# data-out buffers to the beginning of pages which are 4096 bytes -# long at a minimum. This is the way NVMe likes things as well. diff --git a/examples/ref_sense.txt b/examples/ref_sense.txt deleted file mode 100644 index 89bca5b7..00000000 --- a/examples/ref_sense.txt +++ /dev/null @@ -1,7 +0,0 @@ -# Test User data segment referral sense data. Values are in hex. -# Invocation: 'sg_decode_sense -f ref_sense.txt' [dpg 20110208] - -72,0,0,0,0,0,0 38 -b,36,1,0 -0,0,0,2,11,11,11,11,22,22,22,22,55,55,55,55,66,66,66,66 1,0,0,7, 2,0,0,8 -0,0,0,1,77,77,77,77,77,77,77,77,88,88,88,88,88,88,88,88, 3,0,0,5 |