Hi, I spent some time on Sunday getting my Compaq Armada M700 to talk to my SH888, eventually managing to get online for a while. Here's a rough summary of my experiences: 1. First things first: the machine boots up/loads the serial stuff with both ports set to IRQ 4. From my Windows setup I noticed that ttyS2, the IrDA port, should be IRQ 3. I'd like to know how Windows gets this right and Linux gets this wrong! setserial fixed this, obviously. 2. I used plain SIR. It's an smc-ircc chip, but it's not recognised, and I'm not smart enough to fix it :) If anyone wants to give me an analysis tool to probe the chip and determine the magic values... 3. I could not make the cable work, except for a brief moment that I'm sure I imagined. The pc would discover the phone just fine, but as soon as I kicked up an ircomm connection over it, it switched the bit rate to 115200 and the phone vanished from the discovery log. On the one occasion when it seemed to work, the phone reappeared after a few minutes, but I couldn't reproduce this. 4. Running via the IrDA port was very tricky. I had to reset the phone a few times; I had to rip out all the modules and reload them a few times. It seems as if the stack doesn't reset itself properly, particularly if anything goes wrong. On one occasion, I had to strip right back to removing the serial module and reloading /that/ before it'd work. 5. The surprise I wasn't expecting! A day after all this, I ran up PilotManager, intending to sync my Palm III. As soon as I started PilotManager listening on the serial port (ttyS0, the hardline), the whole machine locked up solid! Cold boot time... Hope this is of use to anyone developing IrDA. Cheers, Waider. -- Ronan Waide, Technology Consultant StepStone, #102 Block 4, Harcourt Centre, Harcourt Rd, Dublin 2, Ireland Tel: +353 (0)1 2944077 Fax: +353 (0)1 2944078 http://www.stepstone.ie/ _______________________________________________ Linux-IrDA mailing list - [EMAIL PROTECTED] http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
