Home
last modified time | relevance | path

Searched full:attached (Results 1 – 25 of 670) sorted by relevance

12345678910>>...27

/openbmc/qemu/tests/qemu-iotests/
H A D186.out10 Attached to: /machine/peripheral-anon/device[N]
18 Attached to: qdev_id
26 Attached to: /machine/peripheral-anon/device[N]
34 Attached to: qdev_id
42 Attached to: /machine/peripheral-anon/device[N]
50 Attached to: qdev_id
61 Attached to: /machine/peripheral-anon/device[N]
69 Attached to: qdev_id
77 Attached to: /machine/peripheral-anon/device[N]
85 Attached to: qdev_id
[all …]
H A D172.out64 Attached to: /machine/unattached/device[N]
69 Attached to: /machine/unattached/device[N]
114 Attached to: /machine/unattached/device[N]
119 Attached to: /machine/unattached/device[N]
123 Attached to: /machine/unattached/device[N]
168 Attached to: /machine/unattached/device[N]
173 Attached to: /machine/unattached/device[N]
178 Attached to: /machine/unattached/device[N]
252 Attached to: /machine/unattached/device[N]
257 Attached to: /machine/unattached/device[N]
[all …]
/openbmc/openbmc/meta-hpe/meta-common/recipes-hpe/vehci/host-ehci-owner-reset/
H A Dudc-reconnect.sh11 echo "UDC0 is not attached"
22 echo "UDC1 is not attached"
33 echo "UDC2 is not attached"
/openbmc/qemu/docs/system/
H A Ddevice-emulation.rst34 automatically created. In most cases the BUS a device is attached to
38 (``bus=ID``) a device is attached to along with its address
42 additional buses to the system that other devices can be attached to.
48 which would be a bar device (with the ID of baz) which is attached to
50 that bus is itself is attached to the first PCI bus (pci.0).
/openbmc/u-boot/doc/
H A DREADME.nokia_rx5130 * 0. if keyboard is closed boot automatically attached kernel image
33 * 3. try boot from attached kernel image
53 * run attachboot - Boot attached kernel image (attached to U-Boot binary)
100 flashed with attached zImage to RX-51 kernel nand area. For enabling UBIFS
H A DREADME.nvme11 for enterprise and client solid state drives, typically attached to the PCI
30 it is able to scan all available namespaces attached to it. Scanning namespace
46 be executed for all NVMe hard disks attached to the NVMe controller to be
H A DREADME.ubi31 when such a UBI device is attached (via "ubi part"). Here an example:
59 UBI: attached mtd1 to ubi0
74 Now that the UBI device is attached, this device can be modified
152 UBI partition which has been attached with the ubi part command:
/openbmc/u-boot/include/
H A Dvideo_bridge.h37 * check_attached() - check if a bridge is correctly attached
43 * @return 0 if attached, -EENOTCONN if not, or other -ve error
94 * check_attached() - check if a bridge is correctly attached
97 * @return 0 if attached, -EENOTCONN if not, or other -ve error
H A Dnvme.h61 * nvme_scan_namespace - scan all namespaces attached to NVMe controllers
64 * and tries to find all namespaces attached to the NVMe controllers.
/openbmc/qemu/docs/
H A Dpci_expander_bridge.txt32 - a pxb host bridge attached to NUMA 1 with an e1000 behind it
33 - a pxb host bridge attached to NUMA 0 with an e1000 behind it
34 - a pxb host bridge not attached to any NUMA with a hard drive behind it.
54 When adding a device to PXB it is attached to the bridge for two reasons:
/openbmc/qemu/hw/usb/
H A Dbus.c59 dev->attached = false; in usb_device_post_load()
61 dev->attached = true; in usb_device_post_load()
289 if (dev->attached) { in usb_qdev_unrealize()
489 assert(!dev->attached); in usb_check_attach()
516 dev->attached = true; in usb_device_attach()
526 assert(dev->attached); in usb_device_detach()
530 dev->attached = false; in usb_device_detach()
556 dev->attached ? ", attached" : ""); in usb_bus_dev_print()
684 return dev->attached; in usb_get_attached()
691 if (dev->attached == value) { in usb_set_attached()
[all …]
/openbmc/entity-manager/schemas/
H A Dmctp.json11 "description": "The bus index to which the device is attached",
33 "description": "The bus index to which the device is attached",
/openbmc/qemu/qapi/
H A Dcommon.json168 # Indicates whether a netfilter is attached to a netdev's transmit
171 # @all: the filter is attached both to the receive and the transmit
174 # @rx: the filter is attached to the receive queue of the netdev,
177 # @tx: the filter is attached to the transmit queue of the netdev,
/openbmc/u-boot/include/configs/
H A Dnokia_rx51.h212 "attachboot=echo Booting attached kernel image ...;" \
250 "bootmenu_0=Attached kernel=run attachboot\0" \
289 "echo run attachboot - Boot attached kernel image.;" \
334 * Attached kernel image
345 /* Reserve protected RAM for attached kernel */
/openbmc/u-boot/drivers/video/rockchip/
H A Drk_hdmi.h26 * rk_hdmi_read_edid() - read the attached HDMI/DVI monitor's EDID
66 * 1. checks for HPD (i.e. a HDMI monitor being attached)
/openbmc/u-boot/cmd/
H A Ddfu.c69 " on device <dev>, attached to interface\n"
79 " on device <dev>, attached to interface\n"
/openbmc/bmcweb/redfish-core/include/registries/
H A Dstorage_device_message_registry.hpp337 "The volume '%1' attached to the storage controller located in '%2' is degraded.",
350 "The volume '%1' attached to the storage controller located in '%2' has failed.",
363 …"The health of volume '%1' that is attached to the storage controller located in '%2' has changed …
376 "The volume '%1' attached to the storage controller located in '%2' is offline.",
389 "The volume '%1' attached to the storage controller located in '%2' is offline.",
402 "The volume '%1' attached to the storage controller located in '%2' is online.",
/openbmc/qemu/docs/system/devices/
H A Dnvme.rst128 Specifies that the namespace will be attached to all controllers in the
130 and may only be attached to a single controller at a time. Shared namespaces
131 are always automatically attached to all controllers (also when controllers
136 not attached to any controllers initially. A shared namespace with this set
137 to ``on`` will never be automatically attached to controllers.
148 will cause NSID 1 will be a shared namespace that is initially attached to both
151 attached to any controller initially (due to ``detached=on``) or to hotplugged
H A Dusb.rst42 the EHCI controller. Devices must be attached to the correct
56 bus they should be attached to. Here is a complete example:
128 USB attached SCSI device. This does not create a SCSI disk, so
253 case they are added with ``attached = false`` so the guest will not see
254 the device until the ``attached`` property is explicitly set to true.
261 #. ``scripts/qmp/qom-set foo.attached = true``
327 Specifies the bus number the device must be attached to
331 Specifies the physical port the device is attached to
/openbmc/u-boot/test/py/
H A Du_boot_console_sandbox.py39 A u_boot_spawn.Spawn object that is attached to U-Boot.
65 A u_boot_spawn.Spawn object that is attached to U-Boot.
/openbmc/u-boot/doc/driver-model/
H A Dusb-info.txt115 Given a controller, you know the bus - it is the one attached to the
117 root hub attached to it. This hub, which is itself a USB device, can provide
118 one or more 'ports' to which additional devices can be attached. It is
120 attached.
151 U-Boot simply finds the controller to which the device is attached, and sends
173 are attached to a parent hub (or controller in the case of the root hub) and
174 so have parent data attached to them (this is struct usb_device).
200 (only) device that is attached to the controller - a root hub
/openbmc/qemu/docs/specs/
H A Dfsi.rst30 which it is attached.
49 The configuration block presents engines in the order they are attached to the
55 so complete; it's assumed that each CFAM is attached to a single FSI slave (as
/openbmc/u-boot/test/py/tests/
H A Dtest_efi_loader.py19 # Boolean indicating whether the Ethernet device is attached to USB, and hence
24 # Boolean indicating whether the Ethernet device is attached to PCI, and hence
29 # True if a DHCP server is attached to the network, and should be tested.
H A Dtest_net.py17 # Boolean indicating whether the Ethernet device is attached to USB, and hence
22 # Boolean indicating whether the Ethernet device is attached to PCI, and hence
27 # True if a DHCP server is attached to the network, and should be tested.
/openbmc/phosphor-bmc-code-mgmt/cpld/
H A DREADME.md3 This daemon implements the update process for CPLD attached via I2C bus.

12345678910>>...27