From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220193] PATCH 6.1 082/167 which adds support for Owon HDS200 breaks functionality of Owon VDS1022
Date: Thu, 15 Oct 2026 03:02:10 +0000 [thread overview]
Message-ID: <bug-220193-208809-Mr8tmm38xB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220193-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220193
--- Comment #7 from Wei Huang (daway320@163.com) ---
Hi leStoppe,
No worries about the delay - and thanks, the dump is exactly what was needed.
Quick summary of where this landed: the interface tuple is what distinguishes
the VDS1022 (class 5, subclass 6, protocol 0x50) from the HDS200 series (class
5, subclass 0, protocol 0, per the HDS272S dump in the commit message of the
original driver). So the fix is to match the HDS200's full tuple, which leaves
the VDS1022 unclaimed and lets your libusb tool work out of the box again.
I've submitted the updated patch (v2) on the linux-usb mailing list with this
analysis and both descriptor dumps as evidence:
https://lore.kernel.org/linux-usb/20261015025456.3927808-1-huangwei@kylinos.cn/
Thanks again - this settled the last open question from the review.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-10-15 3:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 21:09 [Bug 220193] New: PATCH 6.1 082/167 which adds support for Owon HDS200 breaks functionality of Owon VDS1022 bugzilla-daemon
2026-08-10 9:47 ` [Bug 220193] " bugzilla-daemon
2026-08-10 19:35 ` bugzilla-daemon
2026-08-11 13:24 ` bugzilla-daemon
2026-08-26 2:50 ` bugzilla-daemon
2026-10-12 8:18 ` bugzilla-daemon
2026-10-13 21:28 ` bugzilla-daemon
2026-10-15 3:02 ` bugzilla-daemon [this message]
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=bug-220193-208809-Mr8tmm38xB@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/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