From owner-freebsd-bugs Mon Mar 16 12:40:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16923 for freebsd-bugs-outgoing; Mon, 16 Mar 1998 12:40:07 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: (from gnats@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16871; Mon, 16 Mar 1998 12:40:03 -0800 (PST) (envelope-from gnats) Received: from zephyr.specialix.com (zephyr.specialix.com [192.65.145.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14293 for ; Mon, 16 Mar 1998 12:30:49 -0800 (PST) (envelope-from nick@zephyr.specialix.com) Received: (from nick@localhost) by zephyr.specialix.com (8.8.5/8.8.5) id MAA08594; Mon, 16 Mar 1998 12:30:44 -0800 (PST) Message-Id: <199803162030.MAA08594@zephyr.specialix.com> Date: Mon, 16 Mar 1998 12:30:44 -0800 (PST) From: nsayer@quack.kfu.com Reply-To: nsayer@quack.kfu.com To: FreeBSD-gnats-submit@FreeBSD.ORG X-Send-Pr-Version: 3.2 Subject: docs/6036: New handbook section 10.4.3.4 - si driver config Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 6036 >Category: docs >Synopsis: New handbook section 10.4.3.4 - si driver config >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Mar 16 12:40:01 PST 1998 >Last-Modified: >Originator: Nick Sayer >Organization: Specialix, Inc. >Release: FreeBSD 2.2.2-RELEASE i386 >Environment: >Description: If Cyclades gets one... :-) >How-To-Repeat: >Fix: 10.4.3.4 Configuring the si driver The Specialix SI/XIO and SX multiport cards use the si driver. A single machine can have up to 4 host cards. The following host cards are supported: 1. ISA SI/XIO host card (2 versions) 2. EISA SI/XIO host card 3. PCI SI/XIO host card 4. ISA SX host card 5. PCI SX host card Although the SX and SI/XIO host cards look markedly different, their functionality are basically the same. The host cards do not use I/O locations, but instead require a 32K chunk of memory. The factory configuration for ISA cards places this at 0xd0000-0xd7fff. They also require an IRQ. PCI cards will, of course, autoconfigure themselves. You can attach up to 4 external modules to each host card. The external modules contain either 4 or 8 serial ports. They come in the following varieties: 1. SI 4 or 8 port modules. Up to 57600 bps on each port supported. 2. XIO 8 port modules. Up to 115200 bps on each port supported. One type of XIO module has 7 serial and 1 parallel port. 3. SXDC 8 port modules. Up to 921600 bps on each port supported. Like XIO, a module is available with one parallel port as well. To configure an ISA host card, use the following configuration, changing the numbers as appropriate: device si0 at isa? tty iomem 0xd0000 irq 11 vector siintr Valid IRQ numbers are 9, 10, 11, 12 and 15 for SX ISA host cards and 11, 12 and 15 for SI/XIO ISA host cards. To configure a PCI host card, use this line: device si0 Rebuild and install your new kernel. After rebooting with the new kernel, you need to make the devices in /dev. The MAKEDEV script will take care of this for you. Count how many total ports you have and type ./MAKEDEV ttyAnn cuaAnn (where nn is the number of ports). If you want login prompts to appear on these ports, you will need to add lines like this to /etc/ttys: ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure Change the terminal type as approprate. For modems, 'dialup' or 'unknown' is fine. Note that by default DCD must be asserted for the login prompt to appear. For modems this is correct, but for terminals, this may prevent login prompts from showing up without special steps. There are a few ways to tackle this: 1. PR # 5959 adds a flag 'nc' to the gettytab which will make the gettys _not_ wait for carrier before starting. If you apply the patch in that PR, then you can add ':nc:' to your gettytab entries. 2. You can modify /etc/rc.serial to do a stty clocal on /dev/ttyiAnn and /dev/ttylAnn. This locks 'clocal' on the tty devices, which is basically the same sort of thing as the first option. 3. You can wire DTR from your terminals to DCD of the ports. This has the added benefit of automatically logging people out when they turn off the terminals (presuming that the terminal properly asserts DTR when it's on). >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message