| /openbmc/phosphor-fan-presence/presence/ |
| H A D | psensor.hpp | 16 * Provide concrete implementations of PresenceSensor to realize
19 * Note that implementations drive the inventory update process via
39 * Implementations should peform any preparation
40 * for detecting presence. Typical implementations
51 * Implementations should stop issuing presence
52 * state change notifications. Typical implementations
61 * Implementations should perform an offline (the start
72 * Implementations should log an an event if the
|
| H A D | rpolicy.hpp | 19 * Provide concrete implementations of RedundancyPolicy to realize
50 * a change of presence. Implementations should update
61 * Implementations should start monitoring the sensors
|
| /openbmc/u-boot/drivers/crypto/ |
| H A D | Kconfig | 20 requiring the SHA software implementations, saving code size.
33 SHA software implementations, saving code size.
43 software implementations, saving code size.
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | tftpy_0.8.5.bb | 1 …e Python programming language. It includes client and server classes, with sample implementations."
3 includes client and server classes, with sample implementations. Hooks are \
|
| H A D | python3-keras-applications_1.0.8.bb | 1 SUMMARY = "Reference implementations of popular deep learning models"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/libc-bench/ |
| H A D | libc-bench_git.bb | 1 SUMMARY = "Tests to compare standard functions of different libc implementations"
3 implementations of various C/POSIX standard library functions."
|
| /openbmc/qemu/scripts/ |
| H A D | compare-machine-types.py | 84 def set_implementations(self, implementations: List['Driver']) -> None:
85 self.implementations = implementations
92 def set_implementations(self, implementations: List[Driver]) -> None:
93 self.implementations = implementations
99 for impl in implementations:
189 # only implementations inherit property getter
205 return [impl.name for impl in self.drivers[driver].implementations]
211 implementations)
220 # values from abstract class to all implementations
298 x86_64-cpu) this script will compare all implementations of this class.
|
| /openbmc/qemu/plugins/ |
| H A D | api-user.c | 2 * QEMU Plugin API - user-mode only implementations
5 * implementations or are only relevant to user-mode.
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp.md | 69 implementations in host firmware, which have widely varying runtime
75 - Be usable over simple hardware implementations, but have a facility for higher
110 firmware), this is may not be feasible for all host firmware implementations
126 and managed device implementations.
|
| H A D | mctp-userspace.md | 30 2. one or more binding implementations (eg, MCTP-over-serial), which interact
46 binding implementations. Most of these would be included in the library source
59 These "lower" binding implementations may have very different methods of
|
| /openbmc/phosphor-dbus-monitor/src/ |
| H A D | watch.hpp | 17 * or initialization. Typical implementations might register dbus
22 * their setup. Typical implementations will forward the call
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | VoltageRegulatorMode.interface.yaml | 5 where the VR has a well defined default, implementations should place the
12 if the VR itself defines the interfaces. Implementations may implement this
|
| H A D | Mode.interface.yaml | 6 however not all implementations may respect having this property set
|
| /openbmc/phosphor-host-ipmid/include/ipmid-host/ |
| H A D | cmd-utils.hpp | 38 * implementations may then broadcast an agreed signal
43 * different implementations. Users of Manager will supply
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/cim-schema/files/ |
| H A D | LICENSE | 29 // for such implementations.
33 // or impact implementations of DMTF standards, visit
|
| /openbmc/openbmc/meta-openembedded/meta-networking/licenses/ |
| H A D | DMTF | 29 // for such implementations.
33 // or impact implementations of DMTF standards, visit
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/bearssl/ |
| H A D | bearssl_0.6.bb | 6 algorithm implementations are constant-time by default. \
15 algorithm implementations to be added afterwards, possibly from third \
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/ |
| H A D | MeetsMinimumShipLevel.interface.yaml | 6 There are no requirements on how implementations react to inventory items
|
| /openbmc/u-boot/drivers/scsi/ |
| H A D | sandbox_scsi.c | 6 * This file contains dummy implementations of SCSI functions requried so
|
| /openbmc/qemu/hw/vfio/ |
| H A D | types.h | 13 * between VFIO implementations that use a kernel driver
|
| /openbmc/qemu/bsd-user/ |
| H A D | plugin-api.c | 2 * QEMU Plugin API - bsd-user-mode only implementations
|
| /openbmc/qemu/linux-user/ |
| H A D | plugin-api.c | 2 * QEMU Plugin API - linux-user-mode only implementations
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | redfish-schema-v1.json | 33 "description": "The term shall be applied to a property in order to specify that the property is deprecated. The value of the string should explain the deprecation, including new property or properties to be used. The property can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated properties are likely to be removed in a future major version of the schema."
53 "description": "The term shall be applied to a value in order to specify that the value is deprecated. The value of the string should explain the deprecation, including new value to be used. The value can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated values are likely to be removed in a future major version of the schema."
|
| H A D | redfish-schema.v1_10_1.json | 33 …. The property can be supported in new and existing implementations, but usage in new implementati…
53 …ed. The value can be supported in new and existing implementations, but usage in new implementati…
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | redfish-schema.v1_10_1.json | 33 …. The property can be supported in new and existing implementations, but usage in new implementati…
53 …ed. The value can be supported in new and existing implementations, but usage in new implementati…
|