Bj�rn Mork <[EMAIL PROTECTED]> writes:
> > Then I went and did a "echo 1 >
> > /proc/net/irda/discovery" and a "tail -f /proc/net/irda/discovery" to
> > get the log of what the port finds. This left me with "IrLMP:
> > Discovery log:" and no more if I held my Palm Vx or Ericsson t39 in
> > front of the IR port. (Yes, 10-15 cm, no flourescent lighting, semi
> > dark room, lit candles in a hexagon with a dead chicken in the middle
> > and full moon, etc). Nothing more in the discovery log.
>
> That's how it works for me too. tail -f will not work with files in
> the /proc file system. Try cating the file in another window while
> leaving the tail -f running, and you'll see..
>
Tried, both with my Palm and my phone. No luck :) To quote one of the
famous chaps from Monty Python: dead as a herring. And ifconfig shows
this after having tried to poke the IR connection with various things
that should generate traffic:
lapper:~# ifconfig irda0
irda0 Link encap:IrLAP HWaddr 50:3e:7e:5d
UP RUNNING NOARP MTU:2048 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:8
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:3 Base address:0x3e8
mvh,
A
--
Alexander Hoogerhuis | [EMAIL PROTECTED]
CCNP - CCDP - MCNE - CCSE | +47 905 76 198
"You have zero privacy anyway. Get over it." --Scott McNealy
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda