Browse Source

[doc] Clarify custom hardware manager inheritance

Change-Id: I94657967763f058fccd4f19656925d02cd8973b8
changes/02/752002/1
Arne Wiebalck 2 weeks ago
parent
commit
9dd968fa30
1 changed files with 7 additions and 6 deletions
  1. +7
    -6
      doc/source/contributor/hardware_managers.rst

+ 7
- 6
doc/source/contributor/hardware_managers.rst View File

@@ -32,12 +32,13 @@ server).

How can I build a custom HardwareManager?
-----------------------------------------
Custom HardwareManagers should subclass hardware.HardwareManager or
hardware.GenericHardwareManager. The only required method is
evaluate_hardware_support(), which should return one of the enums
in hardware.HardwareSupport. Hardware support determines which hardware
manager is executed first for a given function (see: "`How are methods
executed on HardwareManagers?`_" for more info). Common methods you
In general, custom HardwareManagers should subclass hardware.HardwareManager.
Subclassing hardware.GenericHardwareManager should only be considered if the
aim is to raise the priority of all methods of the GenericHardwareManager.
The only required method is evaluate_hardware_support(), which should return
one of the enums in hardware.HardwareSupport. Hardware support determines
which hardware manager is executed first for a given function (see: "`How are
methods executed on HardwareManagers?`_" for more info). Common methods you
may want to implement are ``list_hardware_info()``, to add additional hardware
the GenericHardwareManager is unable to identify and ``erase_devices()``, to
erase devices in ways other than ATA secure erase or shredding.


Loading…
Cancel
Save