Brad Hards wrote:
>
>
>
>
>>Loading these modules caused the directory hid to be created in
>>/dev/usb, and the device file /dev/usb/hid/hiddev0 to be created (with
>>the correct major & minor)
>>
>>lilly:[/dev/usb/hid]# ls -l
>>total 0
>>crw-rw-rw- 1 root root 180, 96 Dec 31 1969 hiddev0
>>
>>
>So this device was not taken by the HID input code (either because you didn't
>enable it in the kernel, or because the radio has the wrong Application).
>
Do you mean the input core support? If so, that's turned on.
#
# Input core support
#
CONFIG_INPUT=m
CONFIG_INPUT_KEYBDEV=m
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_EVDEV=m
The radio identifies itself as an hid device, so I don't understand what
you meant by "wrong application", above.
>
>
>>3. I ran the evtest code
>>
>>
>That won't help. You need something that understands hiddev events, not input
>events.
>
I thought that having evdev already loaded when the hid autoloaded would
cause input registration to occur via a call to event_register_device.
--Doug
--
====================================================================
Douglas Roberts, D-2 | "There is no reason anyone would
Los Alamos National Laboratory | want a computer in their home."
^ | -- Ken Olsen, President, Chairman
(505)-667-4569 | and Founder of Digital Equipment
[EMAIL PROTECTED] | Corp., 1977
====================================================================
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
