On Tue, 2005-11-08 at 09:32 +1100, Yuandan Zhang wrote:
> Hi
>
> I followed Craig's suggestion and created /tmp/pilot.
>
> Previously, I have these in files:
>
> 1. add following lines to /etc/udev/rules.d/20-pilot.rules
>
> BUS=="usb",SYSfs{product}=="Palm Handheld",
> KERNEL=="ttyUSB*",Name{ignore_remove}=="pilot", MODE=="188"
>
> this may be overwritten by /tmp/pilot.
>
> 2. in file, /usr/share/gnome-pilot/devices.xml add following line
>
> <!-- Palm Tungsten T5 -->
> <device vendor_id="0830" product_id="0061" />
>
> after the palm was plugged in and switched on. the visor module was
> automatically loaded.
>
> I tested. timing is critic.
>
> after press hotsync 1-2 seconds,
> issue command:
> pilot-xfer -p /tmp/pilot -l
>
> Connection is ok. I used /tmp/pilot as device and get gpilotd tested ok
> too, except there was problem to sync calendar.
>
----
timing was critical when using 'udev rules' and that's why I was working
around them by using the node created in /tmp/pilot and specifically not
creating rules in /etc/udev/rules.d/10_or_20-pilot.rules
I think the bugzilla report was pretty clear about that.
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
