Re: [coldsync-hackers] usb syncronisation troubles

[Alessandro Zummo <azummo-coldsync3 at towertech dot it>]

On Tue, 25 Nov 2003 22:24:03 +0300
spied@yandex.ru wrote:

> and i have some troubles ;)
> largest is - coldsync can't get serial number from palmos5 devices.
> but i can see tungsten t serial number in lsusb output. it's any other
> way to get it???
> second - i can't do 2 or more syncs at one time
> 
> i see coldsync and visor.c code and can rewrite it, but what way (use
> libusb or use visor kernel module) is best?

libusb, when i tested it, was faster, don't know which is "best".


> 1. using kernel visor module
>  - today two sync at one time don't work properly
> 
> IMHO it's not very hard to fix it

 Never tried, i thought it would have worked. Can you explain?
  
>  - i don't know how get serial number using only palmos hotsync
>  protocol (may be i stupid?)

 no, you arent ;) PalmOS 5.0 doesn't support reading the serial number
in the old way.

 Basically, the USB layer can get the serial number. We must implement
a way to pass this information to the upper layer in the coldsync
communication stack.

 For example, we could implement an ioctl toward the USB layer implemented
by libusb.

 
> but for this solution need do linux-specific changes in coldsync (and
> others) programs. other trouble - it's big code change and may be not
> included (or included after large time) to standart linux kernel.
> if i want do kernel update i need merge this changes.

 I agree. 


> 2. use libusb
>  - today libusb code in coldsync is old. i try it with tungsten t - it
>  don't work. after quick and dirty hack i can do hostsync, but it work
>  not very stable. it's more work to do here.
>  - theoretically kernel module must be faster (libusb is blocking)
>  - libusb can't work if visor module is loaded (and hotplug try load
>  it every time palmos device is connected). it's problem not for me,
>  but for other users.
>  - visor kernel module always is updated for support lastest devices,
>  work stable.
> 
> 
> may be exist other solution? how about hotplug subsystem - can it
> collect information about device and call coldsync with right options?

 technically it should. I would choice to implement the changes you described
in the libusb code. I've not so much spare time left but will help try to help
you or, at least, do some testing.


> pps: i can't use cvs.coldsync.org:
> cvs [update aborted]: connect to cvs.coldsync.org(62.152.125.84):2401 failed: Connection refused

 We have a little problem with the server. should be up and running tomorrow.


-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Turin, Italy

  http://www.towertech.it
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.