Palm m515 on Red Hat 7.2 with usbserial.o (without visor.o)

I've been a PalmOS user for some time. My first handheld, an original PalmV with a 3Com logo underneath the power button lasted until May 2003, when the digitizer on the screen finally gave out. I have since replaced it with an Palm m515, mostly for the convience of keeping my data in one format. So, here is some information that you may or may not find useful.

I run a very custom kernel on Red Hat 7.2, kernel version 2.4.7-10custom. Outdated you say? Well, I've backported quite a few newer kernel patches into it, but I'm running some odd hardware these days, and I don't feel like porting my fixes forward. The latest version I found has support for the m515 via the visor.o module. My version does not. So, I went forth to backport the fix into my version of the driver. As I started, other things soon came up, and I needed a quick fix. So, here's my quick fix.

Assuming that you have built the kernel with the modules usbserial.o, then you're half way there. Otherwise, you'll have to build that first.

Next link /dev/pilot (or /dev/palm or whatever you want) to /dev/ttyUSB1 via:

ln -s /dev/ttyUSB1 /dev/pilot

Having done this, we can now use usbserial.o to link us to the palm via this command (must be run as root):

insmod usbserial vendor=0x0830 product=0x0003

That's it. Having done that, you can use a recent version of Jpilot and pilot-link (with USB support) to sync with the palm. I haven't had any problem with this setup. You could also do this with other USB Palm handhelds I suspect, although you would have to change the vendor and product ids. (I just plugged the handheld in, and hit the hotsync button and looked in /var/messages to see what it said. It had the Vendor and Product ID's there...)

If you don't want to su to root to type that everytime, just stick the insmod line in a start file. I put in my printer startup for some odd reason, which I'm sure made perfect since late the night I did it. :-)