Jean Tourrilhes wrote:
>
> Andrew Sutton wrote :
> > i'm having some problems with the irda stuff, primarily with irttp and
> > the irsock interface (or so it seems), and some other odd issues
> > besides.
>
> This doesn't look healthy at all. Your server is ar LSAP 0,
> which is the LSAP reserved for the IAS server. No wonder your IAS
> queries fail.
> Now, the big question is why the IrDA stack allow this to
> happen. It look like the IrDA stack was not initialised properly,
> which goes back to "see the list of common problems".
>
i went ahead and installed kernel 2.4.0-test12 and the irdautils-9.13,
rebuilt everythings (all the irda stuff) as a module and started over.
just to start with a (hopefully) clean slate. however, i'm still seeing
the problem with getting a 0 LSAP. at least with my previous program.
i spent some extra time stubbing out a bunch of little proof-of-concept
programs that create irttp servers, that had some really weird behavior.
the really noticable one was the dependence of the LSAP identifier on
the declaration and creation of the address. for example, if the
sockaddr_irda structure was declared as a global variable or created on
the heap, i'd get a 0 LSAP. if the sockaddr_irda structure was declared
locally, within the function calling bind, then i'd get a more
convincing LSAP (2 or 5 or 17, etc...).
this doesn't really make any sense... i can't imagine how the scope of a
variable would affect how a socket is bound. oh... and there's nothing
in the log files about any kind of errors, the stack is successfully
attached, ias entries added, ias queries succeed, etc, etc.
with the exception of my ineptitude at configuring linux systems, can
anybody make any sense of this?
again, thanks,
----------------
Andrew Sutton
[EMAIL PROTECTED]
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
