From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"harlydavidsen@gmail.com" <harlydavidsen@gmail.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Leif Lindholm (Nuvia address)" <leif@nuviainc.com>,
Andrew Fish <afish@apple.com>, "Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] USB isochronous transfers
Date: Tue, 20 Jul 2021 17:05:49 +0000 [thread overview]
Message-ID: <CO1PR11MB4929A3AFABAEE5CC0FFEA459D2E29@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJQtwF1eO6LqX6hE0vxjq45x_4fF4UD4_PdnF1kZZwwk5G6Few@mail.gmail.com>
PEI use of USB is usually limited to access to recovery images from media devices.
I would recommend focusing on UEFI components,
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ethin Probst
> Sent: Tuesday, July 20, 2021 8:33 AM
> To: devel@edk2.groups.io
> Cc: Leif Lindholm (Nuvia address) <leif@nuviainc.com>; Andrew Fish <afish@apple.com>; Ni, Ray <ray.ni@intel.com>
> Subject: [edk2-devel] USB isochronous transfers
>
> Hello all,
>
> A few days ago Leif determined that the USB DXE does not implement
> isochronous transfers. This will make USB Audio quite impossible as
> the audio data endpoint requires isochronous transfers.
>
> I was looking at the EHCI driver but I can't determine a couple things:
>
> - Isochronous transfers have a different structure compared to other
> URB types. (Each URB type may have its own structure -- I haven't
> checked.)
> - I can't seem to figure out how this is handled in, say, EhciDxe.
> - If we were to try and implement this -- though I'm not quite sure
> how -- would we need to modify the PEIs too?
>
> --
> Signed,
> Ethin D. Probst
>
>
>
>
next prev parent reply other threads:[~2021-07-20 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 15:32 USB isochronous transfers Ethin Probst
2021-07-20 17:05 ` Michael D Kinney [this message]
2021-07-20 17:23 ` [edk2-devel] " Andrew Fish
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-list 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=CO1PR11MB4929A3AFABAEE5CC0FFEA459D2E29@CO1PR11MB4929.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/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