/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
H A D | README.md | 27 - FabricAdapter and Connector.Port: `{connecting, connected_to}` 28 - Cpu and PCIeSlot: `{connecting, connected_to}` 29 - PCIeSwitch and PCIeSlot: `{connecting, connected_to}` 31 - Cable and Item: `{connecting, connected_to}`
|
H A D | FabricAdapter.interface.yaml | 3 capable of connecting to an interconnect fabric. Examples include but are 7 name: connecting 10 connecting association to provide links to one or more Ports.
|
H A D | PCIeSwitch.interface.yaml | 6 name: connecting 9 connecting association to provide links to one or more Slots.
|
H A D | Cable.interface.yaml | 21 - name: connecting 23 Objects that implement Cable can optionally implement the 'connecting'
|
H A D | Cpu.interface.yaml | 91 name: connecting 93 Objects that implement Cpu can optionally implement the connecting
|
/openbmc/linux/arch/arm/boot/dts/aspeed/ |
H A D | aspeed-bmc-facebook-minipack.dts | 76 * connecting to left PDB (Power Distribution Board). 89 * connecting to right PDB (Power Distribution Board). 102 * connecting to top FCM (Fan Control Module). 115 * connecting to bottom FCM (Fan Control Module). 127 * I2C Switch 40-0073 (channel #0 of 11-0070): connecting 140 * I2C Switch 41-0073 (channel #1 of 11-0070): connecting 153 * I2C Switch 42-0073 (channel #2 of 11-0070): connecting 166 * I2C Switch 43-0073 (channel #3 of 11-0070): connecting 179 * I2C Switch 44-0073 (channel #4 of 11-0070): connecting 192 * I2C Switch 45-0073 (channel #5 of 11-0070): connecting [all …]
|
H A D | aspeed-bmc-facebook-fuji.dts | 15 * PCA9548 (2-0070) provides 8 channels connecting to 28 * PCA9548 (8-0070) provides 8 channels connecting to 41 * PCA9548 (11-0077) provides 8 channels connecting to 54 * PCA9548 (24-0071) provides 8 channels connecting to 67 * PCA9548 (25-0072) provides 8 channels connecting to 80 * PCA9548 (26-0076) provides 8 channels connecting to 93 * PCA9548 (27-0076) provides 8 channels connecting to 106 * PCA9548 (40-0076) provides 8 channels connecting to 119 * PCA9548 (41-0076) provides 8 channels connecting to 132 * PCA9548 (42-0076) provides 8 channels connecting to [all …]
|
H A D | aspeed-bmc-facebook-cmm.dts | 22 * PCA9548 (1-0077) provides 8 channels for connecting to 35 * PCA9548 (2-0071) provides 8 channels for connecting to 49 * channels are connecting to 4 Fan Control Boards. 61 * 2 PCA9548 (18-0070 & 18-0073), 16 channels connecting 82 * 2 PCA9548 (19-0070 & 19-0073), 16 channels connecting 103 * 2 PCA9548 (20-0070 & 20-0073), 16 channels connecting 124 * 2 PCA9548 (21-0070 & 21-0073), 16 channels connecting 145 * 2 PCA9548 (16-0070 & 16-0073), 16 channels connecting 166 * 2 PCA9548 (17-0070 & 17-0073), 16 channels connecting 187 * 2 PCA9548 (22-0070 & 22-0073), 16 channels connecting [all …]
|
/openbmc/qemu/python/tests/ |
H A D | protocol.py | 47 self._set_state(Runstate.CONNECTING) 60 self._set_state(Runstate.CONNECTING) 244 Runstate.CONNECTING, 251 Runstate.CONNECTING, 346 self.assertEqual(state, Runstate.CONNECTING) 370 self.assertEqual(state, Runstate.CONNECTING) 379 Test what happens when a connection attempt is made while CONNECTING. 385 self.assertEqual(state, Runstate.CONNECTING) 392 "NullProtocol is currently connecting." 394 self.assertEqual(context.exception.state, Runstate.CONNECTING) [all …]
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 231.out | 4 …driver':'rbd','file.filename':'rbd:rbd/bogus:conf=BOGUS_CONF'}': error connecting: No such file or… 6 …ile.pool':'rbd','file.image':'bogus','file.conf':'BOGUS_CONF'}': error connecting: No such file or… 9 qemu-img: rbd:rbd/aa\/bb:conf=BOGUS_CONF: error connecting: No such file or directory
|
/openbmc/linux/Documentation/devicetree/bindings/media/ |
H A D | imx.txt | 44 connecting to the source and sink devices according to 46 connecting with a MIPI CSI-2 source, and ports 1 47 through 4 are output ports connecting with parallel
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | Cable.v1_2_4.json | 36 …"description": "The `Cable` schema contains properties that describe a cable connecting endpoints … 290 "Fabric": "This cable is used for connecting to a fabric.", 291 "Fan": "This cable is used for connecting to a fan system.", 293 "Network": "This cable is used for connecting to a networking system.", 294 "PCIe": "This cable is used for connecting to a PCIe endpoint.", 295 "Power": "This cable is used for connecting to a power system.", 296 "Serial": "This cable is used for connecting to a serial endpoint.", 297 "Storage": "This cable is used for connecting to a storage system.", 298 "USB": "This cable is used for connecting to a USB endpoint.", 299 "Video": "This cable is used for connecting to a video system."
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
H A D | Cable.v1_2_4.json | 36 …"description": "The `Cable` schema contains properties that describe a cable connecting endpoints … 290 "Fabric": "This cable is used for connecting to a fabric.", 291 "Fan": "This cable is used for connecting to a fan system.", 293 "Network": "This cable is used for connecting to a networking system.", 294 "PCIe": "This cable is used for connecting to a PCIe endpoint.", 295 "Power": "This cable is used for connecting to a power system.", 296 "Serial": "This cable is used for connecting to a serial endpoint.", 297 "Storage": "This cable is used for connecting to a storage system.", 298 "USB": "This cable is used for connecting to a USB endpoint.", 299 "Video": "This cable is used for connecting to a video system."
|
/openbmc/qemu/python/qemu/qmp/ |
H A D | protocol.py | 63 #: In the process of connecting or establishing a session. 64 CONNECTING = 1 variable in Runstate 144 if proto.runstate == Runstate.CONNECTING: 145 emsg = f"{name} is currently connecting." 327 assert self.runstate == Runstate.CONNECTING 330 @require(Runstate.CONNECTING) 337 :raise StateError: When the `Runstate` is not `CONNECTING`. 552 self._set_state(Runstate.CONNECTING) 575 # Allow runstate watchers to witness 'CONNECTING' state; some 615 self._set_state(Runstate.CONNECTING) [all …]
|
/openbmc/openbmc/meta-ibm/recipes-phosphor/inventory/phosphor-inventory-manager/p10bmc/ |
H A D | ibm,rainier-4u_associations.json | 2171 "rType": "connecting", 2221 "rType": "connecting", 2271 "rType": "connecting", 2321 "rType": "connecting", 2371 "rType": "connecting", 2460 "rType": "connecting", 2510 "rType": "connecting", 2560 "rType": "connecting", 2610 "rType": "connecting", 2660 "rType": "connecting", [all …]
|
H A D | ibm,blueridge-4u_associations.json | 2171 "rType": "connecting", 2221 "rType": "connecting", 2271 "rType": "connecting", 2321 "rType": "connecting", 2371 "rType": "connecting", 2460 "rType": "connecting", 2510 "rType": "connecting", 2560 "rType": "connecting", 2610 "rType": "connecting", 2660 "rType": "connecting", [all …]
|
H A D | ibm,fuji_associations.json | 1115 "fType": "connecting" 1145 "fType": "connecting" 1175 "fType": "connecting" 1205 "fType": "connecting" 1235 "fType": "connecting" 1283 "fType": "connecting" 1313 "fType": "connecting" 1365 "fType": "connecting" 1399 "fType": "connecting" 2841 "rType": "connecting", [all …]
|
H A D | ibm,everest_associations.json | 1115 "fType": "connecting" 1145 "fType": "connecting" 1175 "fType": "connecting" 1205 "fType": "connecting" 1235 "fType": "connecting" 1283 "fType": "connecting" 1313 "fType": "connecting" 1365 "fType": "connecting" 1399 "fType": "connecting" 2841 "rType": "connecting", [all …]
|
H A D | ibm,blueridge-2u_associations.json | 2025 "rType": "connecting", 2075 "rType": "connecting", 2125 "rType": "connecting", 2175 "rType": "connecting", 2225 "rType": "connecting", 2314 "rType": "connecting", 2364 "rType": "connecting", 2414 "rType": "connecting", 2464 "rType": "connecting", 2514 "rType": "connecting", [all …]
|
H A D | ibm,rainier-2u_associations.json | 2026 "rType": "connecting", 2076 "rType": "connecting", 2126 "rType": "connecting", 2176 "rType": "connecting", 2226 "rType": "connecting", 2315 "rType": "connecting", 2365 "rType": "connecting", 2415 "rType": "connecting", 2465 "rType": "connecting", 2515 "rType": "connecting", [all …]
|
/openbmc/phosphor-mrw-tools/docs/ |
H A D | mrw-xml-requirements.md | 60 accomplished by connecting instances of the `BMC_FLASH` part to the 83 UARTs are enabled by connecting the appropriate UART master units in the BMC 100 I2C devices are enabled by connecting the I2C master units in the BMC to the I2C
|
/openbmc/qemu/docs/system/arm/ |
H A D | xenpvh.rst | 24 Sample QEMU xenpvh commands for running and connecting with Xen: 38 In above QEMU command, last two lines are for connecting xenpvh QEMU to swtpm
|
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
H A D | Cable_v1.xml | 44 <Annotation Term="OData.Description" String="The `Cable` schema contains properties that describe a cable connecting endpoints of a chassis, port, or any other cable-compatible endpoint."/> 180 <Annotation Term="OData.Description" String="This cable is used for connecting to a power system."/> 183 <Annotation Term="OData.Description" String="This cable is used for connecting to a networking system."/> 186 <Annotation Term="OData.Description" String="This cable is used for connecting to a storage system."/> 189 <Annotation Term="OData.Description" String="This cable is used for connecting to a fan system."/> 192 <Annotation Term="OData.Description" String="This cable is used for connecting to a PCIe endpoint."/> 195 <Annotation Term="OData.Description" String="This cable is used for connecting to a USB endpoint."/> 198 <Annotation Term="OData.Description" String="This cable is used for connecting to a video system."/> 201 <Annotation Term="OData.Description" String="This cable is used for connecting to a fabric."/> 204 <Annotation Term="OData.Description" String="This cable is used for connecting t [all...] |
/openbmc/webui-vue/src/views/Operations/Kvm/ |
H A D | KvmConsole.vue | 52 const Connecting = 0; 72 status: Connecting, 92 return i18n.global.t('pageKvm.connecting');
|
/openbmc/qemu/docs/system/ |
H A D | tls.rst | 86 When connecting the certificate is sent to the client which validates it 89 clients when connecting. The hostname / IP address that the client 90 specifies when connecting will be validated against the hostname(s) and 97 when connecting, they may also be included in the certificate. Both IPv4 322 When connecting from a qemu-based client you must specify the directory
|