From: Ethin Probst <ethindp@pm.me>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: Assistance getting the Universal Audio Apollo Solo USB to work with Linux
Date: Wed, 15 May 2024 22:12:54 +0000 [thread overview]
Message-ID: <N-wnVREkI4qROqLV1rCTIoLRiRzMGvywHt9QIdRD-e5AHby9wfaXcTn2V-Gd_UnmW-JomnWn6xGNhDhIeHIG3VHfHRFmnmPdZEPL8Qi5Gf4=@pm.me> (raw)
In-Reply-To: <ab4d0394-0d71-45a7-a79b-02e3c90f8ac8@rowland.harvard.edu>
[-- Attachment #1.1: Type: text/plain, Size: 622 bytes --]
On Sunday, May 12th, 2024 at 09:13, Alan Stern <stern@rowland.harvard.edu> wrote:
> ...
> Most likely, Windows sends some firmware to the device (which it needs
> in order to run properly) and then restarts the device.
I don't believe this is happening after trying to dig into the
captures a bit more. The firmware blobs that are in the archive are
over 100000 bytes, and though there are some significantly large
transfers, there isn't a single transfer that is the size of the
firmware blob. I can't tell for certain though; VirtualBox truncated
those large frames, so I'm uncertain what data is in them.
[-- Attachment #1.2: publickey - ethindp@pm.me - 0x846BFA7B.asc --]
[-- Type: application/pgp-keys, Size: 4337 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2024-05-15 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 20:07 Assistance getting the Universal Audio Apollo Solo USB to work with Linux Ethin Probst
2024-05-12 14:13 ` Alan Stern
[not found] ` <8fcVwO4QZdKndXMug6gtJOMJ7bCUM0dk3lfyiKsUSR1QFvQeQ1SdRkQUUTJd73wI_dgxAULH_oTBA64hdSb3JYiwAyejHLM7RccUgY1m4sM=@pm.me>
2024-05-13 1:14 ` Alan Stern
2024-05-15 22:12 ` Ethin Probst [this message]
2024-05-16 5:19 ` Lars Melin
2024-05-16 5:56 ` Ethin Probst
2024-05-16 10:09 ` Lars Melin
2024-05-17 19:10 ` Ethin Probst
2024-05-17 21:43 ` Ethin Probst
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='N-wnVREkI4qROqLV1rCTIoLRiRzMGvywHt9QIdRD-e5AHby9wfaXcTn2V-Gd_UnmW-JomnWn6xGNhDhIeHIG3VHfHRFmnmPdZEPL8Qi5Gf4=@pm.me' \
--to=ethindp@pm.me \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).