Kay Sievers wrote:
On Mon, Apr 27, 2009 at 00:31, Phil Endecott
<phil_cmcsb_endec...@chezphil.org> wrote:
So protocol==0 is not specific to this unusual device; even a keyboard or
mouse will have 0 for its non-boot interfaces. ÃÂ So the current logic will
only create /dev/by-id|path nodes for boot interfaces. ÃÂ Is that intentional?
These links got added to distinguish multiple keyboards on
mainframe-like servers, that's why the rules have been so strict so
far, and cover only "real" input devices. :)
Hmm, OK; so how am I supposed to identify things that may be connected
to different sockets and enumerated in different orders each time I use them?
We see several mouse-like devices, which are not covered by that, and
we might need to find a scheme to include them in the link creation.
We need to be careful here though, because there are tons of HID
devices with "00" which have nothing to do with input devices in the
usual sense. I have a thermometer which is exactly like that. :)
Right. I have a Wi-Spy which I think is a HID device. Does it do any
harm to add links for things like that?
What kind of kernel devices does this device create, I mean, if you
run "udevadm monitor --kernel" and plug it in, what does it say?
(I should say first that I re-discovered this bug because the computer
that I was using the PowerMate with has died; I have been trying to
remember what I had to do to make it work so that I can use it with the
replacement. I don't have it working properly yet, I think because
something in X has changed. The following info is from the new
not-yet-working machine.)
# udevadm monitor --kernel
udevmonitor will print the received events for:
UEVENT the kernel uevent
UEVENT[1240788686.318926] add
/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.1 (usb)
UEVENT[1240788686.322049] add
/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.1/1-4.1:1.0 (usb)
UEVENT[1240788686.325014] add /class/input/input15 (input)
UEVENT[1240788686.325203] add /class/input/input15/event12 (input)
UEVENT[1240788686.325301] add /class/usb_endpoint/usbdev1.9_ep81
(usb_endpoint)
UEVENT[1240788686.325394] add /class/usb_endpoint/usbdev1.9_ep02
(usb_endpoint)
UEVENT[1240788686.325549] add /class/usb_device/usbdev1.9 (usb_device)
UEVENT[1240788686.325651] add /class/usb_endpoint/usbdev1.9_ep00
(usb_endpoint)
Care to show the entire sequence?
Not sure what you mean.
Is it "inputX" only for the input devices, or do you get also a "mouseX" device?
I get only an eventX device:
# tree /dev/input
/dev/input
|-- by-id
| |-- usb-Apple_Inc._Apple_Keyboard-event-kbd -> ../event10
| |-- usb-Griffin_Technology__Inc._Griffin_PowerMate-event-misc -> ../event12
| |-- usb-Kingsis_Peripherals_Evoluent_VerticalMouse_2-event-mouse ->
../event9
| `-- usb-Kingsis_Peripherals_Evoluent_VerticalMouse_2-mouse -> ../mouse1
|-- by-path
| |-- pci-0000:00:1d.1-usb-0:1:1.0-event-mouse -> ../event9
| |-- pci-0000:00:1d.1-usb-0:1:1.0-mouse -> ../mouse1
| |-- pci-0000:00:1d.7-usb-0:4.1:1.0-event-misc -> ../event12
| |-- pci-0000:00:1d.7-usb-0:4.2:1.0-event-kbd -> ../event10
| |-- pci-0000:00:1d.7-usb-0:4.2:1.1-event- -> ../event11
| |-- platform-i8042-serio-0-event-kbd -> ../event7
| |-- platform-i8042-serio-1-event-mouse -> ../event8
| |-- platform-i8042-serio-1-mouse -> ../mouse0
| `-- platform-pcspkr-event-spkr -> ../event5
|-- event0
|-- event1
|-- event10
|-- event11
|-- event12
|-- event2
|-- event3
|-- event4
|-- event5
|-- event6
|-- event7
|-- event8
|-- event9
|-- mice
|-- mouse0
`-- mouse1
Also, care to add the full section of "lsusb -v" for this device?
Bus 001 Device 009: ID 077d:0410 Griffin Technology PowerMate
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x077d Griffin Technology
idProduct 0x0410 PowerMate
bcdDevice 4.00
iManufacturer 1 Griffin Technology, Inc.
iProduct 2 Griffin PowerMate
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 Media Controller
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 5 Endpoint 1
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 74
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0006 1x 6 bytes
bInterval 10
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered)
Cheers, Phil.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
