Sorry for the html in the previous message, I thought it was turned off..
--Doug
Brad Hards wrote:
>>>
>>>
>>Do you mean the input core support? If so, that's turned on.
>>
>>
>In later kernels, there is a config option for HID -> input layer. It is
>CONFIG_USB_HIDINPUT.
>
>
Yes, that's turned on too:
#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
CONFIG_USB_WACOM=m
>
>
>>The radio identifies itself as an hid device, so I don't understand what
>>you meant by "wrong application", above.
>>
>>
>You're going to have to read the HID spec some more times, before
you'll be
>able to write a userspace app :-)
>
You got that one right ;-}. I have mucked around in the kernel in the
past, though, so I'm not totally new. About 4 or 5 years ago I hacked
a fix to the cardbus driver in RH5.3(I think), because it wasn't working
on an old Gateway laptop I had at the time. That earned me a spot on
the RH developer's list, but I did not take advantage when RH did their
IPO. RH closed today at $3.84, so I guess I didn't miss out too much.
>In the HID spec, Application (I'm using caps to denote a defined term)
is a
>specific value returned by the HID interface. It is used to determine
things
>like the usage pages. Look in the hid code (hid.h) and find the test for
>IS_INPUT_APPLICATION. If the Application(s) reported by the HID device
>matches, then the device is considered an input device, and gets
associated
>with the hid-input code. Otherwise it goes to hiddev.
>
>
Ok, here's the macro:
#define IS_INPUT_APPLICATION(a) (((a >= 0x00010000) && (a <=
0x00010008)) || (a == 0x00010080) || ( a == 0x000c0001))
>The dump-events code I gave a link to in my previous email can tell
you what
>the Applications are for your device.
>
And here they are:
Application 0 is 0xffa00001 (Needs to be added)
Report id: 1 (1 fields)
Field: 0: app: ffa00001 phys ffa00002 flags 2 (1 usages) unit 0 exp 0
Usage: ffa00003 val 0 idx 0
Report id: 2 (1 fields)
Field: 0: app: ffa00001 phys ffa00004 flags 2 (1 usages) unit 0 exp 0
Usage: ffa00005 val 0 idx 0
Report id: 3 (1 fields)
Field: 0: app: ffa00001 phys ffa00006 flags 2 (1 usages) unit 0 exp 0
Usage: ffa00007 val 0 idx 0
Report id: 4 (1 fields)
Field: 0: app: ffa00001 phys ffa00008 flags 2 (1 usages) unit 0 exp 0
Usage: ffa00009 val 0 idx 0
Waiting for events ... (interrupt to exit)
Which sort of leaves me using /dev/usb/hid/hiddev0 to talk to my radio,
which is perfectly fine with me, as long as I can figure out how to do it...
Can you (continue) to help by suggesting an approach? I don't mind
patching the kernel, and I mind using hiddev. All I really need to do
at the moment is to send a control sequence to the radio and read it's
response back.
Thanks for the help so far...
--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
