QUOTE(BarryW @ Jul 4 2006, 01:39 PM)
Good to see you're still looking into it. My forhead hurts. I have thought about flashing pdax just to see if it works that way.
OK, got the unit via mail-order. Got through the "device not claimed" (modprobe hid). Created /dev/hiddev0, but still getting "unable to find device" problem.
But I have only been working on this for a couple of hours. Unfortunately, I don't have strace to see exactly what the program (wispy_curses) is missing.
I did plug it into my LinuxPPC laptop, and after making wispy_curses and wispy_gtk, it works fine.
I do see differences between the LinuxPPC (kernel 2.6) and the Zaurus (2.4), which I am not sure about. On LinuxPPC, I see that it is the usbfs driver that is being used. I don't find a usbfs driver in the 2.4 kernel for the Zaurus (this could be a 2.6 only thing).
Barry, is your Slackware Linux 2.4 or 2.6? Can you do a cat /proc/bus/usb/devices and see what driver the wispy is using? Mine reports:
P: Vendor=1781 ProdID=083e Rev= 1.00
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 98mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbfs