Re: [coldsync-hackers] New snapshot: 2.2.0

[Koen Deforche <kdf@irule.be>]

Greg KH wrote:
> Is this:
>         01ff 0000 0016
> the bytes that you are talking about?

That's it! Did you get the linux kernel to print these bytes
somehow?
 
> It looks like they get sent from the bulk endpoint like you said.  But
> they get sent _right_ after initialization.  The visor driver doesn't
> submit that endpoint until the port is opened.  Which is a lot later in
> time than the Windows driver.  That might be why there is a difference.

What do you mean with 'submit that endpoint'? Submit this data
to user-space? That never seems to happens. In fact, tracing
usb-serial.c and visor.c, I don't see these 6 bytes at all getting
even there.

What happens with these bytes then? Where do they go?

> > I have no idea of what is going wrong, but some possible scenarios
> > could be:
> >  - when usb-serial gets insmodded, it already starts reading from
> >    the data pipe, but since nobody has open()'ed the serial
> >    tty yet, it is dropped.
> 
> Nope, this does not happen.
> 
> >  - when usb-serial gets insmodded, it is not yet reading from the
> >    data pipe, and therefore the usb stack in the kernel drops
> >    the data.
> 
> No, if the bulk request never gets sent by the driver, the data never
> gets sent.  It stays on the device.

So why is this bulk request sent so early? If the driver would
wait until the serial port gets open()'ed, would it then work
correctly?
 
> >  - the first handshaking is different in timing and little
> >    details from the windows handshaking, and the palm acts
> >    funny.
> 
> I think this is it.

I am not sure. And if so, what can we do about it?

> > An interesting test is whether under FreeBSD this header is
> > there or not. So, for anyone trying coldsync to sync a
> > Palm m50x in a usb cradle on FreeBSD, if protocol simple
> > does not work, try protocol net.
> >
> > Also, since the problem where my palm hangs when transferring
> > large files from the palm to the PC is not solved yet, it
> > may be related to this as well.
> 
> I hope not :)

I actually hope so, since this problem is at least easily
reproducable :)

> Hope this helps a bit.

Ergh, I hope this helps *you* a bit ? :) Do I look like a
kernel hacker to you? [1]

cu,
koen.

[1] Actually, I am a very wanna-be kernel hacker, and I set my-
    self to get the Palm USB cradle to work with linux to earn
    my eternal fame with my own kernel driver, and I even got
    the palm.o module up and running with linux 2.4.5, until I
    noticed that it was already in the latest kernel, by *you* :)
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.