[irda-users] Re: 0x85 parameter pbm with W*nd*ws WP

[Jean T. <jt...@bo...>]

Sylvain Meunier wrote :
> It's still work after. I had to patch msb_value() in qos.c because
> it was returning -1 and then value[index] returning 2048 (from
> data_size[] !)
> and then got a add BOF of 2048!. 

	The patch called "Fixes chat over IrCOMM problem++" has a
workaround for this problem. But I now think there is more than this
workaround.

> 11:40:31.459330 snrm:cmd ca=fe pf=1 98d04e4d < 000007c5 new-ca=a2 
> 	LAP QoS: Baud Rate=4000000bps Max Turn Time=500ms Data Size=2048B
> Window Size=4 Add BOFS=0 Min Turn Time=500us Link Disc=12s (34) 
> 	ff93c50700004d4ed098a20102ff0182010183013f84010f8502800386010808
> 	 . . . . . . M N . . . . . . . . . . . . ? . . . . . . . . . . .

	This is clearly a bug in Windows. If you look at the IrLAP 1.1
specification, chapt 6.6.7, page 41, you will see that the XBOFS
parameter is only one byte. Even VFIR doesn't changes that.
	But, on the other hand, 85028003 is somewhat consistent, and
we shoud be able to parse it properly (which is not the case). So, I
clearly need to go to the root of the problem, which is probably in
irda_extract_integer().

	Thanks for the dump, it helps a lot !

	Jean