"Rafael R. Sevilla" wrote:
>
> On Wed, 7 Mar 2001, Wolfgang Grandegger wrote:
> >
> > Does this help? I will send you a test version later
> > this week.
> >
>
> I'll see what happens...
>
> > Does the pilot-link program handle the write() return
> > code correctly. A write to the serial device may
> > return 0 and the program must deal with that e.g. it
> > must redo the write():
> >
>
> I have no idea. So far the pilot-xfer program has done nothing but read
> data from the Palm on hotsync. If it still doesn't work after it's able
> to detect the hotsync key, I'll do a little more careful study of the core
> serial code and perhaps contribute a patch to pilot-link.
I checked the linux-usb-devel mailing list and indeed also
pilot-xfer seems not to be properly written. You can look for
example here:
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=97889646414658&w=2
What you can do in this case is to enable a work-a-round in the
MCT U232 driver.
#define FIX_WRITE_RETURN_CODE_PROBLEM
#ifdef FIX_WRITE_RETURN_CODE_PROBLEM
static int write_blocking = 1; /* disabled by default */
#endif
Do not forget to set write_blocking to 1.
Hope this helps,
Ciao Wolfgang.
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
