| /openbmc/openbmc/poky/meta/lib/oeqa/manual/ |
| H A D | toaster-managed-mode.json | 4 "@alias": "toaster-managed-mode.toaster-managed.All_layers:_default_view",
50 "@alias": "toaster-managed-mode.toaster-managed.All_layers:_Add/delete_layers",
88 "@alias": "toaster-managed-mode.toaster-managed.All_targets:_Default_view",
122 "@alias": "toaster-managed-mode.toaster-managed.Configuration_variables:_default_view",
156 "@alias": "toaster-managed-mode.toaster-managed.Configuration_variables:_Test_UI_elements",
218 "@alias": "toaster-managed-mode.toaster-managed.Project_builds:_Default_view",
252 … "@alias": "toaster-managed-mode.toaster-managed.Project_builds:_Sorting_the_project_builds_table",
290 …"@alias": "toaster-managed-mode.toaster-managed.Project_builds:_customize_the_columns_of_the_table…
324 … "@alias": "toaster-managed-mode.toaster-managed.Project_builds:_filter_the_contents_of_the_table",
358 … "@alias": "toaster-managed-mode.toaster-managed.Project_builds:_search_the_contents_of_the_table",
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/ |
| H A D | ActivationBlocksTransition.interface.yaml | 3 prevent a state transition of the associated managed element while the
7 A typical use of this would be to prevent (delay) the power-on of a managed
8 host while the BIOS is being updated. The managed host, via systemd
|
| H A D | README.md | 14 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/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | ErrorBlocksTransition.interface.yaml | 3 prevent a state transition of the associated managed element while the
7 A typical use of this would be to prevent the power-on of a managed host
8 while a critical error is open. The managed host, via systemd transitions,
|
| /openbmc/intel-ipmi-oem/ |
| H A D | ipmi-allowlist.conf | 317 0x3e:0x02:0xff7f //<Intel Managed Data Region>:<BMC Data Region Update Event Message>
318 0x3e:0x20:0x7f7f //<Intel Managed Data Region>:<BMC Region Status>
319 0x3e:0x21:0x7f7f //<Intel Managed Data Region>:<BMC Region Update Complete>
320 0x3e:0x22:0xff7f //<Intel Managed Data Region>:<MDR Event>
321 0x3e:0x23:0xff7f //<Intel Managed Data Region>:<BMC Region Read>
322 0x3e:0x24:0x7f7f //<Intel Managed Data Region>:<BMC Region Write>
323 0x3e:0x25:0x7f7f //<Intel Managed Data Region>:<BMC Region Lock>
324 0x3e:0x28:0xff7f //<Intel Managed Data Region>:<Get DIMM information>
325 0x3e:0x30:0xff7f //<Intel Managed Data Region>:<MDR2 Status>
326 0x3e:0x31:0xff7f //<Intel Managed Data Region>:<MDR2 GET Direction>
[all …]
|
| /openbmc/pldm/fw-update/ |
| H A D | inventory_manager.hpp | 17 * managed by the BMC. It discovers the firmware identifiers and the component
37 * FDs managed by the BMC.
39 * identifiers for the FDs managed
42 * managed by the BMC.
71 * downstream device identifiers of the FDs managed by the BMC.
192 /** @brief Device identifiers of the managed FDs */
195 /** @brief Firmware Device names of the managed FDs */
198 /** @brief Downstream Device identifiers of the managed FDs */
201 /** @brief Component information needed for the update of the managed FDs */
|
| /openbmc/openbmc/meta-yadro/meta-vegman/recipes-phosphor/leds/rx20-led-manager-config/ |
| H A D | led.yaml | 5 # Managed by callback-manager
61 # Managed by phosphor-dbus-monitor
98 # Managed by phosphor-dbus-monitor
133 # Managed by phosphor-dbus-monitor
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | RegisteredClient.v1_1_2.json | 47 "description": "A resource managed by a client.",
48 …n": "This object shall contain information about a resource managed by a client. The managed reso…
65 …ption": "Indicates whether the subordinate resources of the managed resource are also managed by t…
66 …er the subordinate resources of the managed resource referenced by the `ManagedResourceURI` proper…
74 … "description": "The URI of the resource or resource collection managed by the registered client.",
76 …l contain the URI of the Redfish resource or Redfish resource collection managed by the registered…
84 …Indicates whether the registered client expects to have exclusive access to the managed resource.",
85 …te whether the registered client expects to have exclusive access to the managed resource referenc…
|
| /openbmc/u-boot/include/linux/soc/ti/ |
| H A D | ti_sci_protocol.h | 62 * @get_device: Command to request for device managed by TISCI
65 * @idle_device: Command to idle a device managed by TISCI
68 * @put_device: Command to release a device managed by TISCI
99 * @set_device_resets: Command to configure resets for device managed by TISCI.
103 * @get_device_resets: Command to read state of resets for device managed
116 * managed by driver for that purpose.
145 * @idle_clock: Request for Idling a clock managed by processor
146 * @put_clock: Release the clock to be auto managed by TISCI
147 * @is_auto: Is the clock being auto managed
148 * - req_state: state indicating if the clock is auto managed
[all …]
|
| /openbmc/phosphor-net-ipmid/command/ |
| H A D | rakp34.cpp | 112 * 1) Managed System Random Number - 16 bytes in RAKP34()
135 // Managed System Random Number in RAKP34()
180 * 2) Managed System Random Number - 16 bytes in RAKP34()
197 // Managed Console Random Number in RAKP34()
224 * 2) Managed System Session ID - 4 bytes in RAKP34()
225 * 3) Managed System GUID - 16 bytes in RAKP34()
228 // Get Managed System Session ID in RAKP34()
241 // Managed System Session ID in RAKP34()
246 // Managed System GUID in RAKP34()
|
| H A D | rakp12.cpp | 105 * 2) Managed System Session ID - 4 bytes in RAKP12()
107 * 4) Managed System Random Number - 16 bytes in RAKP12()
108 * 5) Managed System GUID - 16 bytes in RAKP12()
128 // Managed System Session ID in RAKP12()
143 // Generate the Managed System Random Number in RAKP12()
290 // Copy the Managed System Random Number to the Authentication Algorithm in RAKP12()
295 // Managed System GUID in RAKP12()
320 // Copy Managed System Random Number to the Response in RAKP12()
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/ |
| H A D | ManagedHost.interface.yaml | 2 Implement to define the inventory item as being the embodiment of a managed
8 The index / identifier of the managed host computer system. Many
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | RegisteredClient_v1.xml | 110 <Annotation Term="OData.Description" String="A resource managed by a client."/>
111 …ing="This object shall contain information about a resource managed by a client. The managed reso…
114 …Data.Description" String="The URI of the resource or resource collection managed by the registered…
115 …l contain the URI of the Redfish resource or Redfish resource collection managed by the registered…
120 …ndicates whether the registered client expects to have exclusive access to the managed resource."/>
121 …te whether the registered client expects to have exclusive access to the managed resource referenc…
125 … String="Indicates whether the subordinate resources of the managed resource are also managed by t…
126 …er the subordinate resources of the managed resource referenced by the `ManagedResourceURI` proper…
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/ |
| H A D | Manager.interface.yaml | 12 state managed.
17 A dictionary of fully enumerated items to be managed.
|
| /openbmc/u-boot/drivers/core/ |
| H A D | Kconfig | 160 bool "Managed device resources"
163 This option enables the Managed device resources core support.
164 Device resources managed by the devres framework are automatically
169 non-managed variants. For example, devres_alloc() to kzalloc(),
173 bool "Managed device resources debugging functions"
179 debug resource management for a managed device.
|
| /openbmc/phosphor-ipmi-flash/bmc/firmware-handler/ |
| H A D | net_handler.hpp | 7 #include <stdplus/handle/managed.hpp>
38 using Fd = stdplus::Managed<int>::Handle<closefd>;
|
| /openbmc/phosphor-networkd/test/ |
| H A D | test_network_manager.cpp | 47 manager.handleAdminState("managed", 2); in TEST_F()
59 manager.handleAdminState("managed", 1); in TEST_F()
76 manager.handleAdminState("managed", 1); in TEST_F()
|
| /openbmc/openbmc/meta-yadro/meta-vegman/recipes-phosphor/leds/vegman-led-manager-config/ |
| H A D | led.yaml | 5 # Managed by callback-manager
67 # Managed by phosphor-dbus-monitor
|
| /openbmc/openpower-pnor-code-mgmt/ |
| H A D | utils.hpp | 48 /** @brief Set the Hardware Management Console Managed bios attribute to
49 * Disabled to clear the indication that the system is HMC-managed.
|
| /openbmc/phosphor-webui/app/access-control/directives/ |
| H A D | role-table.js | 29 // should have 'Configure components managed by this service'
37 'Configure components managed by this service', check, '', '',
|
| /openbmc/phosphor-ipmi-flash/tools/ |
| H A D | net.cpp | 30 #include <stdplus/handle/managed.hpp>
46 using Fd = stdplus::Managed<int, const internal::Sys*>::Handle<closefd>;
97 // TODO: use stdplus Managed for the addrinfo structs in sendContents()
|
| /openbmc/openbmc/poky/meta/recipes-kernel/systemtap/systemtap/ |
| H A D | 0001-Install-python-modules-to-correct-library-dir.patch | 42 --single-version-externally-managed \
51 --single-version-externally-managed \
|
| /openbmc/openbmc/meta-phosphor/conf/machine/include/ |
| H A D | obmc-evb-common.inc | 2 # managed host. Enable this machine override to allow other recipes to know
|
| /openbmc/qemu/include/hw/timer/ |
| H A D | npcm7xx_timer.h | 94 * @timer: The five individual timers managed by this module.
95 * @watchdog_timer: The watchdog timer managed by this module.
|
| /openbmc/phosphor-pid-control/pid/ |
| H A D | README | 10 Each group of these controllers is managed within a zone. A PIDZone object
|