From: Tony Vroon <tony@linx.net>
To: linux-usb@vger.kernel.org
Cc: usb-storage@lists.one-eyed-alien.net, linux-kernel@vger.kernel.org
Subject: ums-realtek: Unneeded SubClass & Protocol entries (Fujitsu S760 laptop)
Date: Wed, 04 May 2011 14:00:09 +0100 [thread overview]
Message-ID: <4DC14DD9.9060407@linx.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Good afternoon,
The following message was emitted by my kernel:
usb 1-1.6: new high speed USB device number 5 using ehci_hcd
ums-realtek 1-1.6:1.0: This device (0bda,0138,3882 S 06 P 50) has
unneeded SubClass and Protocol entries in unusual_devs.h (kernel
2.6.39-rc5-00274-g609cfda)
Please send a copy of this message to <linux-usb@vger.kernel.org> and
<usb-storage@lists.one-eyed-alien.net>
scsi6 : usb-storage 1-1.6:1.0
This is the built-in card reader on a Fujitsu S760 laptop. Full lsusb
for the device in question:
Bus 001 Device 005: ID 0bda:0138 Realtek Semiconductor Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bda Realtek Semiconductor Corp.
idProduct 0x0138
bcdDevice 38.82
iManufacturer 1 Generic
iProduct 2 USB2.0-CRW
iSerial 3 20090516388200000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 CARD READER
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 5 Bulk-In, Bulk-Out, Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Could you CC me on any postings as I am not subscribed to the USB lists.
If there is further information you require, I am happy to provide it.
Regards,
- --
Tony Vroon
UNIX systems administrator
London Internet Exchange Ltd, Trinity Court, Trinity Street,
Peterborough, PE1 1DA
Registered in England number 3137929
E-Mail: tony@linx.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3BTdkACgkQp5vW4rUFj5rGPACgkOfjbenHWGPLpgOAPrzbHqjH
vJEAoKjva6ZsDs/rcdgh6TngHm63/beO
=qwHu
-----END PGP SIGNATURE-----
next reply other threads:[~2011-05-04 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 13:00 Tony Vroon [this message]
2011-05-04 16:35 ` ums-realtek: Unneeded SubClass & Protocol entries (Fujitsu S760 laptop) Alan Stern
2011-05-05 9:18 ` Tony Vroon
2011-05-05 13:57 ` Alan Stern
2011-05-05 14:22 ` Tony Vroon
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=4DC14DD9.9060407@linx.net \
--to=tony@linx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=usb-storage@lists.one-eyed-alien.net \
/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