From: Eddie Chapman <eddie@ehuk.net>
To: Oliver Neukum <oneukum@suse.com>,
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: Tue, 17 Nov 2026 14:41:48 +0000 [thread overview]
Message-ID: <13c443fc-cd23-4bb8-9aca-71b6b0f7b09d@ehuk.net> (raw)
In-Reply-To: <5ce29ee1-ea5e-4ebe-9a9a-f16844ad7b78@suse.com>
On 17/11/2026 08:34, Oliver Neukum wrote:
> On 16.11.26 22:04, Eddie Chapman wrote:
>> Bringing this a little bit back on topic for issues seen in the Linux
>> kernel with Asmedia USB to SATA devices, I'd be willing to wager that
>> a lot (if not most) of the time, if there is a firmware update out
>> there for a chip, there's an excellent chance it will resolve the
>> issue. But it is a mine field for users who are forced to take risks,
>> and it is a
>> very problematic situation for Linux to deal with to say the least.
>
> Hi,
>
> do they show a different version number?
> If not, I am afraid we will have to be conservative
> and blacklist everything.
>
> Regards
> Oliver
Hi Oliver,
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.
In the case of this particular device that reports "ASMT135x" as the
iProduct seems it's a little unusual, I'd love to see what's printed on
the chip on the PCB to confirm what it actually is, as you can easily
write any string you like to iProduct in the Windows firmware utility.
I've done that myself when updating firmware, here's one I did recently:
idVendor 0x174c ASMedia Technology Inc.
idProduct 0x235c DD25-C3-GY-BP
bcdDevice 1.00
iManufacturer 2 Orico
iProduct 3 DD25-C3-GY-BP
iSerial 1 234567890126
That device from Orico that came with much older firmware initially
reported a different idVendor and idProduct which I can't recall. But as
part of the firmware update those 2 fields changed to the above and it
is now recognised correctly by the kernel and works better, which is
good. But the string "DD25-C3-GY-BP" *I* chose and set that in the
firmware utility, it's just the model number of the device. But I could
have set it to "111111" or anything else.
regards,
Eddie
next prev parent reply other threads:[~2026-11-17 14:41 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 [this message]
2026-11-18 9:18 ` Oliver Neukum
-- 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=13c443fc-cd23-4bb8-9aca-71b6b0f7b09d@ehuk.net \
--to=eddie@ehuk.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=olivier.kaloudoff@gmail.com \
--cc=oneukum@suse.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