€•
^      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ/translations/zh_CN/scsi/hpsa”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/zh_TW/scsi/hpsa”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/it_IT/scsi/hpsa”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/ja_JP/scsi/hpsa”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/ko_KR/scsi/hpsa”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/sp_SP/scsi/hpsa”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒ7/var/lib/git/docbuild/linux/Documentation/scsi/hpsa.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ)HPSA - Hewlett Packard Smart Array driver”h]”hŒ)HPSA - Hewlett Packard Smart Array driver”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒ	paragraph”“”)”}”(hXî  This file describes the hpsa SCSI driver for HP Smart Array controllers.
The hpsa driver is intended to supplant the cciss driver for newer
Smart Array controllers.  The hpsa driver is a SCSI driver, while the
cciss driver is a "block" driver.  Actually cciss is both a block
driver (for logical drives) AND a SCSI driver (for tape drives). This
"split-brained" design of the cciss driver is a source of excess
complexity and eliminating that complexity is one of the reasons
for hpsa to exist.”h]”hXö  This file describes the hpsa SCSI driver for HP Smart Array controllers.
The hpsa driver is intended to supplant the cciss driver for newer
Smart Array controllers.  The hpsa driver is a SCSI driver, while the
cciss driver is a â€œblockâ€ driver.  Actually cciss is both a block
driver (for logical drives) AND a SCSI driver (for tape drives). This
â€œsplit-brainedâ€ design of the cciss driver is a source of excess
complexity and eliminating that complexity is one of the reasons
for hpsa to exist.”…””}”(hhËhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒSupported devices”h]”hŒSupported devices”…””}”(hhÜhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hhÙhžhhŸh³h KubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒSmart Array P212”h]”hÊ)”}”(hhóh]”hŒSmart Array P212”…””}”(hhõhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khhñubah}”(h]”h ]”h"]”h$]”h&]”uh1hïhhìhžhhŸh³h Nubhð)”}”(hŒSmart Array P410”h]”hÊ)”}”(hj
  h]”hŒSmart Array P410”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hïhhìhžhhŸh³h Nubhð)”}”(hŒSmart Array P410i”h]”hÊ)”}”(hj!  h]”hŒSmart Array P410i”…””}”(hj#  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hïhhìhžhhŸh³h Nubhð)”}”(hŒSmart Array P411”h]”hÊ)”}”(hj8  h]”hŒSmart Array P411”…””}”(hj:  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj6  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hïhhìhžhhŸh³h Nubhð)”}”(hŒSmart Array P812”h]”hÊ)”}”(hjO  h]”hŒSmart Array P812”…””}”(hjQ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KhjM  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hïhhìhžhhŸh³h Nubhð)”}”(hŒSmart Array P712m”h]”hÊ)”}”(hjf  h]”hŒSmart Array P712m”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khjd  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hïhhìhžhhŸh³h Nubhð)”}”(hŒSmart Array P711m”h]”hÊ)”}”(hj}  h]”hŒSmart Array P711m”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj{  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hïhhìhžhhŸh³h Nubhð)”}”(hŒStorageWorks P1210m
”h]”hÊ)”}”(hŒStorageWorks P1210m”h]”hŒStorageWorks P1210m”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj’  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hïhhìhžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1hêhŸh³h KhhÙhžhubhÊ)”}”(hŒÿAdditionally, older Smart Arrays may work with the hpsa driver if the kernel
boot parameter "hpsa_allow_any=1" is specified, however these are not tested
nor supported by HP with this driver.  For older Smart Arrays, the cciss
driver should still be used.”h]”hX  Additionally, older Smart Arrays may work with the hpsa driver if the kernel
boot parameter â€œhpsa_allow_any=1â€ is specified, however these are not tested
nor supported by HP with this driver.  For older Smart Arrays, the cciss
driver should still be used.”…””}”(hj²  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KhhÙhžhubhÊ)”}”(hXx  The "hpsa_simple_mode=1" boot parameter may be used to prevent the driver from
putting the controller into "performant" mode.  The difference is that with simple
mode, each command completion requires an interrupt, while with "performant mode"
(the default, and ordinarily better performing) it is possible to have multiple
command completions indicated by a single interrupt.”h]”hX„  The â€œhpsa_simple_mode=1â€ boot parameter may be used to prevent the driver from
putting the controller into â€œperformantâ€ mode.  The difference is that with simple
mode, each command completion requires an interrupt, while with â€œperformant modeâ€
(the default, and ordinarily better performing) it is possible to have multiple
command completions indicated by a single interrupt.”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K!hhÙhžhubeh}”(h]”Œsupported-devices”ah ]”h"]”Œsupported devices”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒHPSA specific entries in /sys”h]”hŒHPSA specific entries in /sys”…””}”(hjÙ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÖ  hžhhŸh³h K(ubhŒblock_quote”“”)”}”(hŒfIn addition to the generic SCSI attributes available in /sys, hpsa supports
the following attributes:
”h]”hÊ)”}”(hŒeIn addition to the generic SCSI attributes available in /sys, hpsa supports
the following attributes:”h]”hŒeIn addition to the generic SCSI attributes available in /sys, hpsa supports
the following attributes:”…””}”(hjí  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K*hjé  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jç  hŸh³h K*hjÖ  hžhubeh}”(h]”Œhpsa-specific-entries-in-sys”ah ]”h"]”Œhpsa specific entries in /sys”ah$]”h&]”uh1h´hh¶hžhhŸh³h K(ubhµ)”}”(hhh]”(hº)”}”(hŒHPSA specific host attributes”h]”hŒHPSA specific host attributes”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj	  hžhhŸh³h K.ubjè  )”}”(hXB  ::

  /sys/class/scsi_host/host*/rescan
  /sys/class/scsi_host/host*/firmware_revision
  /sys/class/scsi_host/host*/resettable
  /sys/class/scsi_host/host*/transport_mode

the host "rescan" attribute is a write only attribute.  Writing to this
attribute will cause the driver to scan for new, changed, or removed devices
(e.g. hot-plugged tape drives, or newly configured or deleted logical drives,
etc.) and notify the SCSI midlayer of any changes detected.  Normally this is
triggered automatically by HP's Array Configuration Utility (either the GUI or
command line variety) so for logical drive changes, the user should not
normally have to use this.  It may be useful when hot plugging devices like
tape drives, or entire storage boxes containing pre-configured logical drives.

The "firmware_revision" attribute contains the firmware version of the Smart Array.
For example::

      root@host:/sys/class/scsi_host/host4# cat firmware_revision
      7.14

The transport_mode indicates whether the controller is in "performant"
or "simple" mode.  This is controlled by the "hpsa_simple_mode" module
parameter.

The "resettable" read-only attribute indicates whether a particular
controller is able to honor the "reset_devices" kernel parameter.  If the
device is resettable, this file will contain a "1", otherwise, a "0".  This
parameter is used by kdump, for example, to reset the controller at driver
load time to eliminate any outstanding commands on the controller and get the
controller into a known state so that the kdump initiated i/o will work right
and not be disrupted in any way by stale commands or other stale state
remaining on the controller from the previous kernel.  This attribute enables
kexec tools to warn the user if they attempt to designate a device which is
unable to honor the reset_devices kernel parameter as a dump device.
”h]”(hŒliteral_block”“”)”}”(hŒž/sys/class/scsi_host/host*/rescan
/sys/class/scsi_host/host*/firmware_revision
/sys/class/scsi_host/host*/resettable
/sys/class/scsi_host/host*/transport_mode”h]”hŒž/sys/class/scsi_host/host*/rescan
/sys/class/scsi_host/host*/firmware_revision
/sys/class/scsi_host/host*/resettable
/sys/class/scsi_host/host*/transport_mode”…””}”hj   sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h K2hj  ubhÊ)”}”(hXb  the host "rescan" attribute is a write only attribute.  Writing to this
attribute will cause the driver to scan for new, changed, or removed devices
(e.g. hot-plugged tape drives, or newly configured or deleted logical drives,
etc.) and notify the SCSI midlayer of any changes detected.  Normally this is
triggered automatically by HP's Array Configuration Utility (either the GUI or
command line variety) so for logical drive changes, the user should not
normally have to use this.  It may be useful when hot plugging devices like
tape drives, or entire storage boxes containing pre-configured logical drives.”h]”hXh  the host â€œrescanâ€ attribute is a write only attribute.  Writing to this
attribute will cause the driver to scan for new, changed, or removed devices
(e.g. hot-plugged tape drives, or newly configured or deleted logical drives,
etc.) and notify the SCSI midlayer of any changes detected.  Normally this is
triggered automatically by HPâ€™s Array Configuration Utility (either the GUI or
command line variety) so for logical drive changes, the user should not
normally have to use this.  It may be useful when hot plugging devices like
tape drives, or entire storage boxes containing pre-configured logical drives.”…””}”(hj.  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K7hj  ubhÊ)”}”(hŒaThe "firmware_revision" attribute contains the firmware version of the Smart Array.
For example::”h]”hŒdThe â€œfirmware_revisionâ€ attribute contains the firmware version of the Smart Array.
For example:”…””}”(hj<  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K@hj  ubj  )”}”(hŒ@root@host:/sys/class/scsi_host/host4# cat firmware_revision
7.14”h]”hŒ@root@host:/sys/class/scsi_host/host4# cat firmware_revision
7.14”…””}”hjJ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h KChj  ubhÊ)”}”(hŒ˜The transport_mode indicates whether the controller is in "performant"
or "simple" mode.  This is controlled by the "hpsa_simple_mode" module
parameter.”h]”hŒ¤The transport_mode indicates whether the controller is in â€œperformantâ€
or â€œsimpleâ€ mode.  This is controlled by the â€œhpsa_simple_modeâ€ module
parameter.”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KFhj  ubhÊ)”}”(hXæ  The "resettable" read-only attribute indicates whether a particular
controller is able to honor the "reset_devices" kernel parameter.  If the
device is resettable, this file will contain a "1", otherwise, a "0".  This
parameter is used by kdump, for example, to reset the controller at driver
load time to eliminate any outstanding commands on the controller and get the
controller into a known state so that the kdump initiated i/o will work right
and not be disrupted in any way by stale commands or other stale state
remaining on the controller from the previous kernel.  This attribute enables
kexec tools to warn the user if they attempt to designate a device which is
unable to honor the reset_devices kernel parameter as a dump device.”h]”hXö  The â€œresettableâ€ read-only attribute indicates whether a particular
controller is able to honor the â€œreset_devicesâ€ kernel parameter.  If the
device is resettable, this file will contain a â€œ1â€, otherwise, a â€œ0â€.  This
parameter is used by kdump, for example, to reset the controller at driver
load time to eliminate any outstanding commands on the controller and get the
controller into a known state so that the kdump initiated i/o will work right
and not be disrupted in any way by stale commands or other stale state
remaining on the controller from the previous kernel.  This attribute enables
kexec tools to warn the user if they attempt to designate a device which is
unable to honor the reset_devices kernel parameter as a dump device.”…””}”(hjf  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KJhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jç  hŸh³h K0hj	  hžhubhµ)”}”(hhh]”(hº)”}”(hŒHPSA specific disk attributes”h]”hŒHPSA specific disk attributes”…””}”(hj}  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjz  hžhhŸh³h KVubjè  )”}”(hXû  ::

  /sys/class/scsi_disk/c:b:t:l/device/unique_id
  /sys/class/scsi_disk/c:b:t:l/device/raid_level
  /sys/class/scsi_disk/c:b:t:l/device/lunid

(where c:b:t:l are the controller, bus, target and lun of the device)

For example::

      root@host:/sys/class/scsi_disk/4:0:0:0/device# cat unique_id
      600508B1001044395355323037570F77
      root@host:/sys/class/scsi_disk/4:0:0:0/device# cat lunid
      0x0000004000000000
      root@host:/sys/class/scsi_disk/4:0:0:0/device# cat raid_level
      RAID 0
”h]”(j  )”}”(hŒ†/sys/class/scsi_disk/c:b:t:l/device/unique_id
/sys/class/scsi_disk/c:b:t:l/device/raid_level
/sys/class/scsi_disk/c:b:t:l/device/lunid”h]”hŒ†/sys/class/scsi_disk/c:b:t:l/device/unique_id
/sys/class/scsi_disk/c:b:t:l/device/raid_level
/sys/class/scsi_disk/c:b:t:l/device/lunid”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h KZhj‹  ubhÊ)”}”(hŒE(where c:b:t:l are the controller, bus, target and lun of the device)”h]”hŒE(where c:b:t:l are the controller, bus, target and lun of the device)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K^hj‹  ubhÊ)”}”(hŒFor example::”h]”hŒFor example:”…””}”(hj«  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K`hj‹  ubj  )”}”(hŒîroot@host:/sys/class/scsi_disk/4:0:0:0/device# cat unique_id
600508B1001044395355323037570F77
root@host:/sys/class/scsi_disk/4:0:0:0/device# cat lunid
0x0000004000000000
root@host:/sys/class/scsi_disk/4:0:0:0/device# cat raid_level
RAID 0”h]”hŒîroot@host:/sys/class/scsi_disk/4:0:0:0/device# cat unique_id
600508B1001044395355323037570F77
root@host:/sys/class/scsi_disk/4:0:0:0/device# cat lunid
0x0000004000000000
root@host:/sys/class/scsi_disk/4:0:0:0/device# cat raid_level
RAID 0”…””}”hj¹  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h Kbhj‹  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jç  hŸh³h KXhjz  hžhubeh}”(h]”Œhpsa-specific-disk-attributes”ah ]”h"]”Œhpsa specific disk attributes”ah$]”h&]”uh1h´hj	  hžhhŸh³h KVubeh}”(h]”Œhpsa-specific-host-attributes”ah ]”h"]”Œhpsa specific host attributes”ah$]”h&]”uh1h´hh¶hžhhŸh³h K.ubhµ)”}”(hhh]”(hº)”}”(hŒHPSA specific ioctls”h]”hŒHPSA specific ioctls”…””}”(hjà  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÝ  hžhhŸh³h Kjubjè  )”}”(hX$  For compatibility with applications written for the cciss driver, many, but
not all of the ioctls supported by the cciss driver are also supported by the
hpsa driver.  The data structures used by these are described in
include/linux/cciss_ioctl.h

CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD
      The above three ioctls all do exactly the same thing, which is to cause the driver
      to rescan for new devices.  This does exactly the same thing as writing to the
      hpsa specific host "rescan" attribute.

CCISS_GETPCIINFO
      Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID).

CCISS_GETDRIVVER
      Returns driver version in three bytes encoded as::

              (major_version << 16) | (minor_version << 8) | (subminor_version)

CCISS_PASSTHRU, CCISS_BIG_PASSTHRU
      Allows "BMIC" and "CISS" commands to be passed through to the Smart Array.
      These are used extensively by the HP Array Configuration Utility, SNMP storage
      agents, etc.  See cciss_vol_status at http://cciss.sf.net for some examples.”h]”(hÊ)”}”(hŒöFor compatibility with applications written for the cciss driver, many, but
not all of the ioctls supported by the cciss driver are also supported by the
hpsa driver.  The data structures used by these are described in
include/linux/cciss_ioctl.h”h]”hŒöFor compatibility with applications written for the cciss driver, many, but
not all of the ioctls supported by the cciss driver are also supported by the
hpsa driver.  The data structures used by these are described in
include/linux/cciss_ioctl.h”…””}”(hjò  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Klhjî  ubhŒdefinition_list”“”)”}”(hhh]”(hŒdefinition_list_item”“”)”}”(hŒúCCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD
The above three ioctls all do exactly the same thing, which is to cause the driver
to rescan for new devices.  This does exactly the same thing as writing to the
hpsa specific host "rescan" attribute.
”h]”(hŒterm”“”)”}”(hŒ0CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD”h]”hŒ0CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h Kthj  ubhŒ
definition”“”)”}”(hhh]”hÊ)”}”(hŒÈThe above three ioctls all do exactly the same thing, which is to cause the driver
to rescan for new devices.  This does exactly the same thing as writing to the
hpsa specific host "rescan" attribute.”h]”hŒÌThe above three ioctls all do exactly the same thing, which is to cause the driver
to rescan for new devices.  This does exactly the same thing as writing to the
hpsa specific host â€œrescanâ€ attribute.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Krhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h Kthj  ubj  )”}”(hŒaCCISS_GETPCIINFO
Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID).
”h]”(j  )”}”(hŒCCISS_GETPCIINFO”h]”hŒCCISS_GETPCIINFO”…””}”(hj>  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h Kwhj:  ubj  )”}”(hhh]”hÊ)”}”(hŒOReturns PCI domain, bus, device and function and "board ID" (PCI subsystem ID).”h]”hŒSReturns PCI domain, bus, device and function and â€œboard IDâ€ (PCI subsystem ID).”…””}”(hjO  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KwhjL  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj:  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h Kwhj  ubj  )”}”(hŒCCISS_GETDRIVVER
Returns driver version in three bytes encoded as::

        (major_version << 16) | (minor_version << 8) | (subminor_version)
”h]”(j  )”}”(hŒCCISS_GETDRIVVER”h]”hŒCCISS_GETDRIVVER”…””}”(hjm  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h K|hji  ubj  )”}”(hhh]”(hÊ)”}”(hŒ2Returns driver version in three bytes encoded as::”h]”hŒ1Returns driver version in three bytes encoded as:”…””}”(hj~  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kzhj{  ubj  )”}”(hŒA(major_version << 16) | (minor_version << 8) | (subminor_version)”h]”hŒA(major_version << 16) | (minor_version << 8) | (subminor_version)”…””}”hjŒ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1j  hŸh³h K|hj{  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hji  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h K|hj  ubj  )”}”(hX	  CCISS_PASSTHRU, CCISS_BIG_PASSTHRU
Allows "BMIC" and "CISS" commands to be passed through to the Smart Array.
These are used extensively by the HP Array Configuration Utility, SNMP storage
agents, etc.  See cciss_vol_status at http://cciss.sf.net for some examples.”h]”(j  )”}”(hŒ"CCISS_PASSTHRU, CCISS_BIG_PASSTHRU”h]”hŒ"CCISS_PASSTHRU, CCISS_BIG_PASSTHRU”…””}”(hjª  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h K€hj¦  ubj  )”}”(hhh]”hÊ)”}”(hŒæAllows "BMIC" and "CISS" commands to be passed through to the Smart Array.
These are used extensively by the HP Array Configuration Utility, SNMP storage
agents, etc.  See cciss_vol_status at http://cciss.sf.net for some examples.”h]”(hŒÈAllows â€œBMICâ€ and â€œCISSâ€ commands to be passed through to the Smart Array.
These are used extensively by the HP Array Configuration Utility, SNMP storage
agents, etc.  See cciss_vol_status at ”…””}”(hj»  hžhhŸNh NubhŒ	reference”“”)”}”(hŒhttp://cciss.sf.net”h]”hŒhttp://cciss.sf.net”…””}”(hjÅ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÇ  uh1jÃ  hj»  ubhŒ for some examples.”…””}”(hj»  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj¸  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj¦  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h K€hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j   hjî  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jç  hŸh³h KlhjÝ  hžhubeh}”(h]”Œhpsa-specific-ioctls”ah ]”h"]”Œhpsa specific ioctls”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kjubeh}”(h]”Œ'hpsa-hewlett-packard-smart-array-driver”ah ]”h"]”Œ)hpsa - hewlett packard smart array driver”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j)  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j  j   jÓ  jÐ  j  j  jÚ  j×  jÒ  jÏ  jû  jø  uŒ	nametypes”}”(j  ‰jÓ  ‰j  ‰jÚ  ‰jÒ  ‰jû  ‰uh}”(j   h¶jÐ  hÙj  jÖ  j×  j	  jÏ  jz  jø  jÝ  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.