I've contacted Kodak and got the specs on the Kodak DC 265/290 host interface. It says under IrDA that the camera implements TinyTP and IRCOMM. This makes me believe that once you get an appropriate IrCOMM channel to the camera you can the same communication protocol as the NSS (normal serial port) and USB. The spec does NOT mention bFTP, or InTran-P which are mentioned at the www.irda.org site as part of the picture transport protocol for cameras. The spec says basically for NSS-only you do the beacon-phase and then for all modes you proceed with the rest of the spec. The spec says the camera will talk SIR or FIR. I've setup my laptop as follows: Linux 2.2.15pre11 irda-utils 0.9.9 modules: (modprobe and the kernel are installing them automatically) irtty 7300 2 (autoclean) serial 18676 1 (autoclean) ircomm-tty 30408 0 (autoclean) ircomm 13628 0 (autoclean) [ircomm-tty] irda 135201 2 (autoclean) [irtty ircomm-tty ircomm] I run irattach /dev/ttyS1 irmanager -d1 /var/log/messages shows: top kernel: IrDA (tm) Protocols for Linux-2.2 (Dag Brattli) top kernel: IrCOMM protocol (Dag Brattli) top PAM_pwdb[1064]: (su) session opened for user root by (uid=101) top irattach: device=/dev/ttyS1 top irattach: SIR device top kernel: Serial driver version 4.27 with no serial options enabled top kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A top kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A top kernel: IrDA: Registered device irda0 top irattach: SIR device (2) top irattach: Starting device irda0 top irattach: executing: 'echo top > /proc/sys/net/irda/devname' top irmanager: executing: 'echo 1 > /proc/sys/net/irda/discovery' top irmanager: executing: 'echo top > /proc/sys/net/irda/devname' top irmanager: + 1.1 Tue Nov 9 15:30:55 1999 Dag Brattli top irmanager: + 1.1 Tue Nov 9 15:30:55 1999 Dag Brattli with irdadump running while I turn on the camera I get: 19:54:39.005345 xid:cmd 3e7a1b8f > ffffffff S=6 s=0 (14) 19:54:39.095318 xid:cmd 3e7a1b8f > ffffffff S=6 s=1 (14) 19:54:39.185313 xid:cmd 3e7a1b8f > ffffffff S=6 s=2 (14) 19:54:39.275309 xid:cmd 3e7a1b8f > ffffffff S=6 s=3 (14) 19:54:39.365310 xid:cmd 3e7a1b8f > ffffffff S=6 s=4 (14) 19:54:39.455314 xid:cmd 3e7a1b8f > ffffffff S=6 s=5 (14) 19:54:39.455380 xid:rsp 3e7a1b8f < b0348914 S=6 s=4 Kodak DC265 Zoom hint=8404 [ Computer IrCOMM ] (33) 19:54:39.545311 xid:cmd 3e7a1b8f > ffffffff S=6 s=* top hint=0400 [ Computer ] ( When I run irtest.c, or my own home grown version, both programs hang forever at the open of /dev/ircomm0. the irdadump shows: 19:55:28.223720 snrm:cmd ca=fe pf=1 3e7a1b8f > b0348914 new-ca=c0 (32) 19:55:28.345304 ua:rsp ca=c0 pf=1 3e7a1b8f < b0348914 (31) 19:55:28.345402 rr:cmd > ca=c0 pf=1 nr=0 (2) 19:55:28.595320 rr:cmd > ca=c0 pf=1 nr=0 (2) 19:55:28.615320 rr:rsp < ca=c0 pf=1 nr=0 (2) 19:55:28.615364 i:cmd > ca=c0 pf=1 nr=0 ns=0 LM slsap=1a dlsap=00 CONN_CMD (6) 19:55:28.635315 i:rsp < ca=c0 pf=1 nr=1 ns=0 LM slsap=00 dlsap=1a CONN_RSP (6) 19:55:28.635395 i:cmd > ca=c0 pf=1 nr=1 ns=1 LM slsap=19 dlsap=00 CONN_CMD (6) 19:55:28.655315 rr:rsp < ca=c0 pf=1 nr=2 (2) 19:55:28.655351 i:cmd > ca=c0 pf=1 nr=1 ns=2 LM slsap=1a dlsap=00 GET_VALUE_BY_CLASS: "IrDA:IrCOMM" "Parameters" (28) rd:rsp < ca=0xc0 pf=1 (2) 19:55:28.675363 disc:cmd > ca=0xc0 pf=1 (2) 19:55:28.685311 ua:rsp ca=c0 pf=1 41447249 < 0b841a00 (2) and then 19:55:30.005344 xid:cmd 3e7a1b8f > ffffffff S=6 s=0 (14) 19:55:30.095319 xid:cmd 3e7a1b8f > ffffffff S=6 s=1 (14) 19:55:30.185311 xid:cmd 3e7a1b8f > ffffffff S=6 s=2 (14) 19:55:30.275317 xid:cmd 3e7a1b8f > ffffffff S=6 s=3 (14) 19:55:30.365315 xid:cmd 3e7a1b8f > ffffffff S=6 s=4 (14) 19:55:30.455310 xid:cmd 3e7a1b8f > ffffffff S=6 s=5 (14) 19:55:30.545313 xid:cmd 3e7a1b8f > ffffffff S=6 s=* top hint=8404 [ Computer IrCOMM ] (20) is repeated forever. The camera does not reappear on the list until I power cycle it. Any ideas why its hanging in the open of /dev/ircomm0? I'm not perfectly clear or ircomm vs irtty vs irxxx. I'm wasn't expecting the kernel to load irtty. If I haven't fouled something simple up in the configuration of all this stuff, I'm planning to look at the IrDA specs to examine the handshaking that is occuring. -- Brian Litzinger <[EMAIL PROTECTED]> _______________________________________________ Linux-IrDA mailing list - [EMAIL PROTECTED] http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
