>The irdadump program cannot handle fragmented IrOBEX frames. Most them are
>fragmented! You'll need to adjust the max_sdu_size of OBEX to a lower value
>to be able to debug it with irdadump. So the transmission might actually be
>correct.
I tried to decrease the max sdu size (I found only one parameter that seemed
to be used, the IRTTP_MAX_SDU_SIZE), but that pretty much broke the rest of
the protocol (i.e., once the change was made, it always failed to even make
a OBEX connection). Now I don't understand this stuff, but I figured I
would give it a try anyway to see if irdadump did punt out some better info.
Probably the connection is succeeding even with the unknown opcodes,
but the problem is that, regardless of irdadump, the operation never
finishes, and the document I am trying to put on the pilot never is
received.
thanks for the feedback,
Steve
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda