From: Anthony Liguori <anthony@codemonkey.ws>
To: Hans de Goede <hdegoede@redhat.com>, Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] usb-redir: Allow to attach USB 2.0 devices to 1.1 host controller
Date: Tue, 18 Sep 2012 16:18:09 -0500 [thread overview]
Message-ID: <87lig76ne6.fsf@codemonkey.ws> (raw)
In-Reply-To: <50573283.3080206@redhat.com>
Hans de Goede <hdegoede@redhat.com> writes:
> Hi,
>
> On 09/17/2012 11:18 AM, Jan Kiszka wrote:
>> On 2012-09-17 11:08, Hans de Goede wrote:
>
> <snip>
>
>>> Although not pretty I'm ok with this, since I actually want to add
>>> similar code to allow usb-3 (superspeed) devices like a usb-3 usb-stick
>>> to work with ehci or uhci controllers :)
>>
>> Great, that would have been my next question, but I don't have hardware
>> for that around yet.
>
> I do have hardware for that around, so once you've respun your patch to
> address the issues discussed, then that will give me a nice basis to
> add usb-3 usb-stick to ehci-controller redirection :)
>
>> BTW, I'm facing several incompatibilities with passed-through CDC/ACM
>> devices (e.g. a Galaxy S2), independent of my patch. Both host-linux and
>> redir doesn't allow to use them properly but show different symptoms.
>> Need to analyze and report once time permits.
>
> Hmm, there is (was) one know issues with these devices, which has been fixed
> in usbredir, so first of all make sure that the usbredir on your spice-client
> / usbredirserver, has this patch:
> http://cgit.freedesktop.org/spice/usbredir/commit/?id=7783d3db61083bbf7f61b1ea8608c666b4c6a1dd
>
> If that does not work, add the debug parameter to the usb-redir device, set it
> to 4, collect logs of trying to redirect the device and send me the logs
> please, ie:
> -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1,debug=4
>
> Also be aware that usb-redir relies on chardev flowcontrol working,
> which it does not upstream! See for example here for the chardev flow
> control patch set which RHEL / Fedora carry:
> http://cgit.freedesktop.org/~jwrdegoede/qemu/log/?h=qemu-kvm-1.2-usbredir&ofs=50
Those patches are garbage.
Are you saying that usb-redir doesn't work in qemu.git? So why are we
even carrying it?
Regards,
Anthony Liguori
>
> And then the first 13 patches after: "Merge tag 'v1.2.0'"
>
> Oh, and also, if you're running qemu git master, make sure you've:
> http://cgit.freedesktop.org/~jwrdegoede/qemu/commit/?id=81e34f5973d8d6a1ef998a50c4a4bf66abb3b56b
>
> Regards,
>
> Hans
next prev parent reply other threads:[~2012-09-18 21:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 16:27 [Qemu-devel] [PATCH] usb-redir: Allow to attach USB 2.0 devices to 1.1 host controller Jan Kiszka
2012-09-17 9:08 ` Hans de Goede
2012-09-17 9:18 ` Jan Kiszka
2012-09-17 14:24 ` Hans de Goede
2012-09-17 16:22 ` Jan Kiszka
2012-09-18 9:41 ` Hans de Goede
2012-09-21 11:49 ` Jan Kiszka
2012-09-21 12:21 ` Hans de Goede
2012-09-21 12:25 ` Jan Kiszka
2012-09-18 21:18 ` Anthony Liguori [this message]
2012-09-19 9:20 ` Hans de Goede
2012-09-22 9:29 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2012-10-08 17:36 ` Jan Kiszka
2012-10-08 23:05 ` [Qemu-devel] [v2] " Hans de Goede
2012-10-09 8:38 ` Hans de Goede
2012-10-09 8:40 ` Gerd Hoffmann
2012-10-09 10:05 ` 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=87lig76ne6.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=hdegoede@redhat.com \
--cc=jan.kiszka@web.de \
--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).