-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 10 Oct 2002 08:47, Douglas Roberts wrote: > Ok, here's the macro: > > #define IS_INPUT_APPLICATION(a) (((a >= 0x00010000) && (a <= > 0x00010008)) || (a == 0x00010080) || ( a == 0x000c0001))
> 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 This application (and the usages) are from the vendor specific space. > 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... hiddev isn't too bad, and the event interface is really only good for input devices (ie. if doesn't look like a keyboard or a mouse, its going to be trouble). > 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. Note: You are getting close to my "no more free consultancy" limit. You really need to know what the different usages do (aka ask the vendor). That'll be step one. The input layer can really only handle a few specific outputs (eg LEDs, sound, force feedback). If you can't map your requirements to that, event interface isn't going to help - you'll need to go the hiddev interface. Here is another (even rougher) bit of code.http://www.frogmouth.net/hid-doco/examples/hiddev-misc/write-events.c It is a demo I hacked up (from dump-events, which is why it looks identical) at a conference - it shows how to use hiddev to send reports to a keyboard to turn the LED on and off. You'll need to disable CONFIG_USB_HIDINPUT to test it on a keyboard - otherwise the keyboard won't be on a hiddev interface, per my previous explanation. Brad - -- http://linux.conf.au. 22-25Jan2003. Perth, Aust. I'm registered. Are you? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9pLbmW6pHgIdAuOMRApunAJ90Ys1ZI5+ByeV7vgiC16z3Unxb7QCfc92D e5McV8Sia1Gxgi1NmqQcJUQ= =/ytL -----END PGP SIGNATURE----- ------------------------------------------------------- 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
