From: Lars Melin <larsm17@gmail.com>
To: Ethin Probst <ethindp@pm.me>
Cc: Alan Stern <stern@rowland.harvard.edu>,
"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: Thu, 16 May 2024 17:09:26 +0700 [thread overview]
Message-ID: <3c09b040-e76a-40b4-bf86-47469a6107cb@gmail.com> (raw)
In-Reply-To: <5jZCAcuLt5YeqkzP4xk28ICJ2WQUxY1eht4CjJNdnGymv3q6AIk3WugtglGVjqvu6BPVO7zHNx7LJeMnS71JUcoNpVZAMmz4o7G4vVyu0GU=@pm.me>
On 2024-05-16 12:56, Ethin Probst wrote:
> On Thursday, May 16th, 2024 at 00:19, Lars Melin <larsm17@gmail.com> wrote:
>
>> On 2024-05-16 05:12, Ethin Probst wrote:
>> I can also not find such a transition in your other two captures, all
>> descriptor readouts that includes USB Id are 2b5a:000c.
>
> This is what puzzles me as well. If I'm missing something it's at a
> level that USB Pcap can't capture. When I begin the capture, plug in
> the device and power it on, the second packet is always the right
> descriptor (pid 000d). There is no indicator in the capture that
> commands are sent before that pid is received. As for the other
> problem, yeah, that confused me too; I would've thought that another
> get descriptor request would've been sent, but apparently not, because
> when I remove the device from the VM and reattach it to the host, the
> pid is correct.
>
You can set up a USBPCap filter on id.Vendor and id.Product (2b5a:000c)
so that the capture will not start until you connect your device.
It will stop capture (logging on screen will stop) when the device
transition into 2b5a:000d so you can then close the pcap file.
The cmd making the transition should be near the end of your capture. :-)
Your IDA-disassembly is probably on the wrong file, I'd guess that the
.sys file in the driver directory corresponding to the .inf file for
the firmware loading Id is what handles firmware loading/checking.
best
Lars
next prev parent reply other threads:[~2024-05-16 10:09 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
2024-05-16 5:19 ` Lars Melin
2024-05-16 5:56 ` Ethin Probst
2024-05-16 10:09 ` Lars Melin [this message]
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=3c09b040-e76a-40b4-bf86-47469a6107cb@gmail.com \
--to=larsm17@gmail.com \
--cc=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 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.