http://bugs.winehq.org/show_bug.cgi?id=19397
--- Comment #64 from Juan Lang juan_lang@yahoo.com 2009-07-29 15:28:57 --- (In reply to comment #63)
Now there seems to be actually some data moving.
Agreed, so the last patch appears to be correct. From irdadump:
8:58:48.831478 i:cmd > ca=2e pf=1 nr=0 ns=0 LM slsap=5b dlsap=00 CONN_CMD (6) 18:58:48.863541 i:rsp < ca=2e pf=1 nr=1 ns=0 LM slsap=00 dlsap=5b CONN_RSP (5) 18:58:48.863603 i:cmd > ca=2e pf=1 nr=1 ns=1 LM slsap=5b dlsap=00 GET_VALUE_BY_CLASS: "HRM" "IrDA:TinyTP:LsapSel" (29) 18:58:48.907545 i:rsp < ca=2e pf=1 nr=2 ns=1 LM slsap=00 dlsap=5b GET_VALUE_BY_CLASS: Success Integer: 43 (15) 18:58:48.907625 i:cmd > ca=2e pf=1 nr=2 ns=2 LM slsap=5b dlsap=00 DISC (6) 18:58:48.938557 rr:rsp < ca=2e pf=1 nr=3 (2) 18:58:48.938606 i:cmd > ca=2e pf=1 nr=2 ns=3 LM slsap=5c dlsap=43 CONN_CMD TTP credits=16 (7) 18:58:48.971811 i:rsp < ca=2e pf=1 nr=4 ns=2 LM slsap=43 dlsap=5c CONN_RSP TTP credits=1 (7)
However the socket complains that it's not connected: trace:winsock:WSASendTo socket 0088, wsabuf 0x1d9ea28, nbufs 1, flags 0, to (nil), tolen 0, ovl (nil), func (nil) trace:winsock:WSASendTo fd=35, options=0 warn:winsock:wsaErrno errno 107, (Transport endpoint is not connected).
Looking at the log above, it appears as though there's a connection made (CONN_CMD), then it's disconnected (DISC), and the subsequent connect request (CONN_CMD) is the last thing done.
I'm frankly a bit out of my league at this point. I've never worked with IrDA before, and I don't have any devices to test with myself. I'll send in my patch set since it appears to help the situation a bit, but I'll have to hope that someone with more knowledge in the area steps in.
Out of curiosity, did this USB dongle come from Polar? Is there a different one you can try?