On Fri, Mar 16, 2001 at 05:38:51PM +0100, Pontus Fuchs wrote:
> > Look down in the log :
> > ----------------------------------
> > 01:38:33.392600 i:cmd > ca=30 pf=1 nr=3 ns=4 LM slsap=17 dlsap=39 TTP credits=0
> >
> > OBEX CONNECT len=7 ver=1.1 flags=0 mtu=1024 (12)
> > 01:38:33.408341 i:rsp < ca=30 pf=1 nr=5 ns=3 LM slsap=39 dlsap=17 TTP credits=1
> >
> > OBEX SUCCESS len=7 ver=1.1 flags=0 mtu=1024 (12)
> > 01:38:33.416529 i:cmd > ca=30 pf=1 nr=4 ns=5 LM slsap=17 dlsap=39 TTP credits=1
> >
> > OBEX GET final=1 len=3 (8)
> >
> > 01:38:33.436387 i:rsp < ca=30 pf=1 nr=6 ns=4 LM slsap=39 dlsap=17 TTP credits=1
> >
> > OBEX CONTINUE (1029)
> > ^^^^^^^^^^^^^^^^^^^^
> > -----------------------------------
> > As per Obex spec v1.2, chapter 3.2, page 21 and 22, this
> > should be "OBEX CONTINUE final=1 (1029)".
> > You are sending 0x10, while you should be sending 0x90. You
> > should send 0x10 only in response to 0x03 (GET without final bit) and
> > always send 0x90 in answer to a 0x83 (GET + final).
> >
> > That's it...
>
> Yes. You are right. I'll have a look at this soon!
>
> /Pontus
Low priority fixes (don't hurry), all clients we use are
flexible enough to ignore it. I just figured out that it would be
trivial for you to fix.
Have fun...
Jean
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
