From: "Ethin Probst" <harlydavidsen@gmail.com>
To: Michael Brown <mcb30@ipxe.org>
Cc: devel@edk2.groups.io
Subject: Re: [edk2-devel] EFI_AUDIO_OUTPUT_PROTOCOL: assistance with VirtIO initialization
Date: Thu, 1 Jul 2021 13:10:45 -0500 [thread overview]
Message-ID: <CAJQtwF3WnWCvgmfPJ6NFS9GuqwPdWeOZz1Nnn3WmeZm5A7xDmg@mail.gmail.com> (raw)
In-Reply-To: <f81fc950-d368-15be-92ea-56c251ee597f@ipxe.org>
The first: I don't know how to retrieve the descriptors on the UEFI
API. I've looked at the Chaos Key DXE, if memory serves, or the
display port one -- one of the two. One of them contained a
ReadDescriptor() function, and so I've borrowed that, but that doesn't
really help much.
On 7/1/21, Michael Brown <mcb30@ipxe.org> wrote:
> On 01/07/2021 00:01, Ethin Probst wrote:
>> So Leif and I have been working on USB Audio but we've run into a snag.
>> We've encountered a problem -- neither of us knows enough about USB to
>> figure out how to get the class-specific AC interface descriptors, and
>> those contain vital information that I need to be able to control the
>> audio device.
>
> Do you mean that you can't figure out how to retrieve the descriptors
> via the UEFI APIs, or that you don't know how to interpret the
> descriptors after retrieval?
>
> Thanks,
>
> Michael
>
--
Signed,
Ethin D. Probst
next prev parent reply other threads:[~2021-07-01 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 23:01 EFI_AUDIO_OUTPUT_PROTOCOL: assistance with VirtIO initialization Ethin Probst
2021-07-01 14:15 ` [edk2-devel] " Michael Brown
2021-07-01 18:10 ` Ethin Probst [this message]
2021-07-02 8:59 ` Laszlo Ersek
2021-07-02 9:41 ` Michael Brown
[not found] ` <168DEFFB0E406B59.30759@groups.io>
2021-07-02 9:46 ` Michael Brown
2021-07-02 18:18 ` Ethin Probst
2021-07-02 18:22 ` Ethin Probst
2021-07-06 12:53 ` Michael Brown
2021-07-02 8:54 ` Laszlo Ersek
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=CAJQtwF3WnWCvgmfPJ6NFS9GuqwPdWeOZz1Nnn3WmeZm5A7xDmg@mail.gmail.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