[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re[2]: [coldsync-hackers] usb syncronisation troubles
>> >> AZ> What if you launch several instances of coldsync, each one with a different
>> >> AZ> ttyUSBx device?
>> >>
>> >> ok
>> >> via libusb call each found several palm devices. each palm have own
>> >> serial number. how coldsync know what serial use?
>>
>> AZ> ? each instance will take care of the first unassigned palm... am I
>> AZ> missing something? i'm a bit tired today ;)
it's one of possible solutions, but imho any way in userspace is ugly
and/or not very stable.
examples:
- palm device not listed in kernel visor module (old kernel), but
coldsync know about this model and get serial number from it to other
palm
- hotsync on several palms pressed with very small time difference -
coldsync can swap serial numbers across devices
it's one way without global changes get information from kernel to
userspace - read kernel log. but it's VERY ugly
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.