All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 03 Nov 2026 03:27:49 +0000	[thread overview]
Message-ID: <bug-220193-208809-m5523VrTs6@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 #9 from Wei Huang (daway320@163.com) ---
Hi Craig,

Thanks for the additional device data - this is very helpful, and
it changes the picture significantly.

The VDS1022I reporting the same (5, 0, 0) tuple as the HDS200
means the interface-level narrowing approach I proposed doesn't
reliably separate the device families. I've posted the analysis
and options on the mailing list:

https://lore.kernel.org/linux-usb/20260810091322.2201740-1-huangwei@kylinos.cn/

In short: OWON reuses the same tuples across devices with
different userspace needs, so there may be no clean kernel-side
fix. The question is now with the USB serial maintainer on how
to proceed.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2026-11-03  3:27 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
2026-11-03  3:27 ` 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-m5523VrTs6@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.