Re: gpilotd sync problems - workaround?

[Szabó Balázs "(dLux)" <dlux dlux hu>]

I don't have it fully working either, but I did a dirty trick in my gpilotd source:

In the visor_devices_in function, I added a while cycle, which waits until the Treo really exists in the /proc/bus/usb/devices. It sleeps until it can found it. Of course it can be run only from a terminal.

It seems that /proc/bus/usb/devices is not refreshed at the time when you push the HotSync button, only after 4-5 seconds (I use kernel 2.5.70), and this causes the problem. If I use the following coreography, it works:

- kill any accidentally-running gpilotd
- start the hacked ./gpilotd from a terminal
- push sync button
- kill the gpilotd (Ctrl+C)

This gpilotd process can be used only for one synchronization, it won't wake up again if you push the button again.

Sometimes I got "Unable to bind to pilot" message at the first try, but It always work for second time.

Did it help?

On Fri, 2003-07-11 at 10:44, Nigel Metheringham wrote:
> Would anyone who has a fully working current gnome-pilot setup working
> care to get an strace of gnome-pilot starting with it sitting waiting
> for a hotsync and then picking up a hotsync (don't need it to carry on
> through the sync itself) on a USB connected palm.
>
> I can then compare that to whats happening on my box and see if I can
> pin down where it goes screwy.
>
> Thanks
> 	Nigel.

Szabó Balázs (dLux)

dlux dlux hu