From: Oliver Neukum <oneukum@suse.com>
To: Eddie Chapman <eddie@ehuk.net>,
Olivier Kaloudoff <olivier.kaloudoff@gmail.com>
Cc: linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
gregkh@linuxfoundation.org, usb-storage@lists.one-eyed-alien.net
Subject: Re: [PATCH] usb: uas: ignore UAS for ASMT135x bridges (174c:55aa)
Date: Wed, 18 Nov 2026 10:18:13 +0100 [thread overview]
Message-ID: <399a19e6-9dc0-408f-89b6-3c326bb07f30@suse.com> (raw)
In-Reply-To: <13c443fc-cd23-4bb8-9aca-71b6b0f7b09d@ehuk.net>
On 17.11.26 15:41, Eddie Chapman wrote:
> Yes totally agreed, if the firmware version cannot be easily read from the device somehow, today, then the only and safest option for the kernel is to treat all such devices as if running older firmware. I mean, it is definitely *possible* to query the device to find its firmware version because Asmedia has firmware update utilities that do that under Windows. But I've no idea how. In an ideal world someone from Asmedia would one day provide a patch that exposes that info to the kernel somehow. In the absence of that perhaps one day someone will have the time to sniff USB packets using Qemu to see how it is done and submit a patch.
Hi,
do you know whether anyone has tried talking to Asmedia?
Regards
Oliver
next prev parent reply other threads:[~2026-11-18 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 17:49 [PATCH] usb: uas: ignore UAS for ASMT135x bridges (174c:55aa) Olivier Kaloudoff
2026-11-16 21:04 ` Eddie Chapman
2026-11-17 8:34 ` Oliver Neukum
2026-11-17 14:41 ` Eddie Chapman
2026-11-18 9:18 ` Oliver Neukum [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-13 22:19 Olivier Kaloudoff
2026-10-13 22:23 ` sashiko-bot
2026-10-14 5:00 ` Greg KH
2026-11-13 18:32 ` Eddie Chapman
2026-10-11 16:42 Olivier Kaloudoff
2026-10-11 16:47 ` sashiko-bot
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=399a19e6-9dc0-408f-89b6-3c326bb07f30@suse.com \
--to=oneukum@suse.com \
--cc=eddie@ehuk.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=olivier.kaloudoff@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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