On 2/15/07, irda-users-request@... > On Sun, Feb 04,
2007 at 11:01:35PM +0200, Gabor Szelei wrote:
> > > , what are the commands/steps you're following ?
> > I suspect opening the ircomm channel. I see from irdadump log that
> > linux close channel of param negotiation and my gadget responded too
> > late.
> It seems that yes, we keep on waiting for a never coming frame.
> It's also interesting to note that your device has a big turnaround time (the
> biggest available...). Could you try to run at a lower speed, so that we don't
> send so many BOFs ? Can you try at 9600bps ?
I have tried. Same case, about the same output.
> > 16:20:43.600124 i:cmd > ca=60 pf=1 nr=1 ns=1 LM slsap=1c dlsap=00
> > GET_VALUE_BY_CLASS: "IrDA:IrCOMM" "Parameters" (28)
> > 16:20:43.620102 i:rsp < ca=60 pf=1 nr=2 ns=1 LM slsap=00 dlsap=1c
> > GET_VALUE_BY_CLASS: Success
> > IrCOMM Parameters Service Type=NINE_WIRE Port Type=SERIAL (19)
> > 16:20:43.624183 i:cmd > ca=60 pf=1 nr=2 ns=2 LM slsap=1c dlsap=00 DISC (6)
> We send the disconnection right after getting the IAS answer. So, with IrDA
> debug set to 5, could you please run the same test again until it fails, and
> then send the complete dmesg output, no matter how big it is ?
You can find it @ http://spidernest.ath.cx/irda/dmesg.txt.gz