From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215361] New: SL-6000 zaurus USB error - 'bad CDC descriptors'
Date: Sun, 19 Dec 2021 06:14:00 +0000 [thread overview]
Message-ID: <bug-215361-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215361
Bug ID: 215361
Summary: SL-6000 zaurus USB error - 'bad CDC descriptors'
Product: Drivers
Version: 2.5
Kernel Version: 3/4/5
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: bids.7405@bigpond.com
Regression: No
A 'bad CDC descriptors' error occurs when plugging the Sharp SL-6000 zaurus
into USB. It was working in 2.6.32 but has been broken from kernel 3 onwards.
usb 5-2: new full-speed USB device number 2 using uhci_hcd
usb 5-2: New USB device found, idVendor=04dd, idProduct=9032
usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 5-2: Product: SL-6000
usb 5-2: Manufacturer: Sharp
usb 5-2: bad CDC descriptors
usbcore: registered new interface driver cdc_ether
In 2.6.32 the following lines were included in dmesg:
usb0: register 'zaurus' at usb-0000:00:14.0-2, pseudo-MDLM (BLAN) device,
fe:1b:05:23:49:7f
usbcore: registered new interface driver zaurus
--
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 reply other threads:[~2021-12-19 6:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 6:14 bugzilla-daemon [this message]
2021-12-19 20:46 ` [Bug 215361] SL-6000 zaurus USB error - 'bad CDC descriptors' bugzilla-daemon
2021-12-19 22:27 ` bugzilla-daemon
2021-12-20 8:37 ` [Bug 215361] New: " Greg KH
2021-12-20 8:37 ` [Bug 215361] " bugzilla-daemon
2021-12-21 8:07 ` bugzilla-daemon
2021-12-21 8:20 ` Greg KH
2021-12-21 8:20 ` bugzilla-daemon
2022-01-16 4:23 ` bugzilla-daemon
2022-01-26 12:31 ` Greg KH
2022-01-26 12:32 ` bugzilla-daemon
2022-01-27 2:25 ` bugzilla-daemon
2022-01-27 6:00 ` bugzilla-daemon
2022-01-27 7:45 ` bugzilla-daemon
2022-01-27 15:50 ` bugzilla-daemon
2022-01-28 23:52 ` bugzilla-daemon
2022-04-22 4:00 ` 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-215361-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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.