Small argument going on over on the Pilot-Unix list about Hot-Syncing and
IRCOMM. It has been my experience that on some systems, you have to kill
or not run irmanager in order to get normally serial-based apps like
minicom, seyon, etc. to work properly with /dev/ircommN.
When irmanager is running, I get a "device unavailable" or "Failed to
lock device" message when trying to use /dev/ircommN with these
programs. When stopped, things like minicom, pilot-xfer, etc. all work
fine.
My personal experience with this has been on Toshiba Librettos, esp. Model
70.
So the question I have is:
Where do IRCOMM packets get decapsulated into regular serial line
discipline data? Is this happening because you can't lock the /dev/ircommN
pseudo-device or because the lock request is getting as far as /dev/ttySN,
finding irmanager on the port and failing?
Thanks,
----Steve
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
