aboutsummaryrefslogtreecommitdiff
path: root/hw/usb/desc-msos.c
diff options
context:
space:
mode:
authorIsaac Lozano <109lozanoi@gmail.com>2016-04-17 04:29:53 -0700
committerGerd Hoffmann <kraxel@redhat.com>2016-05-11 10:33:49 +0200
commit1f66fe5778ca906448385ee004b38381ae067755 (patch)
tree43b0916d7f0f3a32cdcf1257fea406e434ed584e /hw/usb/desc-msos.c
parent491d68d9382dbb588f2ff5132ee3d87ce2f1b230 (diff)
downloadqemu-1f66fe5778ca906448385ee004b38381ae067755.zip
qemu-1f66fe5778ca906448385ee004b38381ae067755.tar.gz
qemu-1f66fe5778ca906448385ee004b38381ae067755.tar.bz2
usb-mtp: fix usb_mtp_get_device_info so that libmtp on the guest doesn't complain
If an application uses libmtp on the guest system, it will complain with the warning message: LIBMTP WARNING: VendorExtensionID: ffffffff LIBMTP WARNING: VendorExtensionDesc: (null) LIBMTP WARNING: this typically means the device is PTP (i.e. a camera) but not a MTP device at all. Trying to continue anyway. This is because libmtp expects a MTP Vendor Extension ID of 0x00000006 and a MTP Version of 0x0064. These numbers are taken from Microsoft's MTP Vendor Extension Identification Message page and are what most physical devices show. Signed-off-by: Isaac Lozano <109lozanoi@gmail.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Message-id: 1460892593-5908-1-git-send-email-109lozanoi@gmail.com Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'hw/usb/desc-msos.c')
0 files changed, 0 insertions, 0 deletions