Hi. It was suggested to me that you guys could help. I inherited a project that involves writing a user-space program to communicate with a usb digital radio. When plugged in, the radio device identifies itself as an hid device, so I guess that's good news as I should be able to use the Linux hid driver. I'm running Mandrake 9.0 (gcc3.2, kernel 2.4.19-16mdkcustom which I built).
To get started, I was going to run the evtest code referred to by https://bugzilla.redhat.com/bugzilla/showattachment.cgi?attach_id=39264 and that's where the problems started. Here's what I did 1. modprobe evdev 2. I plugged the radio device in, and Mandrake's hotplug usb.agent recognized the device as an hid device and logged the following: Oct 9 09:59:54 lilly kernel: hub.c: USB new device connect on bus2/1, assigned device number 3 Oct 9 10:00:00 lilly kernel: usb.c: USB device 3 (vend/prod 0x6a3/0x100b) is not claimed by any active driver. Oct 9 10:00:03 lilly /etc/hotplug/usb.agent: Setup hid for USB product 6a3/100b/100 Oct 9 10:00:03 lilly kernel: usb.c: registered new driver hiddev Oct 9 10:00:03 lilly kernel: usb.c: registered new driver hid Oct 9 10:00:07 lilly kernel: usb-uhci.c: interrupt, status 3, frame# 1865 Oct 9 10:00:12 lilly kernel: hiddev0: USB HID v1.00 Pointer [SAITEK RF Tester] on usb2:3.0 Oct 9 10:00:12 lilly kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <[EMAIL PROTECTED]> Oct 9 10:00:12 lilly kernel: hid-core.c: USB HID support drivers 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 3. I ran the evtest code lilly:[~/radio/driver]% ./evtest /dev/input/event0 evtest: No such file or directory 4. cd /dev/input, and sure enough, there is not event0 device file, nor is there an evdev0 file. 5. Went to evdev.c and sprinkled a few printk's through it to find out what was happening, and found that the only function firing was evdev_init. 6. Unloaded evdev, input, hid, went to input.c and added a few more printk's and found that modprobe evdev does cause input to be loaded by calling input's input_register_handler, but the device files event0 and evdev0 were not being created. At this point I realized that I didn't have a clue as to what was going on, and needed some help. What I need to do is get my user-space program talking to my hid digital radio device. Any help, suggestions, pointers, flames, etc. greatly appreciated. TIA, --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
