qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Howard Spoelstra <hsp.cat7@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.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: Tue, 9 Feb 2021 18:17:04 +0100	[thread overview]
Message-ID: <CABLmASEG3FiJ--7bQzZVJ1DtdFJSZ=a41yAf1QgEBf8BoGZk_w@mail.gmail.com> (raw)
In-Reply-To: <20210209151221.dxiiydxgxsqu3gmu@sirius.home.kraxel.org>

[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]

On Tue, Feb 9, 2021 at 4:12 PM Gerd Hoffmann <kraxel@redhat.com> wrote:

>   Hi,
>
> > A noticeable issue when comparing the pcap files seems to be at Fedora
> pcap
> > frame 8 and Mac OS 9.2 pcap frame 28 (configuration descriptor). It seems
> > the Mac OS side is missing 5 bytes and hence the packet is malformed.
> > (A run with Mac OS 9.0 as guest showed that this guest only missed 1 byte
> > in the response.)
>
> That is normal.  Note that the configuration descriptor is requested
> twice:  Once with a buffer large enough to see the wTotalLength field.
> and then again with a buffer large enough for the whole descriptor.
>
> > Also visible in the Mac OS pcap file at frame 53 is that it seems a setup
> > package is contained in an URB that is not suited for it.
>
> Looks more like a bug in the qemu pcap code, probably have to set some
> flag to indicate the setup section doesn't contain valid data instead
> of just leaving it all blank.
>
> Frame 55 is probably the problematic one.  Look at the timestamps.  The
> device seems to not answer, then after a while macos seems to try reset
> the device.
>
> Also the fedora trace has the bulk transfer data so wireshark can decode
> usb-storage commands and the scsi command wrapped inside.  That is not
> the case in the macos trace.  Not sure whenever that is another bug in
> the pcap code.  It could also indicate the bug in the ohci emulation
> which in turn causes macos fail ...
>
> > Qemu-system-ppc is started like this for the Mac OS guest:
> > ./qemu-system-ppc \
> > -M mac99,via=pmu \
> > -m 512 \
> > -boot c \
> > -serial stdio \
> > -L pc-bios \
> > -drive file=/home/hsp/Mac-disks/9.2.img,format=raw,media=disk \
> > -device usb-host,vendorid=0x058f,productid=0x6387,pcap=macos92.pcap
>
> Does an emulated usb stick work with macos?
>
> Hi Gerd,

Thanks for getting back to me.
Yes, usb-storage works just fine with

-drive if=none,id=stick,file=/home/hsp/Mac-disks/9.0.img,format=raw \
-device usb-storage,drive=stick

Best,
Howard

[-- Attachment #2: Type: text/html, Size: 2613 bytes --]

  reply	other threads:[~2021-02-09 17:19 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 [this message]
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
     [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='CABLmASEG3FiJ--7bQzZVJ1DtdFJSZ=a41yAf1QgEBf8BoGZk_w@mail.gmail.com' \
    --to=hsp.cat7@gmail.com \
    --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).