USB Visor and one-click syncing

[David Saff <saff MIT EDU>]

All,

I have successfully set up hotsyncing between my visor deluxe and Redhat
7.2 / Ximian Gnome system using the standard Visor USB cradle. 
pilot-xfer works correctly, and pilot-link, gnome-pilot, and Evolution
are almost right.  Currently, however, it isn't quite a one-touch
operation: I push the hotsync button on my cradle, and it indicates that
it is "Connecting to Desktop..."  I then have to pull up System Settings
/ Pilot Link / Devices.  I have only one device configured, described
below.  I select the device and choose Edit.  I then hit OK on the edit
screen, and OK on the Pilot Link control applet.  Immediately, my pilot
indicates that it is Identifying User, and syncing begins.

This is acceptable, but I'd really like it if I could get it to
automatically sync when I hit the hotsync button.  The device
configuration that works for me is:

Name: Cradle
Port: /dev/ttyUSB1
Speed: 115200
Timeout: 2
Type: Serial

I developed my current theory about what's going on by looking at the
/var/log/messages file for two runs of the hotsync:

Aug 16 13:42:07 jane kernel: hub.c: USB new device connect on bus2/2,
assigned device number 41
Aug 16 13:42:07 jane kernel: usbserial.c: Handspring Visor converter
detected
Aug 16 13:42:07 jane kernel: visor.c: Handspring Visor: Number of ports:
2
Aug 16 13:42:07 jane kernel: visor.c: Handspring Visor: port 1, is for
Generic use and is bound to ttyUSB0
Aug 16 13:42:07 jane kernel: visor.c: Handspring Visor: port 2, is for
HotSync use and is bound to ttyUSB1
Aug 16 13:42:07 jane kernel: usbserial.c: Handspring Visor converter now
attached to ttyUSB0 (or usb/tts/0 for devfs)
Aug 16 13:42:07 jane kernel: usbserial.c: Handspring Visor converter now
attached to ttyUSB1 (or usb/tts/1 for devfs)
Aug 16 13:45:05 jane kernel: usb-uhci.c: interrupt, status 3, frame#
1009
Aug 16 13:45:05 jane kernel: usb.c: USB disconnect on device 41
Aug 16 13:45:05 jane kernel: usb-uhci.c: interrupt, status 2, frame#
1013
Aug 16 13:45:05 jane kernel: usbserial.c: Handspring Visor converter now
disconnected from ttyUSB0
Aug 16 13:45:05 jane kernel: usbserial.c: Handspring Visor converter now
disconnected from ttyUSB1
Aug 16 14:07:48 jane kernel: hub.c: USB new device connect on bus2/2,
assigned device number 42
Aug 16 14:07:48 jane kernel: usbserial.c: Handspring Visor converter
detected
Aug 16 14:07:48 jane kernel: visor.c: Handspring Visor: Number of ports:
2
Aug 16 14:07:48 jane kernel: visor.c: Handspring Visor: port 1, is for
Generic use and is bound to ttyUSB0
Aug 16 14:07:48 jane kernel: visor.c: Handspring Visor: port 2, is for
HotSync use and is bound to ttyUSB1
Aug 16 14:07:48 jane kernel: usbserial.c: Handspring Visor converter now
attached to ttyUSB0 (or usb/tts/0 for devfs)
Aug 16 14:07:48 jane kernel: usbserial.c: Handspring Visor converter now
attached to ttyUSB1 (or usb/tts/1 for devfs)
Aug 16 14:09:51 jane kernel: usb-uhci.c: interrupt, status 3, frame# 66
Aug 16 14:09:51 jane kernel: usb.c: USB disconnect on device 42
Aug 16 14:09:51 jane kernel: usb-uhci.c: interrupt, status 2, frame# 76
Aug 16 14:09:51 jane kernel: usbserial.c: Handspring Visor converter now
disconnected from ttyUSB0
Aug 16 14:09:51 jane kernel: usbserial.c: Handspring Visor converter now
disconnected from ttyUSB1

Specifically, I noticed that the cradle is assigned a new device number
every time it connects.  (Above, first 41, then 42).  My theory is that
the daemon continues to monitor device 41, and only when I do my
control-panel mumbo-jumbo above does it readjust itself to look for
device 42.

I'd appreciate any thoughts you have about 1) Whether you've had a
similar problem, 2) Whether the above analysis looks correct, 3) Where
to start looking for a fix.

Thanks,

	David Saff