From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Fabio Fantoni <fabio.fantoni@m2r.biz>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: [PATCH v7 2/2] libxl: spice usbredirection support for upstream qemu
Date: Thu, 5 Dec 2013 14:40:13 +0000 [thread overview]
Message-ID: <52A0904D.3020009@citrix.com> (raw)
In-Reply-To: <1386253954.20047.69.camel@kazak.uk.xensource.com>
On 05/12/13 14:32, Ian Campbell wrote:
>
> Has a qemu person acked the command lines used to create each of these
> configurations? To my non-usb aware mind it looks odd that USB2
> explicitly creates the legacy USB1 controller (AIUI this is how USB2 is
> supposed to be done) while USB3 doesn't create any legacy controllers. I
> don't know how USB3 is suppose to work, so perhaps USB3 does differ from
> USB2 in this way, I don't know.
xhci controllers support all speeds of devices (low, full, high and
super) so the legacy controllers are not needed.
David
next prev parent reply other threads:[~2013-12-05 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 15:20 [PATCH v7 1/2] libxl: usb2 and usb3 controller support for upstream qemu Fabio Fantoni
2013-11-19 15:20 ` [PATCH v7 2/2] libxl: spice usbredirection " Fabio Fantoni
2013-12-03 17:13 ` Ian Jackson
2013-12-05 14:22 ` George Dunlap
2013-12-05 14:29 ` Ian Jackson
2013-12-05 14:32 ` Ian Campbell
2013-12-05 14:40 ` David Vrabel [this message]
2013-12-05 14:44 ` Ian Campbell
2013-12-05 14:44 ` George Dunlap
2013-12-05 14:48 ` Ian Campbell
2013-12-06 13:23 ` Ian Campbell
2013-12-03 16:17 ` [PATCH v7 1/2] libxl: usb2 and usb3 controller " Ian Jackson
2013-12-03 16:55 ` George Dunlap
2013-12-03 16:58 ` Ian Jackson
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=52A0904D.3020009@citrix.com \
--to=david.vrabel@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=fabio.fantoni@m2r.biz \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.