Thomas Heide Clausen wrote:
> Drop using irmanager. Use the following:
>
> irattach /dev/ttyS1 -s 1
>
> That is: you need to attach the IR to a TTY (namely the one, where the IR-port
> presents itself. On my laptop, the IR-port is com2, hence the above works for me.
> The -s 1 means "discovery on". Discovering the semantics of -s 0 are left as an
> exercise to you :)
>
> > # cu -l /dev/ttyS2
>
> HERE you use /dev/ircomm0 instead. Then it will all be dandy :)
>
> In short: Your IR-port lives as a "serial port" (sort of - has an UART and stuff
> and presents itself as such). Using irattach, you tie that port to the IrDA-code,
> and by accessing /dev/ircomm0, you will be able to communicate through the
> IrDA-stack to the ttyS and into the "air" :)
>
> Sent in private since 1) I am not an "official" IrDA-person and 2) the above is
> slightly inaccurate however useful for "the craftsman" who wants to get things
> working.
>
> Have fun - the SH888 works fine with my ThinkPad :)
Hi Thomas,
Thanks very much for the speedy and knowledgeable response -- now I know at least
what I am trying to do. Still, there is something else going on.
I got irda-utils 0.9.5 instead of 0.9.4 (which has not got the -s 1 option to
irattach), and typed after reboot:
# irattach /dev/ttyS2 -s 1
1.1 Tue Nov 9 15:30:55 1999 Dag Brattli
The sys log shows:
Dec 13 22:49:12 rennell irattach: Serial connection established.
Dec 13 22:49:12 rennell kernel: IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Dec 13 22:49:12 rennell kernel: IrDA: Registered device irda0
Dec 13 22:49:12 rennell kernel: irmanager is not running!
Dec 13 22:49:13 rennell irattach: executing: 'echo 1 > /proc/sys/net/irda/discov
ery'
Dec 13 22:49:13 rennell irattach: executing: 'echo rennell > /proc/sys/net/irda/
devname'
Dec 13 22:49:13 rennell irattach: Unable to get name of device!
Dec 13 22:49:13 rennell irattach: Using device:
Dec 13 22:49:13 rennell modprobe: can't locate module
# more /etc/conf.modules
alias parport_lowlevel parport_pc
alias tty-ldisc-11 irtty
alias char-major-161 ircomm_tty
pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start
keep
path[pcmcia]=/lib/modules/default
path[pcmcia]=/lib/modules/preferred
# more /proc/net/irda/discovery
IrLMP: Discovery log:
name: SH 888, hint: 0x9104, saddr: 0xe0380cee, daddr: 0x75138e09
[root@rennell /root]# lsmod
Module Size Used by
irtty 4636 2 (autoclean)
irda 135713 1 (autoclean) [irtty]
nm256 64456 0 (unused)
sound 57228 0 [nm256]
soundcore 2372 6 [sound]
vmnet 11200 3
vmppuser 5216 0 (unused)
parport_pc 5620 0 [vmppuser]
parport 7124 0 [vmppuser parport_pc]
vmmon 15072 0 (unused)
nfsd 150496 8 (autoclean)
3c575_cb 18792 2
cb_enabler 2104 2 [3c575_cb]
ds 5740 2 [cb_enabler]
i82365 22640 2
pcmcia_core 39912 0 [cb_enabler ds i82365]
Ifconfig has:
irda0 Link encap:UNSPEC HWaddr EE-0C-38-E0-00-00-00-D9-00-00-00-00-00-00-00
-00
UP RUNNING NOARP MTU:2048 Metric:1
RX packets:183 errors:0 dropped:0 overruns:0 frame:0
TX packets:1281 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:8
What screws me is apparently this system call in irattach.c:
/* Start the network interface */
if (ioctl(fd, IRTTY_IOCGNAME, &info) < 0) {
syslog(LOG_ERR, "Unable to get name of device!\n");
}
Any more ideas are welcome to me. Would it be worth it to patch my kernel to a
higher level than patch 2.2.13-irda3? In which way to attack kernel debugging?
Kind regards and thanks for the help.
--
Kris Heyrman.
Ottergemsesteenweg 337, B-9000 Gent. Phone: +32.9.221.79.69
"L'an 0. On arr�te tout, puis on r�flechit. Et c'est pas triste."
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
