| /openbmc/sdbusplus/test/server/ |
| H A D | object.cpp | 38 // Simulate the typical usage of a service in TEST_F()
62 // Simulate the typical usage of a service in TEST_F()
94 // Simulate the typical usage of a service in TEST_F()
124 // Simulate the typical usage of a service in TEST_F()
149 // Simulate the typical usage of a service in TEST_F()
|
| /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-fan-presence/presence/ |
| H A D | psensor.hpp | 40 * for detecting presence. Typical implementations
52 * state change notifications. Typical implementations
|
| /openbmc/gpioplus/ |
| H A D | README.md | 16 For a test / debug build, a typical configuration is
|
| /openbmc/openbmc/poky/meta-yocto-bsp/conf/machine/ |
| H A D | genericx86.conf | 3 …. Supports a moderately wide range of drivers that should boot and be usable on "typical" hardware.
|
| H A D | genericx86-64.conf | 3 …. Supports a moderately wide range of drivers that should boot and be usable on "typical" hardware.
|
| /openbmc/sdeventplus/ |
| H A D | README.md | 21 For a test / debug build, a typical configuration is
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/ |
| H A D | MeetsMinimumShipLevel.interface.yaml | 7 that do or do not meet the MSL. Typical reactions might be to prevent a
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/ |
| H A D | ActivationBlocksTransition.interface.yaml | 7 A typical use of this would be to prevent (delay) the power-on of a managed
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | ErrorBlocksTransition.interface.yaml | 7 A typical use of this would be to prevent the power-on of a managed host
|
| /openbmc/openpower-hw-diags/ |
| H A D | README.md | 20 For a test / debug build, a typical configuration is:
|
| /openbmc/u-boot/tools/binman/etype/ |
| H A D | intel_refcode.py | 18 This is executed by U-Boot when needed early during startup. A typical
|
| H A D | intel_mrc.py | 18 is executed by U-Boot when needed early during startup. A typical filename
|
| H A D | intel_me.py | 23 A typical filename is 'me.bin'.
|
| /openbmc/openbmc/poky/meta-skeleton/recipes-kernel/linux/linux-yocto-custom/ |
| H A D | 0001-linux-version-tweak.patch | 26 # To see a list of typical targets execute "make help"
|
| /openbmc/u-boot/arch/arm/mach-at91/include/mach/ |
| H A D | at91_gpbr.h | 24 * known typical uses of the GPBRs:
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/xrdp/xrdp/ |
| H A D | 0001-Added-req_distinguished_name-in-etc-xrdp-openssl.con.patch | 32 # Extensions for a typical CA - PKIX recommendation.
|
| /openbmc/qemu/docs/system/ |
| H A D | linuxboot.rst | 22 ``-nographic`` option. The typical command line is:
|
| /openbmc/u-boot/doc/ |
| H A D | README.commands.spl | 16 TYPICAL CALL
|
| H A D | README.pblimage | 70 Typical example of rcw.cfg file:
81 Typical example of pbi.cfg file:
|
| /openbmc/openbmc-tools/tof-voters/ |
| H A D | README.md | 11 The typical use of the tool is something like this:
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/celt051/ |
| H A D | celt051_git.bb | 9 on the signal, even less than is typical for speech centric formats \
|
| /openbmc/phosphor-dbus-interfaces/ |
| H A D | README.md | 11 This project can be built with `meson`. The typical `meson` workflow is:
|
| /openbmc/openbmc/poky/scripts/pybootchartgui/ |
| H A D | README.pybootchart | 22 A typical boot sequence consists of several hundred processes. Since
|
| /openbmc/qemu/docs/devel/ |
| H A D | secure-coding-practices.rst | 46 accesses and data read from guest memory must be validated. A typical example
75 typical "theory of operation" presented in driver writer manuals. The guest
|