.\" Copyright (c) 1996-1998 Greg Ungerer (gerg@stallion.oz.au). .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Greg Ungerer. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD: src/usr.sbin/stallion/bootcode/stl.4,v 1.8.2.5 2001/12/14 16:41:52 ru Exp $ .\" .Dd August 6, 2009 .Dt STL 4 i386 .Os .Sh NAME .Nm stl , .Nm stli .Nd "drivers for Stallion Technologies multiport serial controllers" .Sh SYNOPSIS .Cd "device stl" .Cd "device stl0 at isa? port irq " .Cd "device stli0 at isa? port iomem iosiz flags " .Sh DESCRIPTION This is a kernel driver for Stallion Technologies multiport serial boards. There are two drivers, each supporting a different class of boards. The .Nm driver supports the EasyIO, EasyConnection 8/32 and EasyConnection 8/64-PCI boards, while the .Nm stli driver supports all other types, including ONboard, Brumby and EasyConnection 8/64 (ISA). .Sh CONFIGURATION Each non-PCI board installed in the system needs a configuration entry in the kernel configuration file. Slightly different options and parameters are required for each of the different board types. Depending on the type of board one of the .Nm or .Nm stli drivers will be used. The .Nm and .Nm stli drivers can support up to 8 boards. .Pp Configuration of the hardware - DIP switches, jumpers, etc - varies from board to board. Consult documentation supplied with the board for hardware configuration details. Alternatively the board documentation is available on Stallion Technologies WWW site at .Pa http://www.stallion.com . .Pp The EasyIO, EasyConnection 8/32 and EasyConnection 8/64-PCI families of boards use the .Nm driver. ISA board configuration entries for the .Nm driver take the general form of: .Pp .Cd "device stlX at isa? port irq " .Pp .Ar X is the unit number assigned to the board. Any unique value between 0 and 7 is valid. .Pp The I/O address used by the board is specified by .Ar . Each of the EasyIO and EasyConnection 8/32-AT boards can use an I/O address in the range from 0 to 0x400. .Pp All EasyIO and EasyConnection 8/32 boards require an interrupt, and this interrupt is specified by .Ar . Legal IRQ values for the ISA boards are 3, 4, 5, 7, 10, 11, 12 and 15. Interrupts are software programmed on all boards except the EasyIO-8M. .Pp The EasyConnection 8/32-AT board uses a secondary I/O address region, and this is fixed at address 0x280 in the driver code. All EasyConnection 8/32-AT boards may share the same secondary address region. .Pp All EasyIO and EasyConnection PCI boards are detected automatically by the drivers on boot up. No configuration information is required in advance for these board types. During boot up the .Nm driver will issue messages to indicate that a Stallion PCI board was found, and some information about it. If no ISA card is being configured, an entry like .Pp .Cd "device stl" .Pp will include the driver for PCI cards only. .Pp Following are some examples of configuration entries for each of the ISA boards supported by the .Nm driver. Each example also describes some important details about each of the board types. .Pp Each EasyIO board requires 8 bytes of I/O address space and 1 IRQ line. A configuration entry for an EasyIO board would look like: .Pp .Cd "device stl0 at isa? port 0x2a8 irq 15" .Pp This entry specifies an EasyIO board at I/O address 0x2a8 using IRQ 15. The I/O and IRQ values can be modified as required. .Pp Each EasyConnection 8/32-AT board requires 2 sets of I/O addresses and 1 IRQ line. The primary I/O address range is 2 bytes in size, and must be unique to each EasyConnection 8/32-AT board in the system. The secondary I/O address range is 32 bytes in size, but can be shared by multiple EasyConnection 8/32-AT boards. This secondary I/O address is set at 0x280 in the driver code. A configuration entry would look like: .Pp .Cd "device stl0 at isa? port 0x2a0 irq 10" .Pp This specifies an EasyConnection 8/32-AT with primary I/O address 0x2a0, secondary I/O address of 0x280 and IRQ 10. .Pp The ONboard, Brumby and EasyConnection 8/64 families of boards use the .Nm stli driver. The .Nm stli driver supports the ISA members of these families. .Pp ISA board configuration entries for the .Nm stli driver take the general form of: .Pp .Cd "device stliX at isa? port iomem iosiz flags " .Pp .Ar X is the unit number assigned to the board. Any unique value between 0 and 7 is valid. .Pp The I/O address used by the board is specified by .Ar . Each of the different supported board types has restrictions on valid I/O addresses and also the amount of I/O space required varies between the boards. .Pp All boards using the .Nm stli driver require a shared memory region to operate. Depending on the board type the region required varies in size from 4 kbytes to 64 kbytes. The size of the board region is specified by field .Ar of the configuration entry, and the address of the region is specified by .Ar . .Pp The flags field specifies the particular board type that this entry applies to. Not all board types are distinguishable by the driver at runtime, so this field is required by the driver. Valid board types are: .Bd -literal -offset indent BOARD NAME TYPE I/O SIZE Brumby 2 0x4000 ONboard 4 0x10000 ONboard/E 7 0x10000 EasyConnection 8/64-AT 23 0x1000 .Ed .Pp Following are some examples of configuration entries for each of the boards supported by the .Nm stli driver. Each example also describes some important details about each of the board types. .Pp The EasyConnection 8/64-AT board requires 4 bytes of I/O address space and 4 kbytes of memory space. A configuration entry would look like: .Pp .Cd "device stli0 at isa? port 0x2a0 iomem 0xcc000 iosiz 0x1000 flags 23" .Pp The flags field of this entry specifies that this is an EasyConnection 8/64-AT board. It is set to I/O address 0x2a0 and memory address 0xcc000. The .Ar iosiz parameter specifies a memory region size of 4 kbytes. .Pp Each ONboard ISA board requires 16 bytes of I/O space and a 64 kbyte section of memory address space. Valid ONboard I/O addresses are in the range 0x200 to 0x300. A configuration entry for an ONboard ISA would look like: .Pp .Cd "device stli0 at isa? port 0x240 iomem 0xd0000 iosiz 0x10000 flags 4" .Pp This entry specifies an ONboard ISA by setting flags to 4. It uses I/O address 0x240 and a memory region of 64 kbytes at memory address 0xd0000. .Pp Each Brumby board requires 16 bytes of I/O address space and a 4 kbyte region of shared memory space. The valid Brumby I/O addresses are in the range 0x300 to 0x400. The shared memory region of the Brumby must be in the 0xc0000 to 0xdc000 region of the memory address space. A configuration entry for a Brumby would be like: .Pp .Cd "device stli0 at isa? port 0x360 iomem 0xc8000 iosiz 0x4000 flags 2" .Pp This specifies a Brumby board at I/O address 0x360 using a shared memory region at address 0xc8000. .Sh NOTES Each driver has a separate major number allocated, so even though the port device names are the same for each driver, the major number of the device node is different. .Pp The intelligent board types (ONboard, Brumby and EasyConnection 8/64 (ISA)) require a firmware download before the ports will be operational. This is achieved by using the .Nm stlload command. See its manual page for details on usage. .Sh FILES .Bl -tag -width "/dev/staliomem?" -compact .It Pa /dev/ttyE? stl standard callin devices .It Pa /dev/ttyiE? stl initial-state callin devices .It Pa /dev/ttylE? stl lock-state callin devices .It Pa /dev/cuaE? stl standard callout devices .It Pa /dev/cuaiE? stl initial-state callout devices .It Pa /dev/cualE? stl lock-state callout devices .It Pa /dev/ttyF? stli standard callin devices .It Pa /dev/ttyiF? stli initial-state callin devices .It Pa /dev/ttylF? stli lock-state callin devices .It Pa /dev/cuaF? stli standard callout devices .It Pa /dev/cuaiF? stli initial-state callout devices .It Pa /dev/cualF? stli lock-state callout devices .It Pa /dev/staliomem? board control device .El .Pp Note that the port numbers start at 0 for port 0 of board 0. Each board has 64 port slots allocated for it. So the second boards ports start at 64 and go through 127. .Sh SEE ALSO .Xr stty 1 , .Xr termios 4 , .Xr tty 4 , .Xr comcontrol 8 , .Xr stlload 8 , .Xr stlstats 8 , .Xr stlstty 8 .Sh HISTORY This driver was originally developed by Greg Ungerer (gerg@stallion.com). .Sh BUGS The /dev/staliomem? device name is shared between both the .Nm and .Nm stli drivers. This may cause confusion if both drivers are present in the system at the same time. .Pp Device names use integer suffixes, rather than the 0-9 a-z sequence that other drivers use. .Pp There will be many unused ttyE device names in a system with more than one card.