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: Fri, 30 Oct 2026 21:19:23 +0000 [thread overview]
Message-ID: <bug-220193-208809-5NV48wmjux@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220193-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220193
Craig H (craig@hesling.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |craig@hesling.com
--- Comment #8 from Craig H (craig@hesling.com) ---
I did a bit more digging and found two problematic scenarios.
There seems to be some VDS1022I, that has been supported by the GitHub project,
that identifies as the following:
bInterfaceClass 5 Physical Interface Device
bInterfaceSubClass 0
bInterfaceProtocol 0
From:
https://github.com/florentbr/OWON-VDS1022/issues/54#issuecomment-1120191539
I have also found a owon serial driver user whose OWON SDS1102 identifies as
the following:
bInterfaceClass 5 Physical Interface Device
bInterfaceSubClass 6 [unknown]
bInterfaceProtocol 80
From:
https://github.com/lucky62/OWON_SDS1102_Linux_Capture/issues/1
All variants:
https://github.com/linux4life798/owon-hds200-capture/blob/main/driver/USB_DESCRIPTORS.md
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-10-30 21:19 UTC|newest]
Thread overview: 10+ 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
2026-10-30 21:19 ` bugzilla-daemon [this message]
2026-11-03 3:27 ` bugzilla-daemon
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-5NV48wmjux@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 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.