Hi,
As some of you know, we have a problem with the setting of the slot-timeout
in the stack. The reason for this is that IrLAP sais (page 92):
"Slot-Timer-Timeout. The discovery and address conflict resolution
timer timeout must never exceed 85ms and always be at least 25ms."
So I have always thought that using 80 ms would be a good thing. But this
means that we have a problems discovering a lot of "late" devices which
uses more than 80 ms before their discovery response is fully received. 90
ms is actually quite common.
I've made it possible to change the slot-timeout on the fly, but it's
really not good enough, so I have decided to change the slot timeout to 100
ms instead. That should make all the problems go away. I have measured the
Palm III to 150 ms, and Win95 to 120 ms, so it should be OK that we use a
higher value. You will still be able to change the value on the fly if you
need to.
I must say that I'm really confused about this issue, so it might just be
that I have misunderstood the spec. If somebody knows what all this is
about then please explain it to me!
But anyway, the problems should soon disappear, even if I don't know what
is going on ;-)
-- Dag
--
/ Dag Brattli | The Linux-IrDA Project /
// University of Tromsoe, Norway | Infrared communication for Linux //
/// http://www.cs.uit.no/~dagb | http://www.cs.uit.no/linux-irda/ ///
