Palm Device Matrix

As described in README.usb, some handhelds require newer versions of the kernel. Your kernel should be the version indicated in the tables here or a more-recent kernel version than those listed.

If you add data (such as new models, or vendor/product ids) to these tables, please send it to the pilot-link-devel list so it can be added to the plain text listing too.

** USB-to-Serial Adapters **

Prolific Technologies usb-to-serial adapter works with Linux, using the vendor/product ID of 067b/2303, and works with the pl2303 driver in Linux.

Untested on FreeBSD at this point.

Keyspan USA-19QW, works with Mac OS X 10.1.5 and Linux

**Footnotes**

The Palm M130 device does not support Network Hotsync in any capacity. Someone did actually hack it to allow Network HotSync to work. Follow the procedure below if you’re daring.

  1. Extract the files "HotSync.prc" and "HotSync enUS.prc" from your M505 and save them to your HD as "HotSyn2.prc" and "HotSyn2 enUS.prc" (note the space).
  2. Using a hex editor, change all occurrances of the string “sync” to “syn2”, and “Sync” to “Syn2” in both files. (NOTE: earlier revision changed “sync” to “sync2” — this would likely corrupt the file)
  3. Change the byte at offset 0x21 to 0x09 in both files.

** Solution ID: 16309 **

Information on performing a Network HotSync® operation with the Palm™ Bluetooth™ Card in my Palm™ m125 or m130 handheld

The Palm™ m125 and m130 handhelds do not include the necessary components to setup the handheld for Network HotSync® operation, nor the desktop components needed to complete a Network HotSync operation.

**Solution ID: 16713**

Information on Network HotSync® not being available on certain Palm™ m1xx and Zire handhelds

Network HotSync® for specific Palm™ handhelds are not supported, see list below.
The conduits required for the Palm™ Desktop software to perform a Network HotSync® were
not included with the Palm desktop for these products. In addition, the Network HotSync®

settings on the device are not available to enable this feature.

List of handhelds that do not natively support Network HotSync®:

Handspring handheld devices

Handspring Devices

Device Palm OS ver. kernel ver. Port Vendor/Prod Port (Linux/BSD)
Treo 90 4.1H USB 082d/0200
Treo 180 3.5.2H5 2.4.19 USB 082d/0100 USB1
Treo 270 3.5.2 USB 082d/0100 USB1
Treo 300 3.5.2H6.0 USB 082d/0100
Treo 600 5.2.1H USB 082d/0300
Visor 3.1H2 USB 082d/0100 USB1
Visor Edge
Visor Deluxe 3.1H3 USB 082d/0100 USB1
Visor Platinum 3.5.2H1.2 2.4.18-14 USB 082d/0100 USB1
Visor Prism 3.5.2H1 USB 082d/0100 USB1

Miscellaneous handheld devices

Miscellaneous Devices

Device Palm OS ver. kernel ver. Port Vendor/Prod Port (Linux/BSD)
Kyocera QCP 6035 3.5.1 Serial ttyS0..3/cuaa0..3
Kyocera 7135* 4.1.2 2.6.8 (SuSE) USB ttyUSB0
Acer S50 4.1 USB 0502/0736 Unknown
Acer S60 4.1 USB 0502/0736 Unknown
Tapwave Zodiac 1 & 2 5.2.6 (1.0 ROM) & 5.2.7 (1.1 ROM) USB 12EF/0100 ttyUSB0/Unknown
Garmin iQue 3600 5.2.1r3 2.6.6-1.435
Fedora Core 2
2.6.10-1.741_FC3
Fedora Core 3
USB 091e/0004 ttyUSB0 Linux

Palm, Inc. and palmOne handheld devices

Palm/palmOne Devices

Device Palm OS ver. kernel ver. Port Vendor/Prod Port (Linux/BSD)
Palm i705 4.1 2.4.19-pre6 USB 0830/0020
Palm III 3.0 Serial ttyS0..3/cuaa0..3
Palm IIIc 3.5 Serial ttyS0..3/cuaa0..3
Palm IIIx 3.1 Serial ttyS0..3/cuaa0..3
Palm m100 3.5.1 2.4.20 (RH9) Serial ttyS0..3/cuaa0..3
Palm m105 3.5.1 Serial ttyS0..3/cuaa0..3
Palm m125 4.0 2.4.15-pre5 Serial ttyS0..3/cuaa0..3
Palm m130* 4.0 2.4.19-pre5 USB 0830/0050 USB0
Palm m500 4.0 2.4.6-pre1 USB 0830/0001 USB1/ucom0
Palm m505 4.0 2.4.6-pre1 USB 0830/0002 USB1/ucom0
Palm m515 4.1 2.4.19-pre2 USB 0830/0003 USB1/ucom0
PalmPilot 2.0 Serial ttyS0..3/cuaa0..3
Palm Tungsten|C 5.2.1 USB 0830/0060 USB1
Palm Tungsten|E 5.2.1 2.4.22-ac4 USB 0830/0060 USB1
Palm Tungsten|T 5.0 2.4.21-pre1 USB 0830/0060 USB0
Palm Tungsten|T2 5.2.1 2.4.21 USB 0830/0060 USB0
Palm Tungsten|T3 5.2.1 2.4.21 USB 0830/0060 USB1
Palm Tungsten|T5 5.4.5 NA USB 0830/0061 USB1
Treo 650 USB 0830/0061
Palm Tungsten|W 4.1.2 2.4.20 (RH9) USB 0830/0031 USB0
Palm V 3.1 Serial 0830/????
Palm Vx 3.3/3.5 Serial 0830/????
Palm Zire 4.x 2.4.20-pre9 USB 0830/0070 USB1/ucom0
Palm Zire 21 ?? ?? USB 0830/0061 ??
Palm Zire 31 5.2.8 2.4.21 USB 0830/0061 USB1
Palm Zire 71 5.2.1 2.4.21 USB 0830/0060 USB1
Palm Zire 72 5.2.8 I used 2.6.9 and is Ok USB 0830/0061 USB1

LifeDrive with a Linux desktop

The LifeDrive:
Currently the LifeDrive is Palm's attempt to be relevant in the emerging portable media player market(PMP). It wokrs pretty well as a PDA and does a good job as a PMP. I recently purchased one and thought this would be a good place to comment on it's useabilty with Linux.

The Sync:

All hail the networksync feature of pilot-link. Without I would never have gotten the LifeDrive to sync. It ships with a usb cradle and this is the source of the problems. On most modern Linux distros you have dbus/hotplug enabled and the LifeDrive rports it self as a USB device as soon as you plug it in to teh cradle. This is good for drive mode, bad for hotsyncing. When you press teh hotsync butto the Lifedrive it resets the USB connection causing the /devpilot(/dev/tts/USB1 or /dev/ttyUSB1) to reset and breaking the connection. I have not found a awy around this yet. Luckly the Lifedrive comes with both Bluetooth and wifi. The device can sync over the wifi connection.


To setup Lifedrive for the network sync follow teh instruciton given in the Network Hotsync Document on the right side of the page. Be sure you have pilot-link installed, to test the connection use 'pilot-xfer -p net:any -l'. You should see pilot-xfer listening on port net:any message. Press teh hotsync button and watchit go, you should see a list of items from the Lifedrive.



The Desktop-

I use J-pilot for my desktop software. The LifeDrive supports all the features of the J-pilot. However, J-pilot does NOT support all of the LifeDrive features. Many of these features can be duplicated by using Drive Mode.



Drive Mode-

When the LifeDrive is set to Drive Mode it reports it self as 3.5 gig usb drive and allows you to move files back and forth with Nautilus and I would assume Konquer with out problem. Just be sure to turn off drive Mode be for unpluging the LifeDrive

Sony handheld devices

Sony Organizers

Device Palm OS ver. kernel ver. Port Vendor/Prod Port (Linux/BSD)
Sony Clie 320 2.4.10-pre2 USB 054c/???? USB0/ucom0
Sony Clie 3.5 2.4.10-pre5 USB 054c/0038 ??
Sony Clie 4.0 2.4.10-pre5 USB 054c/0060 ??
Sony Clie 4.1 2.4.19-pre7 USB 054c/009a ??
Sony Clie N610C USB 054c/0066 USB1/ucom0
Sony Clie N760C USB 054c/0066 ??
Sony Clie N770C/E 4.1 USB 054c/0066 USB0
Sony Clie NR70V/U 2.4.26 054c/00da ??
Sony Clie NX60 2.4.21-pre1 USB 054c/00da
Sony Clie NX70U/V 5.0 2.4.20 USB 054c/00da
Sony Clie NX73V 5.0 2.4.20 USB 054c/00da
Sony Clie PEG-S320 4.0 USB 054c/0066 USB1
Sony Clie S360 2.4.19-pre2 USB 054c/0095
Sony Clie SJ30 4.1 USB 054c/0066
Sony Clie T615C USB 054c/0066 USB1/ucom0
Sony Clie T665C 4.12S USB 054c/009a USB0/ucom0
Sony Clie TJ25* 5.2.1 2.6.5 works USB 054c/0169 USB0
Sony Clie TJ35 USB 054c/0169
Sony Clie TJ37 5.2.1 2.6.4 USB 054c/0169 ttyUSB0 Linux
Sony Clie SJ22 4.0 2.4.20 USB ttyUSB0 Linux
Sony Clie TH55 5.2.1 2.4.25 USB 054c/0144 ttyUSB0 Linux

* To make the newer CliƩ devices work with gnome-pilot, they must be added to a hardcoded list of devices in gpilotd.c (USB ids in vendor_product_ids and an additional product_net = TRUE)

pilot-xfer -l failing on FC4

First of all, great work on this project! I really appreciate all the work you guys have done!

Unfortunately, once I upgraded to FC4, I lost all capability to sync with my Zire 72 over USB. This used to work perfectly fine in FC3.

I'll start from the beginning to make sure I'm not missing something completely obvious. I removed all /etc/udev/rules.d and /etc/udev/permissions.d changes. Starting from scratch, I'm trying to get a simple pilot-xfer -l working and am having difficulty.

When I turn on my Palm and press HotSync, I get the following in /var/log/messages:

Jul 18 00:11:46 localhost kernel: usb 1-4.4: new full speed USB device using ehci_hcd and address 15
Jul 18 00:11:46 localhost kernel: visor 1-4.4:1.0: Handspring Visor / Palm OS converter detected
Jul 18 00:11:46 localhost kernel: usb 1-4.4: Handspring Visor / Palm OS converter now attached to ttyUSB0
Jul 18 00:11:46 localhost kernel: usb 1-4.4: Handspring Visor / Palm OS converter now attached to ttyUSB1

So far so good. And the devices /dev/ttyUSB0 and /dev/ttyUSB1 appear after about 6 seconds:

[root@markroth-pc mroth]# ls -l /dev/ttyUSB*
crw-rw---- 1 root uucp 188, 0 Jul 18 00:11 /dev/ttyUSB0
crw-rw---- 1 root uucp 188, 1 Jul 18 00:11 /dev/ttyUSB1

When I do pilot-xfer -p /dev/ttyUSB1 -l, I get:

Listening for incoming connection on /dev/ttyUSB1...

It pauses there and never returns. (I'm using pilot-link-0.12.0-0.pre4.2 on FC4).

Using strace, I've managed to see that some data is being exchanged, but I don't know enough about the protocol to know whether this is good data or not:

write(1, " Listening for incoming connec"..., 56 Listening for incoming connection on /dev/ttyUSB1... ) = 56
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
ioctl(3, SNDCTL_TMR_STOP or TCSETSW, {B9600 -opost -isig -icanon -echo ...}) = 0select(4, [3], NULL, NULL, NULL) = 1 (in [3])
select(4, [3], NULL, NULL, NULL) = 1 (in [3])
read(3, "\1", 1) = 1
select(4, [3], NULL, NULL, NULL) = 1 (in [3])
read(3, "\377\0\0\0\26", 6) = 5
select(4, [3], NULL, NULL, NULL

It just pauses here until the Pilot gives up.

Can anyone help suggest where I can proceed from here? I'd really like to get this working.

Thanks much!
- Mark