OK, I got it up and running. And it's fast.
Thanks, Dag and all!
What I did is to change BIOS setting for SIR port
to ttyS2. I7K allows to choose any port/irq
package corresponding to ttyS0-ttyS3, indicating
conflicts with other devices -- very nice. The
only free ones were ttyS2 and ttyS3, (port 3e8 irq
4) v. (port 2e8 irq 3), respectively.
The default is ttyS0, and my previous attempts
were with ttyS3. I felt there's a port conflict,
that's why my bombardment about ports. I saw no
conflicts in /proc/interrupts -- nobody seemed to
be using irq 3. I instinctively chose it ttyS3
with irq 3 as ttyS0 uses irq 4, and I wanted to be
able to connect via cable anyways.
Now I tried the other BIOS setting, making SIR sit
on ttyS2 -- port 3e8, irq 4. I see pcmcia binding
to yet another serial, setting different irq 10.
Still my first connect occured after I stopped
pcmcia. Having irattach /dev/ttyS2, _then_ I can
start pcmcia and it works. But I'm not sure about
its interference now. :-)
My connection via pilot-xfer works only if I
specify -p /dev/ircomm, _not_ /dev/ttyS2.
When I try to HotSync via cable and /dev/ttyS0,
pilot-xfer say "Unable to bind to /dev/ttyS0".
Doing setserial /dev/ttyS0 reports "Device or
resource busy."
I wonder how to have it both ways, cable and
wireless. :-) What does it mean that 4 serial
ports share 2 irqs in pairs -- that you can't use
more that two, namely those on different irqs?
--
Cheers,
Alexy Khrabrov -- www.suffix.com -- Segmentation f%^(&
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
