Treo 600 discovered as tty and not usb device

[Chuck Williams <chuck manawiz com>]

I have a Treo 600 configured with gnome-pilot, but only in a gross way. 
I have usbserial and visor modules in my kernel (2.6.12.3).  When the
Treo's device node is created after pushing the hotsync button, udevinfo
reports it's P as /class/tty/ttyUSB1.  No udev rules that constrain the
BUS to usb match.  udevinfo -a on the sysfs path for the tty shows none
of the useful attributes (like product, idVendor or idProduct).  The
device also exists in sysfs on the usb where it belongs and lsusb shows
it, as does hal-device-manager.  The usb sysfs node has all of the
useful attributes, udevinfo and hal-device-manager show them, but this
is not the sysfs device node being matched in udev.rules.  So, I can
only recognize the device by attributes on the class tty sysfs node, and
the only attribute on that node  is it's automatically generated
usbserial device number, which is of course subject to change if I
attach another usb serial device to the computer.

More specifically, the uncommented udev rules below work but all of the
commented ones fail to match (including the first one which gnome-pilot
generated):

#BUS="usb", KERNEL="ttyUSB*", SYSFS{product}="Palm Handheld*",
SYMLINK="pilot"
#SYSFS{idProduct}="0300", SYSFS{idVendor}="082d", SYMLINK="pilot"
#KERNEL="ttyUSB*", SYSFS{product}="Palm Handheld*", SYMLINK="pilot"
### The following is a crock, but the device has no other SYSFS
properties, probably because it's class tty and not usb!
KERNEL="ttyUSB*", SYSFS{dev}="188:1", SYMLINK="pilot"
KERNEL="ttyUSB*",    NAME="usb/%k"

The problem is that on the class tty sysfs node, which is what is
evidently passed to udev, the BUS is not usb, and the idProduct,
idVendor and product SYSFS attributes are missing.  The correct sysfs
node does exist but is not processed by udev.

What is the fix for this?  E.g., should I disable the usbserial or visor
kernel modules?

Any help appreciated,

Chuck