[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [coldsync-hackers] New snapshot: 2.2.0



Greg KH wrote:
> I don't see them either.
> For USB, the host has to ask the device if it has any data.  Then the
> device can respond.  The device can't respond on its own.  So on Windows
> it looks like they do a bulk read _right_ after doing the other
> connection negoation.  That is when that data gets sent.
> 
> > What happens with these bytes then? Where do they go?
> 
> It doesn't look like they get sent by the device.  So I'm guessing the
> palm drops them internally.
> 
> > 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?
> 
> Why does the Windows driver do this?  I have no idea.
> 
> The Linux driver currently sends that request when the port gets
> open()'ed.  The data never gets sent from the device at that time.  I am
> guessing that it doesn't have the data anymore, and has moved on to
> other things.  Only a guess though.

What about postponing communication on the control pipe until
the tty is open()'ed? I guess that this could have a chance of
working if the palm delays sending out data until these negotations
are run.

I guess that before we do any of this, we should find out if
by any luck the BSD port has less strange behaviour (including
the mysterious hang events during bulk transfers).
 
> And is this data really necessary?  What does this 6 bytes mean?
> Ah, to only have a spec...

It is a header of what is called in cold-sync the "net" protocol.
I think this spec is quite open: from the back of my head:
byte 1 is unimportant(?), byte 2 is a sequence number,
and bytes 3-6 define the payload length.

So, no this data is not really necessary, since we do not
understand the payload anyway. But it would be more robust
if we did not need to make any assumptions on the length
of the payload.

Also, I still am not convinced that this weird behaviour is
not related to the other more painfull problem.

> Does your version of the driver work better than the visor one?

No, it was in fact just a copy with some reworking. I had exactly
the same behaviour as I see now.

koen.
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.