From: Chmouel Boudjnah <chmouel@mandrakesoft.com>
To: linux-hotplug@vger.kernel.org
Subject: How usb hotplug works
Date: Wed, 17 Jan 2001 10:35:00 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97972768814005@msgid-missing> (raw)
--=-=-
Hi,
I cannot get works actually hotplug with a simple usb keyboard :
--=-=-T: Bus\x02 Lev\x01 Prnt\x02 Port\0 Cnt\x01 Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 1.00 Cls\0(>ifc ) Sub\0 Prot\0 MxPS= 8 #Cfgs= 1
P: Vendor\x05a4 ProdIDô98 Rev= 1.00
S: Manufacturer=NOVATEK
S: Product=USB Keyboard
C:* #Ifs= 2 Cfg#= 1 Atr† MxPwr\x100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls\x03(HID ) Sub\x01 Prot\x01 Driver=(none)
E: AdÅ(I) Atr\x03(Int.) MxPS= 8 Ivl= 10ms
I: If#= 1 Alt= 0 #EPs= 1 Cls\x03(HID ) Sub\x01 Prot\x02 Driver=(none)
E: AdÇ(I) Atr\x03(Int.) MxPS= 8 Ivl= 10ms
--=-=-
or the lsusb output attached.
It load the keybdev module but i believe is a STATIC_MODULES that get
loaded all the time ?
We (mandrake) currently plan to use usbd which works great and detect
the usbkbd without any problem via :
class 0x03 subclass 0x00 protocol 0x01 prio 2 kmod usbkbd
class 0x03 subclass 0x01 protocol 0x01 prio 2 kmod usbkbd
i have also to setup a :
post-install usbkbd modprobe keybdev
in my /etc/modules.conf
i have not yet looked too much at the how hotplug works, let me know
if it's the normal behavior...
--=-=-Content-Disposition: attachment; filename=keyboard
--=-=-Bus 002 Device 003: ID 05a4:9998 Ortek Technology, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 Interface
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x05a4 Ortek Technology, Inc.
idProduct 0x9998
bcdDevice 1.00
iManufacturer 4 NOVATEK
iProduct 54 USB Keyboard
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Devices
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 33
bNumDescriptors 1
bDescriptorType 34
wDescriptorLength 63
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 8
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Devices
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 33
bNumDescriptors 1
bDescriptorType 34
wDescriptorLength 31
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 8
bInterval 10
Language IDs: 0409
--=-=-
--=-=-
--
MandrakeSoft Inc http://www.chmouel.org
--Chmouel
--=-=-=--
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2001-01-17 10:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-hotplug-97972768814005@msgid-missing \
--to=chmouel@mandrakesoft.com \
--cc=linux-hotplug@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.