Re: [coldsync-hackers] Re: Problem respawning coldsync daemon

[Greg KH <greg at kroah dot com>]

On Thu, Feb 28, 2002 at 09:46:01PM +0100, Alessandro Zummo wrote:
>  On 28-Feb-02 at 21:23:34,
>   Greg KH <greg@kroah.com> wrote:
> 
> 
> >> Actually, this is what happens:
> 
> >> 1 - HotSync
> >> 2 - ColdSync closes the serial port
> >> 3 - little delay
> >> 4 - The Palm removes itself from the USB bus
> >> 5 - The module driver ( visor.o ) removes the device entry.
> 
> >> The problem happens if we launch hotsync between 3 and 5, when
> >> the device entry has not yet been removed.
> 
> >> Maybe we could keep the device open until visor.o removes it?
> >> There's a way to detect such a condition?
> 
> > You can just keep the port open until it dissapears (in step 4).  And
> 
> How will I notice it from within coldync?

Hm, don't know.  Maybe if you try to read a byte and get an error that
the device is not there anymore?

> > you can catch the hotplug event that states that the device has now been
> > removed from the USB bus.
> 
> mm.. that could be interesting... any point to the relevant
> documentation?

See http://linux-hotplug.sf.net/ for lots of docs on this.

Let me know if you have any specific questions.

thanks,

greg k-h

-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.