aboutsummaryrefslogtreecommitdiff
path: root/vl.c
diff options
context:
space:
mode:
authorHans de Goede <hdegoede@redhat.com>2010-11-10 10:06:25 +0100
committerAnthony Liguori <aliguori@us.ibm.com>2010-11-16 14:35:00 -0600
commit2cc59d8cb0ebcfa9cf3476c0528e50478997ab0c (patch)
tree75e77787d1b8d4d0dac27d0128961cf126713368 /vl.c
parent71d71bbdeb39544ac1602c5e307d9e14c78f9d5d (diff)
downloadqemu-2cc59d8cb0ebcfa9cf3476c0528e50478997ab0c.zip
qemu-2cc59d8cb0ebcfa9cf3476c0528e50478997ab0c.tar.gz
qemu-2cc59d8cb0ebcfa9cf3476c0528e50478997ab0c.tar.bz2
usb-linux: Get the active configuration from sysfs rather then asking the dev
Some devices seem to choke on receiving a USB_REQ_GET_CONFIGURATION ctrl msg (witnessed with a digital picture frame usb id 1908:1320). When usb_fs_type == USB_FS_SYS, the active configuration can be read directly from sysfs, which allows using this device through qemu's usb redirection. More in general it seems a good idea to not send needless control msg's to devices, esp. as the code in question is called every time a set_interface is done. Which happens multiple times during virtual machine startup, and when device drivers are activating the usb device. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'vl.c')
0 files changed, 0 insertions, 0 deletions