Jean Tourrilhes <[EMAIL PROTECTED]> writes:
> IrDA utils :
> ----------
> It's always a painful experience to compile it on Debian,
> because of some blatant Red-Hat assumptions. Today was better, I
I don't use Debian myself, so somebody running Debian will have to fix such
problems. Both Mandrake and Redhat have now made RPM's out of irda-utils
themselves, so I expect Debian to to the same without my help ;-)
> managed to compile both irattach and irmanager, so I won't complain...
> Compile ok on Mandrake.
> Try to compile 0.9.4 to get Obex. Obex doesn't want to compile.
That's the reason it removed ;-)
> irdaping :
> --------
> Doesn't work.
> irdadump show that messages are going back and forth (rsp is
> comming back). dmesg show something like "wrong magic in skb".
Strange, tested this today, and had no problems. Are you saying you got a
test response back and irdaping didn't show any output? A small snap of
your irdadump output would be appreciated. Wrong magic in skb is btw. a
harmless message.
> irlan :
> -----
> Doesn't work.
> The light on the NetBeamer keep flashing. When I insmod by
> hand irlan, irlan is created but not configured. ifconfig up doesn't
> change anything.
> I won't say anything, because Dag said explicitely that it
> doesn't work.
Tested IrLAN, and had no problems. I have only said that IrLAN doesn't
work with the latest 2.3.x kernels. This is because 2.3.x does not support
dynamically creation of net devices from interrupt context. Well, 2.2
doesn't support it either but it works anyway.
> ircomm :
> ------
> Doesn't work.
> I inserted ircomm and ircomm-tty by hand and then irattach.
> When I try to "echo toto > /dev/ircomm0" the command hang
> forever. Messages are that "param_request is not ready yet",
> "ircomm_tty.c(346): block_til_ready after blocking on ircomm
> open_count=1" and "ircomm_tty_open(), returning after
> block_til_readywith -512".
> Kermit hang when I do "set line /dev/ircomm0"
> getty /dev/ircomm0 return immediately without doing what it's
> supposed to do.
I couldn't make getty work myself, but "mgetty -r /dev/ircomm0" is working
like a dream. Really cool, have never tried this before. Also tried this
using Minicom in both ends, and I had no problems. May I ask what you were
using at the other end? You description makes sense if you don't have
anything to connect to.
> IrObex :
> ------
> Can't compile it, waiting for whatever Dag has promised.
Both Mandrake 6.1 and Redhat 6.1 has RPM's with precompiled OBEX for those
who needs it. There will however be a release of both C-OBEX and PyOBEX in
a few days. Then you should have plenty of things to try out. The release
got delayed since I got an influenza and then Kjetil (the other PyOBEX
developer) went to Oslo for a week :-(
> So, I welcome any tip that would allow me to run any part of
> the IrDA stack between my Linux boxes... What configuration is
> supposed to work by the way ?
You should probably try using Linux-2.2.13-irda5 (uploading right now) with
irda-utils-0.9.5. If you have problems with it, they I suspect you have
some problems with the device drivers that others don't have. Can't think
of anything specific reasons why you have so many problems :-(
-- 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/ ///
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
