On Wed, 17 May 2000, The Armadillo with the Mask wrote:
> HotSync via IRCOMM:
> DON'T run irmanager. It grabs control of the IRDA port and pilot-xfer
> won't be able to get through to the Palm. The more detailed
> explanation is that irmanager is designed to smartly manage the
> IRDA port for things like IRLAN. Pilot-xfer is just checking to
> see if ANYTHING else is using that port. If it can't exclusively
> lock the device, it dies. It won't even try to talk to irmanager.
Actually, the ircomm device works fine for me whether or not irmanager is
started. I have done several IrCOMM syncs with irmanager running. As you
write, however, irmanager is quite unnecessary for connecting to IrCOMM
devices like the Palm or a cel phone.
> COMMON MISTAKES:(I made, so you don't have to :) )
> --Running pilot-sync with PILOTPORT set to the IRDA hardware port instead of
> the pseudo-device /dev/ircommN(as in /dev/ttyS1 instead of /dev/ircomm0).
> See the comments about irmanager for why this is bad.
You CAN do this - but then you DON'T use IrDA. You need some software in
the Palm, such as IrLink, and have that set to sync via "HP-SIR". Then,
WITHOUT any irda modules or irattach, run pilot-xfer directly on the irda
hardware port. Might not work with all irda ports though.
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
