Home
last modified time | relevance | path

Searched full:mechanism (Results 1 – 25 of 520) sorted by relevance

12345678910>>...21

/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/dbus/
H A Dphosphor-dbus-monitor_%.bbappend7 file://fan-rotor-fail-mechanism \
8 file://fan-rotor-fail-mechanism.service \
9 file://fan-rotor-missing-mechanism \
10 file://fan-rotor-missing-mechanism.service \
28 install -m 0755 ${UNPACKDIR}/fan-rotor-fail-mechanism ${D}${libexecdir}/${PN}/
29 install -m 0755 ${UNPACKDIR}/fan-rotor-missing-mechanism ${D}${libexecdir}/${PN}/
/openbmc/docs/designs/
H A Dfirmware-update-via-blobs.md9 The BMC needs a mechanism for receiving a new firmware image from the host
19 update mechanism that can be done in-band between the host and the BMC.
39 - Any update mechanism must provide support for UBI tarballs and legacy (static
41 support for any image type simply by implementing a mechanism for handling it.
43 - Any update mechanism must allow for triggering an image verification step
46 - Any update mechanism must allow implementing the data staging via different
49 - Any update mechanism must provide a handshake or equivalent protocol for
54 - Any update mechanism must attempt to maintain security, insomuch as not
82 layout) or the UBI mechanism, or both. The flags provided to the open command
83 identify the mechanism selected by the client-side. The stat command will return
[all …]
H A Dbmc-service-failure-debug-and-recovery.md112 | Condition | Mechanism |
131 | Condition | Mechanism |
163 | Severity | BMC Recovery Mechanism | Used for …
180 The need to escalate above mechanism 1 should come with data that captures why
184 in the reset. Therefore, mechanism 2 should exist in the system design and its
193 mechanism, support for 2 can be implemented in BMC userspace.
195 Mechanism 1 is typically initiated by the usual in-band interfaces, either IPMI
196 or PLDM. In order to avoid these in the implementation of mechanism 2, the host
202 #### Behavioural Requirements for Recovery Mechanism 2
204 The system behaviour requirement for the mechanism is:
[all …]
H A Dfail-boot-on-hw-error.md20 OpenBMC firmware needs a mechanism to support this use case.
39 - Provide a mechanism to cause the OpenBMC firmware to halt a system if a
41 - The mechanism to enable/disable this feature does not need to be an external
55 - Ensure the mechanism used to halt firmware on inventory callouts can also be
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-printing/cups/cups-pk-helper/
H A Ddont-localize-org.opensuse.CupsPkHelper.Mechanism.service.patch10 - input: 'org.opensuse.cupspkhelper.mechanism.policy.in',
11 - output: 'org.opensuse.cupspkhelper.mechanism.policy',
19 +# input: 'org.opensuse.cupspkhelper.mechanism.policy.in',
20 +# output: 'org.opensuse.cupspkhelper.mechanism.policy',
/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/
H A Ddata_handler.hpp11 * Each data transport mechanism must implement the DataInterface.
19 * Initialize data transport mechanism. Calling this should be idempotent
27 * Close the data transport mechanism.
53 * the mechanism.
/openbmc/qemu/docs/system/
H A Dvnc-security.rst121 strength of the authentication depends on the exact mechanism
122 configured. If the chosen mechanism also provides a SSF layer, then it
125 Refer to the later docs on how to choose the exact SASL mechanism used
138 If the desired SASL authentication mechanism does not supported SSF
158 implementation or host. When SASL is enabled, the mechanism
165 encryption, otherwise the SASL mechanism will have to provide
167 used is drastically reduced. In fact only the GSSAPI SASL mechanism
169 versions of QEMU referred to the DIGEST-MD5 mechanism, however, it has
171 never be used any more. The SCRAM-SHA-256 mechanism provides a simple
182 This says to use the 'GSSAPI' mechanism with the Kerberos v5 protocol,
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-printing/cups/
H A Dcups-pk-helper_0.2.7.bb14 file://dont-localize-org.opensuse.CupsPkHelper.Mechanism.service.patch \
20 …S}/src/org.opensuse.cupspkhelper.mechanism.policy.in ${D}${datadir}/polkit-1/actions/org.opensuse.…
/openbmc/phosphor-ipmi-flash/
H A DREADME.md1 # Secure Flash Update Mechanism
4 update mechanism.
96 …ipmipci`, `ipminet`, `ipmipci-skip-bridge-disable` | The data transport mechanism, typically `ipmi…
101 If you're using an LPC data transfer mechanism, you'll need two additional
105 If you're using a net data transfer mechanism, you'll also need two additional
131 The image flashing mechanism itself is the initramfs stage during reboot. It
163 transfer the data. By default, the data-in-IPMI mechanism is enabled.
188 If a platform enables p2a as the transport mechanism, a specific vendor must be
196 If a platform enables lpc as the transport mechanism, a specific vendor must be
205 A platform may also enable the network transport mechanism.
[all …]
H A Dstatus.hpp9 /** The status of the update mechanism or the verification mechanism */
/openbmc/qemu/include/hw/riscv/
H A Dboot_opensbi.h48 * lottery mechanism can potentially overwrite the previous booting
56 * to use the relocation lottery mechanism.
78 * lottery mechanism can potentially overwrite the previous booting
86 * to use the relocation lottery mechanism.
/openbmc/u-boot/drivers/i2c/muxes/
H A DKconfig6 one of several buses using some sort of control mechanism. The
15 one of several buses using some sort of control mechanism. The
25 response mechanism where masters have to claim the bus by asserting
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/dbus/phosphor-dbus-monitor/
H A Dfan-rotor-fail-mechanism.service2 Description=Add an event log for the fan fail mechanism then shut down 8 hosts.
6 ExecStart=/usr/libexec/phosphor-dbus-monitor/fan-rotor-fail-mechanism
/openbmc/qemu/docs/system/i386/
H A Dkvm-pv.rst45 Enable asynchronous page fault mechanism. Supported since Linux v2.6.38.
61 Enable paravirtualized TLB flush mechanism. Supported since Linux v4.16.
64 Enable paravirtualized IPI mechanism. Supported since Linux v4.19.
74 Enable interrupt based asynchronous page fault mechanism. Supported since Linux
/openbmc/qemu/
H A Dqemu.sasl2 # pick a mechanism which provides session encryption as well
11 # NB, previously DIGEST-MD5 was set as the default mechanism for
34 # mechanism this can be commented out.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-networking/cyrus-sasl/cyrus-sasl/
H A Dsaslauthd.conf5 # Mechanism to use when checking passwords. Run "saslauthd -v" to get a list
6 # of which mechanism your installation was compiled with the ablity to use.
H A D0001-sample-Rename-dprintf-to-cyrus_dprintf.patch36 - dprintf(1, "using mechanism %s\n", chosenmech);
37 + cyrus_dprintf(1, "using mechanism %s\n", chosenmech);
40 the mechanism chosen, the presence of initial response,
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/
H A Dlibxcomposite_0.4.6.bb8 an automatic mechanism for presenting those contents within the parent \
9 window. In external parent, a mechanism for providing redirection of \
/openbmc/openbmc/meta-security/meta-tpm/recipes-tpm1/tpm-quote-tools/
H A Dtpm-quote-tools_1.0.4.bb2 for TPM based attestation using the TPM quote mechanism. \
5 for TPM based attestation using the TPM quote mechanism. The manual \
/openbmc/qemu/docs/devel/
H A Drcu.rst4 Read-copy update (RCU) is a synchronization mechanism that is used to
17 RCU is fundamentally a "wait-to-finish" mechanism. The read side marks
27 the system will have a single instance of the RCU mechanism; a single
28 mechanism can be used for an arbitrary number of "things", without
142 synchronization mechanism.
162 synchronization mechanism to coordinate the accesses.
167 Mark a thread as taking part in the RCU mechanism. Such a thread
172 Mark a thread as not taking part anymore in the RCU mechanism.
244 may be used as a restricted reference-counting mechanism. For example,
325 ``foo_unref`` could use a mechanism such as bottom halves to move deallocation
/openbmc/u-boot/include/
H A Dmailbox.h10 * A mailbox is a hardware mechanism for transferring small fixed-size messages
15 * mechanism. When data transfer is implemented, it is via HW registers or
20 * A mailbox channel is a bi-directional mechanism that can send a message or
73 * mechanism.
91 * mechanism.
/openbmc/u-boot/arch/x86/include/asm/
H A Dirq.h12 * Intel interrupt router configuration mechanism
14 * There are two known ways of Intel interrupt router configuration mechanism
/openbmc/qemu/docs/system/devices/
H A Divshmem-flat.rst26 shared memory, the interrupt mechanism is optional. If no input IRQ is
29 the IRQ mechanism is disabled). The shared memory region is always present.
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/blueman/
H A Dblueman_2.4.4.bb20 SYSTEMD_SERVICE:${PN} = "${BPN}-mechanism.service"
54 ${D}${prefix}/libexec/blueman-mechanism \
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/ssmtp/ssmtp/
H A D0001-ssmtp-Correct-the-null-pointer-assignment-to-char-po.patch26 -char *auth_method = (char)NULL; /* Mechanism for SMTP authentication */
31 +char *auth_method = NULL; /* Mechanism for SMTP authentication */

12345678910>>...21