From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] usb: reword -usb command-line option and mention xHCI
Date: Thu, 15 Aug 2019 08:13:40 +0200 [thread overview]
Message-ID: <20190815061340.gryxnfwaaoswqqi7@sirius.home.kraxel.org> (raw)
In-Reply-To: <20190814132306.GF23970@stefanha-x1.localdomain>
Hi,
> > > -Enable the USB driver (if it is not used by default yet).
> > > +Enable USB emulation on machine types with an on-board USB host controller (if
> > > +not enabled by default). Note that on-board USB host controllers may not
> > > +support USB 3.0. In this case -device nec-usb-xhci can be used instead on
> >
> > Should we maybe rather recommend qemu-xhci instead?
>
> I think nec-usb-xhci is preferred because there are Windows drivers.
> IIRC qemu-xhci works under Linux but not under Windows (just because the
> PCI Vendor/Device ID aren't covered by any driver).
>
> Gerd: Can you confirm this?
That applies to windows 7 only, which is EOL next year.
win7 doesn't ship with xhci drivers, but you can download and use
nec/renesas drivers which require nec-usb-xhci.
win8+ ships with generic xhci drivers which works with all xhci
hardware, including qemu-xhci.
So it indeed makes sense to refer to qemu-xhci.
cheers,
Gerd
next prev parent reply other threads:[~2019-08-15 6:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 13:30 [Qemu-devel] [PATCH] usb: reword -usb command-line option and mention xHCI Stefan Hajnoczi
2019-08-13 17:54 ` Thomas Huth
2019-08-14 13:23 ` Stefan Hajnoczi
2019-08-15 6:13 ` Gerd Hoffmann [this message]
2019-08-15 14:09 ` Stefan Hajnoczi
2019-08-14 9:58 ` Dr. David Alan Gilbert
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=20190815061340.gryxnfwaaoswqqi7@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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 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).