On Wed, 26 Jan 2000, Alexy V. Khrabrov wrote:
> What device do you use -- /dev/ttyS? or
> /dev/irnine or /dev/ircomm?
You hotsync to the IrCOMM device. With recent IrDA, that's a character
device with major number 161, minor number 0. On my laptop, that's
/dev/ircommnew0.
> Namely, IR-HOWTO states a case by Harald Milz/SuSE
> connecting Palm III to a Thinkpad. He manually
> creates mknod /dev/irnine. This step is never
> explained in other docs anywhere. Many docs
> mention /dev/ircomm. or /dev/ircomm0. Where do
> these come from?
I believe irnine was used for ircomm before it was assigned a number
range, or something. ircomm or ircomm0 are the 2nd generation; the
ircommnew devices are used by all recent irda drivers.
> What does have
> irattach /dev/ttyS?
> to do with this new /dev/irnine beast?
irattach is used to tell the IrDA drivers where your IR port is. The
"irnine beast" is not new, it's obsolete. Much of the documentation is out
of date.
> Now, dmesg mentions a UART on tty03. How is
> *that* related to /dev/ttyS0 .. /dev/ttyS3?
It's ttyS3. The S name is used to differentiate the dev nodes from the
consoles, which aren't reported by the kernel.
> Milz still does irattach /dev/ttyS0, saying that
> this will disable a regular serial port, and makes
> a link /dev/pilot --> /dev/irnine. Why both, and
> why can't one use /dev/ttyS3 say?
As far as I know, irattach has nothing to do with your /dev/pilot link.
You should use irattach /dev/ttyS3 if that's where your IR port is (most
people have it at 1, 2 or 3).
> My only desire is to use pilot-xfer to HotSync
> over IR, which uses /dev/pilot by default. So if
> it points at /dev/irnine, why irattach /dev/ttyS0?
Because irnine points to the IrCOMM drivers; the ttyS port could be used
directly if you use a program like IrLink on the Pilot to make it sync
over HP-SIR instead of IrCOMM. In that case, you don't need the irda
drivers and tools at all.
> I'd really appreciate a little insight into this
> tty bonanza. I installed the latest 2.2.14 +
> pre-patch-2.2.15-4 and still my HotSync does nil.
With this setup, get the latest irda-utils too; the irda in 2.2.15-pre3
and later are the newest ones available.
> I also tried to download the latest Obex, but its
> ./autogen.sh fails with the latest libtool-1.3.4!
I built it using libtool-1.3.4. The autogen.sh problems were present, but
it's not libtool that causes them... in my case, I just had to install
glib1.2-dev (that is, development files for glib).
Good luck, and don't hesitate to ask if this caused further confusion!
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
