d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2c75b47793
freebsd-dev/usr.sbin/digictl/digictl.8

119 lines
2.7 KiB
Groff
Raw Normal View History

Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.\" $FreeBSD$
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
.Dd June 20, 2001
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.Dt DIGICTL 8
.Os
.Sh NAME
.Nm digictl
mdoc(7) police: fix markup and spelling.
2001-05-16 10:29:51 +00:00
.Nd control
.Tn Digiboard
devices
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.Sh SYNOPSIS
.Nm
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
.Fl a
mdoc(7) police: fixed markup in rev. 1.3.
2001-07-05 07:04:33 +00:00
.Cm disable | enable | query
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
.Ar device ...
.Nm
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.Op Fl d Ar debug
.Op Fl ir
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
.Ar ctrl-device ...
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.Sh DESCRIPTION
The
.Nm
The .Nm utility
2002-07-14 14:47:15 +00:00
utility provides control of the
mdoc(7) police: fix markup and spelling.
2001-05-16 10:29:51 +00:00
.Tn Digiboard
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
installed with the given
.Ar ctrl-device
name and provides control of individual digiboard
mdoc(7) police: fixed markup in rev. 1.3.
2001-07-05 07:04:33 +00:00
.Ar devices .
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
A digiboard
.Ar ctrl-device
is usually of the form
mdoc(7) police: fixed markup in rev. 1.3.
2001-07-05 07:04:33 +00:00
.Sm off
.Pa /dev/digi Ar N Pa .ctl
.Sm on
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
where
mdoc(7) police: fixed markup in rev. 1.3.
2001-07-05 07:04:33 +00:00
.Ar N
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
is the card number and starts at
.Dq 0
for the first attached card.
A digiboard
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.Ar device
is usually of the form
mdoc(7) police: fixed markup in rev. 1.3.
2001-07-05 07:04:33 +00:00
.Sm off
.Pa /dev/cua Oo Pa il Oc Pa D Ar N Pa \&. Ar P
.Sm on
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
or
mdoc(7) police: fixed markup in rev. 1.3.
2001-07-05 07:04:33 +00:00
.Sm off
.Pa /dev/tty Oo Pa il Oc Pa D Ar N Pa \&. Ar P
.Sm on
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
where
mdoc(7) police: fixed markup in rev. 1.3.
2001-07-05 07:04:33 +00:00
.Ar N
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
is the card number and
mdoc(7) police: fixed markup in rev. 1.3.
2001-07-05 07:04:33 +00:00
.Ar P
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
is the port number.
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.Pp
mdoc(7) police: fix markup and spelling.
2001-05-16 10:29:51 +00:00
The following flags are recognized:
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
.Bl -tag
mdoc(7) police: fixed markup in rev. 1.3.
2001-07-05 07:04:33 +00:00
.It Fl a Cm disable | enable | query
o Add a -a flag for changing/getting the ALTPIN setting for a digi port. o For the -i switch, only show the device if more than one is given on the command line.
2001-06-20 14:52:20 +00:00
Disable, enable or query the
.Em ALTPIN
settings for the given port(s).
.Pp
When ALTPIN is enabled, the CD and DSR lines are logically reversed.
This is useful when wiring serial ports to an 8 way RJ45 cable (full
10 way RJ45 cables are quite rare).
.Pp
A single ALTPIN setting applies to both of the callout and callin devices.
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.It Fl d Ar debug
If the driver has been compiled with
.Dv DEBUG
defined, the following bits from the
.Ar debug
variable are used to enable diagnostics in the digiboard driver:
mdoc(7) police: -xwidth has been fold into -width.
2001-07-13 09:09:52 +00:00
.Bl -tag -width ".No 1024 ( Em MODEM )"
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.It 1 ( Em INIT )
mdoc(7) police: fix markup and spelling.
2001-05-16 10:29:51 +00:00
Diagnostics during card attach, detach and initialization.
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.It 2 ( Em OPEN )
Diagnostics when opening a port.
.It 4 ( Em CLOSE )
Diagnostics when closing a port.
.It 8 ( Em SET )
Diagnostics when setting tty device flags.
.It 16 ( Em INT )
Diagnostics when processing card events.
.It 32 ( Em READ )
Reports return values from port reads.
.It 64 ( Em WRITE )
Reports return values from port writes.
.It 128 ( Em RX )
Reports receive queue flow control.
.It 256 ( Em TX )
Reports transmit queue flow control.
.It 512 ( Em IRQ )
Diagnostics during interrupts (enable these with care).
.It 1024 ( Em MODEM )
Diagnostics when setting modem status flags.
.It 2048 ( Em RI )
Reports when a RING is received.
.El
.It Fl i
mdoc(7) police: fix markup and spelling.
2001-05-16 10:29:51 +00:00
Display the card identification string and type ID.
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.It Fl r
mdoc(7) police: fix markup and spelling.
2001-05-16 10:29:51 +00:00
Reinitialize the card.
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
For boards with external port modules, it is possible to add or remove
modules and dynamically reprobe the number of ports using this switch.
mdoc(7) police: fix markup and spelling.
2001-05-16 10:29:51 +00:00
All ports on the card must be closed in order to reinitialize the card.
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.Pp
mdoc(7) police: fix markup and spelling.
2001-05-16 10:29:51 +00:00
It is preferable to reinitialize the card rather than reload the entire
digi module as reinitialization only affects the specified board rather
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
than affecting all attached boards.
.El
.Sh BUGS
mdoc(7) police: fix markup and spelling.
2001-05-16 10:29:51 +00:00
It should be possible to reinitialize a board without closing all of the
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
existing ports.
.Sh HISTORY
The
.Nm
The .Nm utility
2002-07-14 14:47:15 +00:00
utility first appeared in
Add a ``digi'' driver. This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
2001-05-02 01:08:09 +00:00
.Fx 5.0 .
Reference in New Issue Copy Permalink