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, 13 Oct 2026 21:28:41 +0000 [thread overview]
Message-ID: <bug-220193-208809-oXQUO3PKcI@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 #6 from leStoppe (lestoppe@gmail.com) ---
Apologies for the delayed response! I'll lookup the mail thread and reply there
as well.
1. I use this software : https://github.com/florentbr/Owon-VDS1022
What you said is exactly what is happening. This software uses libusb to
access the VDS1022. The breakage started when the kernel automatically started
to load the usb-simple-serial driver. The application could access it only
after I blacklisted the driver.
3. The VDS1022 supports some SCPI commands. I can enable the socket for it via
the userspace application above. I'm not sure the command set is same as HDS200
or if it can be done through the serial interface instead of libusb
2. Pasting the output of lsusb -v -d 5345:1234 below :
------------------------------------------------------------------------
Bus 001 Device 003: ID 5345:1234 Owon PDS6062T Oscilloscope
Negotiated speed: Full Speed (12Mbps)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x5345 Owon
idProduct 0x1234 PDS6062T Oscilloscope
bcdDevice 10.01
iManufacturer 1 S
iProduct 2 U
iSerial 3 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0029
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 50mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 5 Physical Interface Device
bInterfaceSubClass 6 [unknown]
bInterfaceProtocol 80
iInterface 0
** UNRECOGNIZED: 09 21 00 01 00 01 22 00 00
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
cannot read device status, Resource temporarily unavailable (11)
-----------------------------------------------------------------------
--
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-13 21:28 UTC|newest]
Thread overview: 7+ 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 [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-oXQUO3PKcI@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