Lines Matching refs:devices

5 plug virtual USB devices or real host USB devices (only works with
7 connect virtual USB hubs as necessary to connect multiple USB devices.
23 XHCI supports USB 1.1, USB 2.0 and USB 3.0 devices, so this is the
26 need to use the bus= parameter when adding USB devices.
32 The QEMU EHCI Adapter supports USB 2.0 devices. It can be used either
34 devices. The companion controller setup is more convenient to use
36 1.1 devices. See next section for details.
39 controllers for USB 1.1 devices too. Each controller creates its own
55 When adding USB devices using the ``-device`` switch you can specify the
89 Then use ``bus=ehci.0`` to assign your USB devices to that bus.
95 .. _Connecting USB devices:
97 Connecting USB devices
100 USB devices can be connected with the ``-device usb-...`` command line
101 option or the ``device_add`` monitor command. Available devices are:
153 i.e. for three devices you must use 0+1+2. The 0+1+5 numbering from the
219 For all the above USB devices, by default QEMU will plug the device
241 property specification. If you want to unplug devices too you should
252 The ``usb-bot`` and ``usb-uas`` devices can be hotplugged. In the hotplug
255 That allows you to attach one or more scsi devices before making the
260 #. optionally add more devices (luns 1 ... 15)
265 Using host USB devices on a Linux host
269 it. USB devices requiring real time streaming (i.e. USB Video Cameras)
283 001 devices drivers
285 3. Since only root can access to the USB devices directly, you can
287 devices you want to use. For testing, the following suffices:
301 You should see the list of the devices you can use (Never try to use
351 Note that on the host USB 1.1 devices are handled by UHCI/OHCI and USB
352 2.0 by EHCI. That means different USB devices plugged into the very
354 depending on the speed. Supposing that devices plugged into a given
355 physical port appear as bus 1 + port 1 for 2.0 devices and bus 3 + port 1
356 for 1.1 devices, you can pass through any device plugged into that port
385 The reason for this existing are broken usb devices. In theory one
386 should be able to reset (and re-initialize) usb devices at any time.
399 All usb devices have support for recording the usb traffic. This can