MSCONFIG(8)  BSD System Manager's Manual (i386/i486 Architecture)  MSCONFIG(8)

NAME
     msconfig - configure Maxpeed driver

SYNOPSIS
     msconfig -f port [-D] -d donor [-h freq] [-l lowat] [-x level] [-F bits]
     [-s] [-v] [-L]

DESCRIPTION
     Msconfig is used to set or query the configuration of the Maxpeed driver
     (ms(4)).  To set configuration options, the user must be root.

     -D            Reset the driver to its default state.  A board must be
                   specified and signal sharing will be disabled on that
                   board.  Resetting the driver and the board is the first
                   thing that is done so it may be combined with other op-
                   tions.

     -d donor      Port donating modem control signals.  Must be on the same
                   board as recipient.

     -F bits       Set the driver config flags.  Allows runtime setting of
                   driver options.  All of the flags are set at once.  The
                   flags set in the kernel configuration file may be reset
                   with the -D.

                   The bits argument is put together by or'ing together the
                   following values:

                   0x01    To enable raw input speedups.  Consider turning
                           this off only if you are seeing anomalous behavior
                           with programs that do input in raw mode, or if you
                           are curious about how much difference it makes.

                   0x02    To avoid erroneous setting of DTR when sharing sig-
                           nals with ROM versions prior to D7.

                   0x08    To work around missing status pointers in D5 and D6
                           ROMs.

     -f port       Specify the port (or board) for msconfig to act upon.  If a
                   board is being specified, any port on the board will do as
                   long as you have read permission on it.

     -h freq       Set the polling frequency for the driver.  The argument is
                   the polling frequency in Hertz.  Applies to all boards.

                   Within the driver freq is converted to clock ticks and
                   stored as an integer so the behavior is not always intu-
                   itive (ie; 34 Hz becomes 50).  The actual value set will be
                   reported if the -v flag is present.  UUCP performance is
                   particularly sensitive to the polling frequency.  The best
                   performance will probably be obtained when the polling fre-
                   quency is high enough that UUCP will never be starved for
                   acks.  SLIP probably has similar characteristics but hasn't
                   been subject to much tuning work.

     -L            Use syslog() to log actions and errors.  Implies -v.

     -l lowat      Set the output low water mark.  This is the level (of char-
                   acters) to which the output queue on the board must drain
                   before more characters are transferred to the board.  In
                   general lower is better as it reduces driver overhead, but
                   at high speeds on a loaded system a port may be starved if

                   the low water mark is too low.  Applies to all boards.

     -s            Print the controller's ROM signature.

     -v            Be verbose.  Normally msconfig speaks only if something is
                   wrong.  Verbose output is handy if you are bored or if you
                   wish to log the configuration of the driver.

     -x level      Set level of diagnostic output produced by the driver.  If
                   the driver was compiled with MSDIAG defined then a level
                   greater than 0 will cause messages to be output when unusu-
                   al events occur.  Most of the messages describe ``can't
                   happen'' conditions within the driver - so any output is
                   worthy of investigation.  If I was wrong about what can't
                   happen, a level of 0 will let you get some work done.

EXAMPLES
     To configure signal sharing on an SS-8/2 you might put the following in
     /etc/rc.local :
           msconfig -f ttyh0 -d ttyh4 && (
                stty -f /dev/ttyh0 rtsiflow ctsoflow
                stty -f /dev/ttyh4 clocal
           )

     To enquire about the configuration of the driver:
           msconfig -f /dev/ttyh4
     Any signal sharing on the same board as /dev/ttyh4 would also be report-
     ed.

     You could try:
           msconfig -f /dev/ttyh0 -h 100
     to see if you could get any more performance out of SLIP or UUCP.

     When you are done experimenting
           msconfig -f ttyh0 -D
     will reset the board to its default parameters.  Signal sharing is dis-
     abled by -D so you could do this instead to reset defaults and reconfig-
     ure signal sharing:
           msconfig -f ttyh0 -D -d ttyh4

DIAGNOSTICS
     msconfig tries to do nothing if there is an error with its arguments or
     with accessing the specified devices.  Error messages are intended to be
     self-explanatory.  Zero is returned on success, non-zero on failure.

SEE ALSO
     ms(4)

AUTHOR
     Doug Urner (dlu@tfm.com)

BUGS
     Life will get very interesting if you use msconfig to tell the driver
     that you have ports wired differently than they actually are.

4th Berkeley Distribution       March 27, 1993                               2