/openbmc/qemu/tests/keys/ |
H A D | README | 6 ONLY in situations that cannot be compromised by external network clients.
|
/openbmc/docs/designs/ |
H A D | target-fail-monitoring.md | 20 There are situations where OpenBMC systemd targets fail. They fail due to a 23 but in some situations (segfault, unhandled exception, unhandled error path, 173 fails. This will be viewable by owners of the system. There may be situations
|
H A D | power-recovery.md | 21 reset to the BMC in situations where it is hung or not responding. In these 22 situations, the user may wish for the system to not automatically power on the 72 These options are only checked and enforced in situations where the BMC does not 87 In situations where the BMC or the system have gotten into a bad state, and the 126 - Power system off as quickly as situations requires (or gracefully handle the
|
/openbmc/u-boot/doc/device-tree-bindings/net/ |
H A D | fixed-link.txt | 5 normal MDIO-managed PHY device. For those situations, a Device Tree
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/p910nd/ |
H A D | p910nd_0.97.bb | 1 DESCRIPTION = "A small network printer daemon for embedded situations that passes the job directly …
|
/openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/ |
H A D | SBE.interface.yaml | 8 unresponsive. In such situations, the debug data needs to be collected from
|
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gnome/tracker/tinysparql/ |
H A D | 0001-fix-reproducibility.patch | 55 # Global build root is required to detect noinst situations (tests/introspection), 85 # Global build root is required to detect noinst situations (tests/introspection),
|
/openbmc/openbmc/poky/meta/recipes-kernel/linux/ |
H A D | linux-dummy.bb | 3 provider for virtual/kernel to satisfy dependencies for situations \
|
/openbmc/u-boot/doc/ |
H A D | README.displaying-bmps | 6 make sure all data is properly aligned, and in many situations simply choosing
|
/openbmc/openbmc/meta-phosphor/recipes-core/systemd/phosphor-systemd-policy/ |
H A D | service-restart-policy.conf | 19 # it's even more challenged. Recent failures have shown situations where
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/monit/ |
H A D | monit_5.35.2.bb | 4 causal actions in error situations."
|
/openbmc/witherspoon-pfault-analysis/ |
H A D | names_values.hpp | 17 * situations like error log metadata.
|
/openbmc/phosphor-power/ |
H A D | names_values.hpp | 17 * situations like error log metadata.
|
/openbmc/qemu/docs/user/ |
H A D | main.rst | 125 This slows down emulation a lot, but can be useful in some situations, 270 This slows down emulation a lot, but can be useful in some situations,
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | development-shell.rst | 81 forwarding and similar situations.
|
H A D | libraries.rst | 235 There are be situations where you need to install and use multiple versions 239 library. To accommodate these situations, you can install multiple
|
/openbmc/openbmc/poky/meta/recipes-core/musl/musl/ |
H A D | 0001-Make-dynamic-linker-a-relative-symlink-to-libc.patch | 10 in such situations to feed into cross builds.
|
/openbmc/sdbusplus/include/sdbusplus/server/ |
H A D | interface.hpp | 33 * unique to prevent name collisions in multiple-inheritence situations.
|
/openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
H A D | power_loss.md | 12 situations, the standby voltage rails are still powered on but the main voltage
|
/openbmc/phosphor-state-manager/ |
H A D | README.md | 11 in situations where the BMC is rebooted and the chassis or host are in 114 In situations where the BMC is reset and the chassis and host are on and
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/tayga/files/ |
H A D | tayga.conf | 50 # recommended in most situations, but all lengths specified in RFC 6052 are
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/lvm2/files/ |
H A D | lvm.conf | 127 # Don't use this in low memory situations (can deadlock). 283 # supported under low memory situations - the machine could lock up.
|
/openbmc/qemu/include/qemu/ |
H A D | coroutine-core.h | 131 * ones have already been entered. In such situations this function can be
|
/openbmc/docs/tof/ |
H A D | contract.md | 119 situations, potentially sensitive topics. Sensitive topics would be topics
|
/openbmc/qemu/include/user/ |
H A D | safe-syscall.h | 66 * situations (like 'open') also need to be handled this way.
|