From: Gerd Hoffmann <kraxel@redhat.com>
To: Roy Tam <roytam@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] usb: change VID/PID for usb-hub and usb-msd to prevent conflict
Date: Fri, 16 Sep 2011 11:46:08 +0200 [thread overview]
Message-ID: <4E731AE0.40008@redhat.com> (raw)
In-Reply-To: <CAA=zYJZ6FikPM1CqrP+2ptxJyPcpe172cB27jM0rJhikBWrxLA@mail.gmail.com>
Hi,
>> lsusb says: Bus 004 Device 002: ID 0409:55aa NEC Corp. Hub
>>
>> Looks sensible. Is that actually a USB 1.1 Hub?
>>
>
> Yes. If you want a USB 2.0 ID, use 0x03f0:0x2002 (HP Hub) instead.
> Using USB 1.1 ID to prevent "High Speed" information cloud in XP.
No, a USB 1.1 Hub ID is perfectly fine as we are actually emulating a
1.1 Hub. Just asking because it wasn't obvious whenever this is a 1.1
or 2.0 hub id.
> 0x46f4 is CRC16() of "QEMU".
Ok. I'll add that as comment to the patch.
thanks,
Gerd
prev parent reply other threads:[~2011-09-16 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 3:25 [Qemu-devel] [PATCH] usb: change VID/PID for usb-hub and usb-msd to prevent conflict Roy Tam
2011-09-15 16:06 ` Gerd Hoffmann
2011-09-16 0:14 ` Roy Tam
2011-09-16 9:46 ` Gerd Hoffmann [this message]
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=4E731AE0.40008@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roytam@gmail.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).