From: Gerd Hoffmann <kraxel@redhat.com>
To: Howard Spoelstra <hsp.cat7@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: USB pass through into Mac OS 9.x with qemu-system-ppc
Date: Wed, 17 Feb 2021 08:27:16 +0100 [thread overview]
Message-ID: <20210217072716.k376o2enckzclszo@sirius.home.kraxel.org> (raw)
In-Reply-To: <CABLmASF_r4E85yLQgEYSZWraBO4Uo70o28f6YZQ3-w0+wPW1XA@mail.gmail.com>
> Hi Gerd,
>
> Thanks for looking into this. It looks to me that the usb storage
> device nicely reports endpoints 1 and 2 when asked, but that the host
> only ever communicates with endpoint 1.
EP 1 is host -> device.
EP 2 is device -> host.
So the host sends requests but the device never answers, probably due to
the wMaxPacketSize mismatch, macos being confused and sending broken
requests ...
> Can this also explain that other (non-mass-storage) devices cannot be
> passed through successfully ?
Yes, you can have simliar issues with other devices. Devices can have
different interface descriptors for different device speeds. This can
be rather small differences like the wMacPacketSize for usb sticks. The
descriptors can be identical. Or there can be large differences, like
usb-audio devices offering more channels when plugged into a usb2 port
(with enough bandwidth for that).
Problem is when the device is plugged into a usb2 port you can't query
the usb1 descriptors. So qemu presents the wrong descriptors to the
guest in case host and guest use different usb speeds. That may or may
not work ...
The other way around is less problematic, when plugging a usb2 device
into a usb3-capable (xhci) port I can tell the guest "this is a usb2
device". But reporting "this is a usb2 device" via ohci isn't going to
fly for obvious reasons ...
take care,
Gerd
next prev parent reply other threads:[~2021-02-17 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 13:29 USB pass through into Mac OS 9.x with qemu-system-ppc Howard Spoelstra
2021-02-09 15:12 ` Gerd Hoffmann
2021-02-09 17:17 ` Howard Spoelstra
2021-02-12 8:53 ` Howard Spoelstra
2021-02-16 14:48 ` Gerd Hoffmann
2021-02-16 15:42 ` Howard Spoelstra
2021-02-17 7:17 ` Howard Spoelstra
2021-02-17 7:45 ` Gerd Hoffmann
2021-02-17 7:27 ` Gerd Hoffmann [this message]
[not found] <mailman.2361.1612790999.21101.qemu-devel@nongnu.org>
2021-02-11 20:46 ` Programmingkid
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=20210217072716.k376o2enckzclszo@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=hsp.cat7@gmail.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).