All of lore.kernel.org
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: Howard Spoelstra <hsp.cat7@gmail.com>
Cc: Programmingkid <programmingkidx@gmail.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Implementing isochronous transfers in hw/hcd-ohci.c
Date: Fri, 10 Sep 2021 13:51:16 +0200 (CEST)	[thread overview]
Message-ID: <aa588212-b557-223c-cf85-4c97b7d71cfa@eik.bme.hu> (raw)
In-Reply-To: <CABLmASHenOBj-15oOYvsai8YJuJHbnpVCXW3vAwF3kA=eoPiyQ@mail.gmail.com>

On Fri, 10 Sep 2021, Howard Spoelstra wrote:
> On Fri, Sep 10, 2021 at 7:07 AM Gerd Hoffmann <kraxel@redhat.com> wrote:
>
>> On Thu, Sep 09, 2021 at 05:06:17PM -0400, Programmingkid wrote:
>>> Hi Gerd,
>>>
>>> Howard and I were talking about USB audio problems with Mac OS guests.
>> We think the issue might be with frames being sent to the USB audio card
>> too soon. My guess is only one frame is suppose to be transmitted every 1
>> millisecond. I was also reading the todo notes in the file hw/hcd-ohci.c.
>> This is what it says:
>>>
>>>  * TODO:
>>>  *  o Isochronous transfers
>>>  *  o Allocate bandwidth in frames properly
>>>  *  o Disable timers when nothing needs to be done, or remove timer usage
>>>  *    all together.
>>>  *  o BIOS work to boot from USB storage
>>> */
>>>
>>> Do you think implementing isochronous transfers would fix the audio
>> problems Mac OS guest are experiencing?
>>
>> Most likely yes, audio devices typically use iso endpints.
>>
>> take care,
>>   Gerd
>>
>
> Hi,
>
> Below I pasted the first lines mentioning isochronous traffic from a pcap
> file when running fedora12 with the usb-audio device and the first lines
> from a pcap file running Mac OS 9.2 with the usb-audio device
>
> Fedora:
> 91 56.715001 host 0.5.1 USB 256 URB_ISOCHRONOUS out
> 92 56.715018 0.5.1 host USB 64 URB_ISOCHRONOUS out
>
> MacOS:
> 143 56.031989 host 0.16.1 USB 256 URB_ISOCHRONOUS out
> 144 56.032026 0.16.1 host USB 64 URB_ISOCHRONOUS out
>
> The usb-audio device works for the fedora guest, so would this not indicate
> that the iso endpoints are already working?
>
> The usb-audio device also work (for a limited amount of time) when running
> MacOS. Looking at USB logging in the Mac OS guest, to me it seems the MacOS
> side runs into timing issues when packages drift too far apart. It then
> finally gives up trying to keep the stream open.

I was also trying to find why the usb-audio device does not work with 
MorphOS but I could not figure it out. Now I have two machines (mac99 and 
pegasos2) that can boot MorphOS but usb-audio does not work with either so 
maybe it's not because of the USB controller. I've found there is a debug 
property that enables some logging: -device usb-audio,debug=1 but that did 
not reveal much more. It looks like MorphOS tries to query the device but 
replies come very slow (not sure if that's normal or a problem) then just 
gives up after a while. Maybe you can try comparing what Fedora and other 
OSes query as it may be we're missing some info in USB descriptors that 
other drivers than Linux's rely on but that's just a guess I haven't 
tested with Linux guest on pegasos2 or mac99 yet.

Regards,
BALATON Zoltan


  parent reply	other threads:[~2021-09-10 12:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 21:06 Implementing isochronous transfers in hw/hcd-ohci.c Programmingkid
2021-09-10  5:07 ` Gerd Hoffmann
2021-09-10  6:12   ` Howard Spoelstra
2021-09-10  7:51     ` Gerd Hoffmann
2021-09-10 11:51     ` BALATON Zoltan [this message]
2021-09-10 19:23       ` Programmingkid
2021-09-11  9:46         ` Howard Spoelstra
2021-09-11 15:10           ` 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=aa588212-b557-223c-cf85-4c97b7d71cfa@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=hsp.cat7@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=programmingkidx@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 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.