1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255
|
.\" This -*- nroff -*- file has been generated from
.\" DocBook SGML with docbook-to-man on Debian GNU/Linux.
...\"
...\" transcript compatibility for postscript use.
...\"
...\" synopsis: .P! <file.ps>
...\"
.de P!
\\&.
.fl \" force out current output buffer
\\!%PB
\\!/showpage{}def
...\" the following is from Ken Flowers -- it prevents dictionary overflows
\\!/tempdict 200 dict def tempdict begin
.fl \" prolog
.sy cat \\$1\" bring in postscript file
...\" the following line matches the tempdict above
\\!end % tempdict %
\\!PE
\\!.
.sp \\$2u \" move below the image
..
.de pF
.ie \\*(f1 .ds f1 \\n(.f
.el .ie \\*(f2 .ds f2 \\n(.f
.el .ie \\*(f3 .ds f3 \\n(.f
.el .ie \\*(f4 .ds f4 \\n(.f
.el .tm ? font overflow
.ft \\$1
..
.de fP
.ie !\\*(f4 \{\
. ft \\*(f4
. ds f4\"
' br \}
.el .ie !\\*(f3 \{\
. ft \\*(f3
. ds f3\"
' br \}
.el .ie !\\*(f2 \{\
. ft \\*(f2
. ds f2\"
' br \}
.el .ie !\\*(f1 \{\
. ft \\*(f1
. ds f1\"
' br \}
.el .tm ? font underflow
..
.ds f1\"
.ds f2\"
.ds f3\"
.ds f4\"
'\" t
.ta 8n 16n 24n 32n 40n 48n 56n 64n 72n
.TH "irattach" "8"
.SH "NAME"
irattach \(em binds the Linux/IrDA stack to a device driver
.SH "SYNOPSIS"
.PP
\fBirattach\fP [<dev>] [\fI-s\fP] [\fI-d dongle\fP] [\fI-v\fP]
.SH "OPTIONS"
.PP
\fBdev\fP usually the name of a (serial) tty, but can also be a FIR device
.PP
The currently known FIR drivers are:
.IP " \(bu" 6
\fBali-ircc\fP ALi FIR Controller Driver for ALi M5123
(options: io, irq, dma)
This driver supports SIR, MIR and FIR (4Mbps) speeds.
This chipset is used by e.g.:
.IP "" 10
The ALi M5123 FIR Controller
is embedded in ALi M1543C, M1535, M1535D, M1535+, M1535D Sourth Bridge.
.IP " \(bu" 6
\fBnsc-ircc\fP NSC IrDA device driver
(options: io, irq, dma, dongle_id, qos_mtt_bits)
This chipset is used by e.g.:
.IP "" 10
IBM ThinkPad dongle_id=0x08
HP OmniBook 6000 dongle_id=0x08
.IP " \(bu" 6
\fBsmc-ircc\fP SMC IrCC controller driver
(options: ircc_dma, ircc_irq)
This chipset is used by e.g.:
.IP "" 10
Fujitsu-Siemens Lifebook 635t
Sony PCG-505TX
.IP " \(bu" 6
\fBw83977af_ir\fP Winbond W83977AF IrDA device driver
(options: io, irq, qos_mtt_bits)
This chipset is used by e.g.:
.IP "" 10
Corel NetWinder
.IP " \(bu" 6
\fBtoshoboe\fP Toshiba OBOE IrDA device driver, supports Toshiba Type-O IR chipset.
(options: max_baud)
This chipset is used by e.g.:
.IP "" 10
Toshiba Libretto 100CT, and many more laptops.
.IP " \(bu" 6
\fBdonauboe\fP is a new version of \fBtoshoboe\fP and has better FIR support
and compability with the Donauoboe chip http://libxg.free.fr/lib-irda.html
(options: ..)
This chipset is used by e.g.:
.IP "" 10
...
.IP " \(bu" 6
\fBvlsi_ir\fP VLSI 82C147 SIR/MIR/FIR device driver
(options: ..)
This chipset is used by e.g.:
.IP "" 10
HP Omnibook 800
.PP
You may use \fBfindchip\fP to get information about the FIR chip.
If this doesn't help, the \fBInfrared-HOWTO\fP shows other means to
retrieve these data.
.PP
\fB-s\fP starts discovery of remote IrDA devices (may also work with argument \fB-s 1\fP, but I don't know what it does)
.PP
\fB-v\fP shows version information (this happens, when no option
is given, too)
.PP
\fB-d dongle\fP attaches a dongle driver (see below for more info)
.PP
You need these modules if you have an infrared device that connects to your
computer's serial port (normal 9-pin serial port connector). These devices are called dongles.
, and can currently only be used by IrTTY.
Some more information is contained in the comments at the
top of the kernel files, e.g. \fB../linux/drivers/net/irda/old_belkin.c\fP.
.PP
The currently known (serial) dongles are:
.IP " \(bu" 6
tekram Tekram IrMate IR-210B dongle
.IP " \(bu" 6
esi Extended Systems JetEye PC ESI-9680
.IP " \(bu" 6
actisys ACTiSYS IR-220L dongle
.IP " \(bu" 6
actisys+ ACTiSYS IR-220L+ dongle
.IP " \(bu" 6
girbil Greenwich GIrBIL dongle
.IP " \(bu" 6
litelink Parallax LiteLink dongle
.IP " \(bu" 6
airport N.N.
.IP " \(bu" 6
old_belkin Belkin (old) SmartBeam dongle
.PP
The currently known USB dongles are:
.IP " \(bu" 6
\fBirda-usb\fP Product, idVendor, idProduct, idCapability
ACTiSYS Corp, ACT-IR2000U FIR-USB Adapter { 0x9c4, 0x011, IUC_SPEED_BUG | IUC_NO_WINDOW },
KC Technology Inc., KC-180 USB IrDA Device { 0x50f, 0x180, IUC_SPEED_BUG | IUC_NO_WINDOW },
Extended Systems, Inc., XTNDAccess IrDA USB (ESI-9685) { 0x8e9, 0x100, IUC_SPEED_BUG | IUC_NO_WINDOW },
.IP "" 10
As far as I know the Actisys 2000U and
Extended System ESI-9685
dongles seem to be based on the same hardware.
Note: you need a kernel >= 2.4.5 with CONFIG_EXPERIMENTAL
enabled.
.SH "DESCRIPTION"
.PP
\fBirattach\fP binds the Linux/IrDA stack to a device driver.
So this is something you must do in order to use IrDA on your Linux machine.
.PP
\fBirattach\fP uses the \fBirtty\fP module which connects to the Linux TTY and
serial driver. This works well for most machines, but limits the speed
to 115200bps (IrDA SIR mode). If you want higher speeds, you must use
a special FIR device driver for the IrDA chipset used by your machine.
Currently there are not that many device drivers implemented, mostly
because it's very hard to get the documentation, and the drivers are
in fact quite hard to implement even if you are lucky and get the
documentation for the chipset.
.PP
If you are one of the lucky people which have a FIR chipset that is
supported, then you don't need \fBirattach\fP anymore. Now you just have to \fBmodprobe\fP the driver.
.PP
If you have compiled the IrDA stack as modules (recommended), then you will
need to edit the \fB/etc/modules.conf\fP file.
See the \fBInfrared-HOWTO\fP for details.
.PP
\fBirattach\fP must be run as root or installed setuid root,
as it requires root privileges.
.SH "EXAMPLES"
.PP
Attach the IrDA stack to the second serial port and start discovery
\fBirattach /dev/ttyS1 -s\fP
.PP
Attach the IrDA stack to the first serial port where you have an ACTiSYS
dongle and start discovery
\fBirattach /dev/ttyS0 -d actisys -s\fP
.PP
Attach the IrDA stack to the NSC FIR (4Mbps) device driver on a Thinkpad
laptop \fBirattach irda0 -s 1\fP.
Note: You must also add some entries to
\fB/etc/conf.modules\fP:
.PP
.nf
.ta 8n 16n 24n 32n 40n 48n 56n 64n 72n
\f(CWoptions nsc-ircc dongle_id=0x09
alias irda0 nsc-ircc\fR
.fi
.PP
.SH "DIAGNOSTICS"
.PP
"ioctl(TIOCGETD): %m"
.PP
"irattach: tty: set_disc(%d): %s"
.PP
"tcsetattr: %m"
.PP
"Failed to open %s: %m"
.PP
"Couldn't get device fd flags: %m"
.PP
"Couldn't set device to non-blocking mode: %m"
.SH "BUGS"
.PP
N.N.
.SH "SEE ALSO"
.PP
irattach(8), irdaping(8), irdadump(8), findchip(8),
irkbd(8), irpsion5(8), modprobe(8)
.PP
\fBLinux/IrDA Project\fP http://irda.sourceforge.net -*-
\fBLinux/IrDA-Tutorial\fP http://www.hpl.hp.com/personal/Jean_Tourrilhes/IrDA/index.html -*-
\fBInfrared-HOWTO\fP http://mobilix.org/howtos.html -*-
\fBInfrared-Hardware-Survey\fP http://mobilix.org/ir_misc.html
.SH "AUTHOR"
.PP
This manual page is written by Werner Heuser
wehe@mobilix.org. It is based on the READMEs
from \fBirda-utils\fP by the \fBLinux/IrDA Project\fP and the \fBLinux/IrDA-Tutorial\fP.
.SH "COPYRIGHT"
.PP
Copyright (c) 2001 Werner Heuser
.PP
Permission is granted to copy, distribute
and/or modify this document under
the terms of the GNU Free Documentation
License (GFDL), Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no Front-Cover
Texts and no Back-Cover Texts.
...\" created by instant / docbook-to-man, Sun 19 Aug 2001, 20:58
|