public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael Brown" <mcb30@ipxe.org>
To: devel@edk2.groups.io, harlydavidsen@gmail.com
Subject: Re: [edk2-devel] EFI_AUDIO_OUTPUT_PROTOCOL: assistance with VirtIO initialization
Date: Tue, 6 Jul 2021 13:53:44 +0100	[thread overview]
Message-ID: <80a7f1ae-7e2a-4e26-3a3e-90157af91bdb@ipxe.org> (raw)
In-Reply-To: <CAJQtwF0odTO+KB7wr6Jo6bvirjiCGr9rJgLU7ucHAyAsE6ZOPQ@mail.gmail.com>

On 02/07/2021 19:22, Ethin Probst wrote:
> Update: I just realized I'd made a typo -- the unknown request is
> actually a get_min request.
> 
> On 7/2/21, Ethin Probst <harlydavidsen@gmail.com> wrote:
>> Setup Data
>>      bmRequestType: 0xa1
>>          1... .... = Direction: Device-to-host
>>          .01. .... = Type: Class (0x1)
>>          ...0 0001 = Recipient: Interface (0x01)
>>      bRequest: 130
>>      wValue: 0x0201
>>      wIndex: 1536 (0x0600)
>>      wLength: 2

That doesn't immediately make sense to me in the context of reading 
sections 5.2.1.2 and 5.2.2.2.2 of the audio spec, but feel free to post 
the whole wireshark capture (off-list!) and I can take a look.

Michael

  reply	other threads:[~2021-07-06 12:53 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
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 [this message]
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=80a7f1ae-7e2a-4e26-3a3e-90157af91bdb@ipxe.org \
    --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