[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[coldsync-hackers] Re: Problem respawning coldsync daemon
- To: coldsync-hackers at lusars dot net
- Subject: [coldsync-hackers] Re: Problem respawning coldsync daemon
- From: Alessandro Zummo <azummo-coldsync2 at towertech dot it>
- Date: Thu, 28 Feb 2002 21:46:01 +0100
- In-Reply-To: <20020228202333.GB11828@kroah.com>
- Organization: Tower Technologies
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
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?
> 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?
--
- alex.
--
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.