Carlos Sierra <csierra () gio ! etsit ! upm ! es>
I don't know if this is an interesting post but I didn't find any related post before anywhere. It is possible to sync the Palm over bluetooth to kpilot without the need of
connection in Local (not modem) mode. it is possible too, using udev, to sync both over bluetooth or cradle without the need of touching configuration. To manage this we set a serial bluetooth link that behaves exactly the same way as the USB or serial nodes. All we have to do is:
· register a serial port to the sdpd daemon: sdptool add --channel=#chan SP · make rfcomm listen by: rfcomm listen hci0 #chan (or any other device we would like)
the problem is that rfcomm will quit after each connection so we better daemonize it, for example at /etc/inittab:
supposing we chose channel number 8.
We will nedd also a node /dev/rfcomm0 to read/write:
mknod /dev/rfcomm0 c 216 0
Now we can tell kpilot to sync over /dev/rfcomm0 and that's it! It works really well!
If we have udev installed at our system we can add these rules to udev.rules:
KERNEL="rfcomm[0-9]*", SYMLINK="pilot" KERNEL="ttyUSB0", SYMLINK="pilot"
if we tell kpilot to sync over /dev/pilot now we can sync with both bt or cradle that the system will detect the media we are using and will create /dev/pilot symbolic link appropiately.
DON'T FORGET TO GRANT PROPER ACCESS RIGHTS TO THE NODES because the user application will have to read & write to it. if we are using udev we MUST modify the rigths at udev.permissions.
I don't know if there was information about this before. As I did not find any i thougth it may be of interest.
I will send this info formatted as a guide to pilot-link bluetooth hotsync howto and I hope they will find it interesting and include it.
I hope this will help.
Regards.