From: Dennis Ostermann <fixme@t-online.de>
To: qemu-devel@nongnu.org
Cc: hdegoede@redhat.com, kraxel@redhat.com
Subject: [Qemu-devel] Revert commit 5af35d7feccaa7d26b72c6c3d14116421d736b36 - "usb-host-libusb: Fix reset handling"
Date: Mon, 09 Feb 2015 22:09:04 +0100 [thread overview]
Message-ID: <54D921F0.2060809@t-online.de> (raw)
Hi there,
please revert commit 5af35d7feccaa7d26b72c6c3d14116421d736b36 -
"usb-host-libusb: Fix reset handling"
This breaks usb pass through of FTDI based usb devices:
On the host:
lsusb | grep FT2232
Bus 003 Device 008: ID 0403:6010 Future Technology Devices
International, Ltd FT2232C Dual USB-UART/FIFO IC
~/qemu-install/bin$ sudo ./qemu-system-x86_64 -monitor
telnet:127.0.0.1:1234,server,nowait -hda /dev/sdd2 -redir tcp:20022::22
--enable-kvm -cpu host -smp 4 -vga vmware --vnc :0 -m 8192 -usb -device
usb-ehci,id=ehci -device
usb-host,bus=ehci.0,vendorid=0x0403,productid=0x6010
WARNING: Image format was not specified for '/dev/sdd2' and probing
guessed raw.
Automatically detecting the format is dangerous for raw
images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
libusbx: error [_get_usbfs_fd] libusbx couldn't open USB device
/dev/bus/usb/003/005: No such file or directory
libusbx: error [_get_usbfs_fd] libusbx couldn't open USB device
/dev/bus/usb/003/006: No such file or directory
libusbx: error [_get_usbfs_fd] libusbx couldn't open USB device
/dev/bus/usb/003/007: No such device
The device gets reset again and again and is re-enumerated every time
and finally not passed through.
After reverting the commit:
~/qemu-patched-install/bin$ sudo ./qemu-system-x86_64 -monitor
telnet:127.0.0.1:1234,server,nowait -hda /dev/sdd2 -redir tcp:20022::22
--enable-kvm -cpu host -smp 4 -vga vmware --vnc :0 -m 8192 -usb -device
usb-ehci,id=ehci -device
usb-host,bus=ehci.0,vendorid=0x0403,productid=0x6010
WARNING: Image format was not specified for '/dev/sdd2' and probing
guessed raw.
Automatically detecting the format is dangerous for raw
images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
The device appears in the guest OS and can be used.
Tested with HEAD and several libusb versions. Affects at least FTDI
FT2232H and FTDI FT232R.
Thanks and best regards,
Dennis Ostermann
next reply other threads:[~2015-02-09 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 21:09 Dennis Ostermann [this message]
2015-02-10 8:09 ` [Qemu-devel] Revert commit 5af35d7feccaa7d26b72c6c3d14116421d736b36 - "usb-host-libusb: Fix reset handling" Hans de Goede
2015-02-10 21:02 ` Dennis Ostermann
2015-02-11 7:29 ` Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54D921F0.2060809@t-online.de \
--to=fixme@t-online.de \
--cc=hdegoede@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).