Hi,
Let's not run before we can walk ;-)
Can you irobex_palm3 a file first ?
Looks like if you are getting "waiting for sender" message
then your beaming in preferences->General still on. This is
the obex protocol. Search for obex in sourceforge.net and
get the latest libs and utils there. I suggest to switch off
beaming before doing Ir hotsync.
Also, again /dev/ttyS1 is NOT the device to use pilot-xfer
with. It is /dev/irnine (which is a link to ircomm or ircomm0)
I suggest setting PILOTPORT to /dev/irnine and PILOTRATE to
115200 in your environment before trying to do a pilot-xfer.
/dev/ttySX is the underlying layer that IR protocol is layered
on top of. It will not work as the IR device (well actually it
will work if you are doing testing for serial <-> serial ir).
You *must* use the SIR device.
Cheers
Mitch
-------- Original Message --------
Subject: Re: Fwd: [Linux-IrDA]Linux IBM T20 -- Palm, IRDA nearly working.Notquite!]
Date: Mon, 20 Nov 2000 22:02:59 -0500 (EST)
From: [EMAIL PROTECTED]
To: Mitch DSouza <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Slowly making progress.
Removed all explicit module insertions from rc.local
On a cold reboot did:
irdadump (in one window)
irattach /dev/ttyS1
echo 1 >> /proc/sys/net/irda/discovery
That woke my palm up with the waiting for sender message.
Then hitting the sync button gave the response from irdadump.
01:31:48.263035 xid:cmd 7d7e66c8 > ffffffff S=6 s=0 (14)
01:31:55.413024 xid:cmd 7d7e66c8 > ffffffff S=6 s=1 (14)
01:31:57.483023 xid:cmd ffffffff < 9454596c S=6 s=0 (14)
01:31:57.573024 xid:cmd ffffffff < 9454596c S=6 s=1 (14)
01:31:57.663033 xid:cmd ffffffff < 9454596c S=6 s=2 (14)
01:31:57.753041 xid:cmd ffffffff < 9454596c S=6 s=3 (14)
01:31:57.843023 xid:cmd ffffffff < 9454596c S=6 s=4 (14)
01:31:57.933026 xid:cmd ffffffff < 9454596c S=6 s=5 (14)
01:31:58.033025 xid:cmd ffffffff < 9454596c S=6 s=* IrCOMM hint=8204 [
PDA/Palmtop IrCOMM ] (23)
01:32:00.213027 xid:cmd ffffffff < 9454596c S=6 s=0 (14)
01:32:00.303024 xid:cmd ffffffff < 9454596c S=6 s=1 (14)
01:32:00.393025 xid:cmd ffffffff < 9454596c S=6 s=2 (14)
01:32:00.413024 xid:cmd 7d7e66c8 > ffffffff S=6 s=1 (14)
01:32:00.483023 xid:cmd ffffffff < 9454596c S=6 s=3 (14)
01:32:00.573026 xid:cmd ffffffff < 9454596c S=6 s=4 (14)
01:32:00.663023 xid:cmd ffffffff < 9454596c S=6 s=5 (14)
01:32:00.763023 xid:cmd ffffffff < 9454596c S=6 s=* IrCOMM hint=8204 [
PDA/Palmtop IrCOMM ] (23)
01:32:02.803023 xid:cmd ffffffff < 9454596c S=6 s=0 (14)
01:32:02.893024 xid:cmd ffffffff < 9454596c S=6 s=1 (14)
...
Approximately eleven of these cycles. I can reinitiate those cycles at
any time by hitting the sync button. You get a different palm address.
Now cat /proc/net/irda/discovery gives:
nickname: IrCOMM, hint: 0x8204, saddr: 0x7d7e66c8, daddr: 0x785d855a
I assume this is showing the reception of packets by my laptop from the
palm and that the linux IRDA is now aware of my palm when it is trying
to sync. At this point only ttyS1 is available to bind to. But pilot-xfer
still does nothing but hang.
[/root]# pilot-xfer /dev/ttyS1 -l
Waiting for connection on /dev/ttyS1 (press the HotSync button now)...
Note that I have successfully used this pilot-xfer to sync over the serial
port to my hardware cradle before.
After fooling about for a while, ifconfig shows:
irda0 Link encap:IrLAP HWaddr 7d:7e:66:c8
UP RUNNING NOARP MTU:2048 Metric:1
RX packets:1197 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:8
The RX packets increase when I induce the cycles. Nothing I do seems to
make the TX packets get off zero.
What now?
Ian Hutchinson, Plasma Science and Fusion Center, MIT.
http://psfc.mit.edu/~hutch/home.html
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
