[irda-users] Re: 3 fairly quick questions

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

Kyle L. Pinches wrote :
> 
> 1. What do the timestamps in irdadump's output represent? Is it the time
> start of the frame was received? The time when the end of the frame was
> received? The time when the output was printed? Something else entirely?

	Time the frame pass through the driver interface. So end
received for incomming frame, and before start sending for outgoing
(because mtt is done in driver).
	This is actually the same as tcpdump.

> 2. Is there a way to set the maximum number of BOFs? There is nothing in
> /proc/sys/net/irda as far as I can see.

	Each IrDA driver set the number of incomming xbofs it needs,
because it depends on the hardware (so please hack the relevant
driver). And the outgoing xbofs is whatever the peer ask us to do, and
we better conform to that.
	Note the Linux-IrDA doesn't need any XBOFS in itself, and I
think some driver set it to zero. Actually, XBOFS is no longer used at
FIR speed, and only used at SIR.

> 3. In older versions of irattach it was possible to set the hint bits
> using '-h 8010' for example, but this seems to not work in more recent
> versions (I'm using kernel 2.5.24 with patches). Is there a way to set
> the hint bits in newer versions? I didn't see anything for this in
> /proc/sys/net/irda either.

	Each application can set the hints bits it wants advertised
through a setsockopts. This is cleaner because when the app goes away,
the hint bits are automatically cleared. Check OpenObex source on how
to do that ;-)
	Probably you would need a call to set the "device hints" (such
as computer/PDA) as opposed to the application hints
(OBEX/HTTP/IrCOMM/LAN). If you do a patch for that (making sure that
only the "device hints" can be set), I'll add that in my patch queue.

	Have fun...

	Jean