[linux-usb-devel: I had a detailed discussion with Brad Hards, but I seem to have dropped the CC: somewhere along the line. Sorry.]
> On Thu, 16 May 2002 07:14, Jens Kilian wrote: > > Until now I assumed that the fixed mapping of usage codes to input event > > codes was intentional and should be preserved; if that's not the case, that > > would indeed be a solution. (But then there's an additional problem: the > Perhaps it would help to look at some other input drivers (eg joystick in 2.4, > or the linuxconsole CVS (http://linuxconsole.sf.net and troll through)). The > mapping can't be 1-1 on every driver :) > > > documented interface by which an application finds out what events it can > > expect uses a bitmap where each bit corresponds to one value of > > input_event.code; we might run out of bits quickly. I don't remember if the > > bitmap can be enlarged beyond 32 bits.) > It definately can. Look at the EV_KEY type, which has hundreds of bits. > You only need 9 bits for your driver... Ah hah! I missed this completely (I *should* have read your HID document more carefully). Thanks; I'll think up some more alternative proposals. Have a nice day, Jens. -- mailto:[EMAIL PROTECTED] phone:+49-7031-464-7698 (TELNET 778-7698) http://www.bawue.de/~jjk/ fax:+49-7031-464-7351 PGP: 06 04 1C 35 7B DC 1F 26 As the air to a bird, or the sea to a fish, 0x555DA8B5 BB A2 F0 66 77 75 E1 08 so is contempt to the contemptible. [Blake] _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
