>> 1) I've got a SuperPen <snip> > If the SuperPen (got a URL to show what it looks like?) really does use > the same protocol as the wacom devices, then it'll need to be added to > the driver source code. If the same source told you that it'll work, > and all you need to do is to hack the modules table, then I'm not > optimistic about your chances. Thanks for responding.It *may* not use the same protocol... The superpen website is at http://www.superpen.com When you say it'll need to be added to the driver source code - in what sense do you mean this? Why does hacking the modules table make you pessimistic? I know nothing about USB and I can't seem to find the answers to the questions I need from the FAQs... I assume it is very difficult to modify the driver source? > >> 2) I also just got a free IBM NetVista USB mouse <snip> > Can you post the contents of /proc/bus/usb/devices with both of these > devices plugged in? That is pretty important to get the next step > sorted out.>
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=d400 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=5543 ProdID=0004 Rev= 0.00 C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=hid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=9ms T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=04b3 ProdID=3100 Rev= 4.41 C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=hid E: Ad=81(I) Atr=03(Int.) MxPS= 5 Ivl=10ms Vendor 5543 is the SuperPen and 04b3 the IBM mouse. > Also, can you get > >http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/linuxconsole/ruby/utils/evtest.c?rev=1.19> > and test each device? For the mouse, it would help if you could> > annotate the> output with what actions corresponded to which outputs (eg > "these three lines occurred when I pressed and released the middle > button")> Wow! That's exactly the sort of thing I was looking for. Unfortunately when trying to compile (just using gcc evtest.c) I get : evtest.c: In function `main': evtest.c:168: `EV_SYN' undeclared (first use in this function) evtest.c:168: (Each undeclared identifier is reported only once evtest.c:168: for each function it appears in.) Should I be replacing EV_SYN with a different definition or something? For now I've commented it out (replaced with a 0) and the program compiles. The output it produces is for event0 (the ibm mouse) : Input driver version is 1.0.0 Input device ID: bus 0x3 vendor 0x4b3 product 0x3100 version 0x441 Input device name: "04b3:3100" Supported events: Event type 1 (Key) Event code 272 (LeftBtn) Event code 273 (RightBtn) Event code 274 (MiddleBtn) Event type 2 (Relative) Event code 0 (X) Event code 1 (Y) Event code 2 (Z) Event code 8 (Wheel) Testing ... (interrupt to exit) for event1 (the superPen) Input driver version is 1.0.0 Input device ID: bus 0x3 vendor 0x5543 product 0x4 version 0x0 Input device name: "UC-LOGIC Tablet WP5540U" Supported events: Event type 1 (Key) Event code 272 (LeftBtn) Event code 273 (RightBtn) Event code 274 (MiddleBtn) Event code 275 (SideBtn) Event code 276 (ExtraBtn) Event code 277 (ForwardBtn) Event code 330 (Touch) Event type 2 (Relative) Event code 0 (X) Event code 1 (Y) Event code 2 (Z) Event code 8 (Wheel) Event type 3 (Absolute) Event code 0 (X) Value 0 Min 0 Max 32767 Fuzz 127 Flat 2047 Event code 1 (Y) Value 0 Min 0 Max 32767 Fuzz 127 Flat 2047 Event code 24 (Pressure) Value 0 Min 0 Max 511 Fuzz 1 Flat 31 Event code 28 (?) Value 0 Min 0 Max 255 Flat 15 Testing ... (interrupt to exit) but nothing is produced in response to using either device (could that be because I've commented out EV_SYN - the statement it was originally in tested for equivalence i.e. ev.something==EV_SYN so I then replaced it with != but it didn't make a difference. So, I take it both devices 'report' the types of events that the USB 'controller' can expect? Does this mean that I can just tie them to standard driver? many thanks, Ben ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
