Home
last modified time | relevance | path

Searched refs:managed (Results 1 – 25 of 237) sorted by relevance

12345678910

/openbmc/openbmc/meta-phosphor/conf/machine/include/
H A Dobmc-evb-common.inc2 # managed host. Enable this machine override to allow other recipes to know
/openbmc/openbmc/poky/meta/recipes-kernel/systemtap/systemtap/
H A D0001-Install-python-modules-to-correct-library-dir.patch42 --single-version-externally-managed \
51 --single-version-externally-managed \
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/
H A DREADME.md14 controls and updates the BIOS flash module for a managed host.
62 software versions that are currently present on the managed inventory
122 - Host - The image is the primary firmware for the managed host contained on
139 the image was valid for a managed element, a detailed analysis by the
146 5. _Active_ - The `Software.Version` is active on the managed element. Note that
173 being performed. For example, we do not want to boot a managed host while its
179 It is strongly suggested that any activations are completed prior to a managed
207 single managed element. It is expected that all installed versions are listed as
256 information on how the software is managed.
267 ### Find all software versions on a managed element
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-core/init-ifupdown/files/juno/
H A Dinterfaces9 wireless_mode managed
/openbmc/qemu/docs/system/
H A Dindex.rst33 managed-startup
/openbmc/openbmc/poky/meta/recipes-devtools/python/
H A Dpython3-setuptools-scm_8.2.1.bb5 argument or in a SCM managed file."
/openbmc/openbmc/poky/meta/recipes-core/init-ifupdown/init-ifupdown-1.0/
H A Dinterfaces9 wireless_mode managed
/openbmc/phosphor-pid-control/pid/
H A DREADME10 Each group of these controllers is managed within a zone. A PIDZone object
/openbmc/u-boot/doc/device-tree-bindings/net/
H A Dfixed-link.txt5 normal MDIO-managed PHY device. For those situations, a Device Tree
/openbmc/u-boot/doc/device-tree-bindings/sysreset/
H A Dti,sci-sysreset.txt14 which is managed by the SYSFW. Because this relies on the TI SCI protocol
/openbmc/u-boot/arch/arm/dts/
H A Dkeystone-k2hk-netcp.dtsi27 managed-queues = <0 0x2000>;
39 managed-queues = <0x2000 0x2000>;
/openbmc/phosphor-logging/test/openpower-pels/
H A Dmocks.hpp81 void setHMCManaged(bool managed) in setHMCManaged() argument
83 _hmcManaged = managed; in setHMCManaged()
/openbmc/u-boot/drivers/dfu/
H A DKconfig21 This option allows performing update of DFU-managed medium with data
/openbmc/qemu/docs/devel/
H A Dzoned-storage.rst15 - BLK_Z_HM: The host-managed zoned model only allows sequential writes access
21 regular and drive-managed ZBD devices. ZBD-specific I/O commands are not
/openbmc/u-boot/doc/
H A DREADME.ubispl122 * for the SPL itself and not managed by UBI.
134 UBI, so the only non UBI managed FLASH area is the one which is
/openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/dvb-apps/files/dvb-scan-table/dvb-t/
H A Des-Donostia2 # here. However I have only managed to get a lock for the channel 57 of the French ones.
/openbmc/openbmc/poky/meta/recipes-extended/pam/libpam/pam.d/
H A Dcommon-account9 # As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
/openbmc/openbmc/meta-phosphor/recipes-extended/pam/libpam/pam.d/
H A Dcommon-account9 # As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
/openbmc/openbmc/meta-ibm/recipes-extended/pam/libpam/pam.d/
H A Dcommon-account9 # As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
/openbmc/u-boot/doc/device-tree-bindings/power/
H A Dti,sci-pm-domain.txt13 The PM domain node represents the global PM domain managed by the SYSFW. Because
/openbmc/openbmc/meta-phosphor/classes/
H A Dobmc-phosphor-image.bbclass76 # EVB systems do not have a managed system.
78 # QEMU systems are like EVBs and do not have a managed system.
/openbmc/phosphor-networkd/src/
H A Dnetwork_manager.cpp521 bool managed = state != "unmanaged"; in handleAdminState() local
522 systemdNetworkdEnabled.insert_or_assign(ifidx, managed); in handleAdminState()
525 createInterface(it->second, managed); in handleAdminState()
/openbmc/u-boot/doc/device-tree-bindings/clock/
H A Dti,sci-clk.txt14 The clock controller node represents the clocks managed by the SYSFW. Because
/openbmc/u-boot/doc/device-tree-bindings/reset/
H A Dti,sci-reset.txt14 present on the SoC managed by the SYSFW. Because this relies on the TI SCI
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/ipmiutil/
H A Dipmiutil_3.1.9.bb5 support the IPMI 1.5 or 2.0 specification. IPMI servers can be managed\

12345678910