
#
# CAPI manager driver for the AVM active ISDN adapters (B1, C2, C4, T1)
#
# The CAPI manager module "kcapimgr" is also needed when this device is entered
# into a kernel configuration file.
#
# Note: Compiling this module as a separate module (i.e. not directly into the
#       kernel) is preferred. So it is better to comment out the following
#       device line.
#
# Supported flags:
#    0x00 (or no flags) AVM-B1 ISA
#    0x10 - 0x13        AVM-T1 ISA with board number 0 - 3 (low nibble of
#                       flags)
#
# Supported options:
#    AVMAIC_LOG_LEVEL           initializes the log level for the driver
#    AVMAIC_MAX_APPLICATIONS    specifies the maximum no. supported
#                               simultaneously registered applications,
#                               default is 30
#    AVMAIC_MAX_NCCI_PER_CHANNEL
#                               specifies the maximum no. possible B3
#                               connections per channel and application,
#                               default is 4
#
device avmaic
# AVM-B1 ISA
hint.avmaic.0.at="isa"
hint.avmaic.0.port="0x150"
hint.avmaic.0.irq="5"

#
# CAPI manager driver for the legacy Diehl active ISDN adapters (S, SX, SXn,
# SCOM, Quadro, S2m)
#
# The CAPI manager module "kcapimgr" is also needed when this device is entered
# into a kernel configuration file.
#
# Note: Compiling this module as a separate module (i.e. not directly into the
#       kernel) is preferred. So it is better to comment out the following
#       device line.
#
# Note2: The code for the S2m board is currently not implemented.
#
# Supported options:
#    DAIC_LOG_LEVEL		initializes the log level for the driver
#    DAIC_MAX_APPLICATIONS	specifies the maximum no. supported
#				simultaneously registered applications,
#				default is 30
#    DAIC_MAX_NCCI_PER_PLCI	specifies the maximum no. supported NCCIs per
#				PLCI (useful for ISO 8208 B3-protocol),
#				default is 4
#    DAIC_MAX_NCCI_PER_PORT	specifies the overall maximum no. supported
#				NCCIs per port of a board, default is 128
#    DAIC_MAX_PLCI_PER_PORT	specifies the overall maximum no. supported
#				PLCIs per port of a board, default is 64
#
# For more information about the effect of these driver options see the manual
# page daic(4).
#
device daic
# Diehl S, SX, SXn, SCOM (specifying the memory size is optional)
hint.daic.0.at="isa"
hint.daic.0.maddr="0xD0000"
hint.daic.0.msize="0x800"
hint.daic.0.irq="10"
# Diehl Quattro (specifying the memory size is optional)
hint.daic.0.at="isa"
hint.daic.0.maddr="0xD0000"
hint.daic.0.msize="0x2000"
hint.daic.0.irq="10"
# Diehl S2m (specifying the memory size is optional)
hint.daic.0.at="isa"
hint.daic.0.maddr="0xD0000"
hint.daic.0.msize="0x4000"
hint.daic.0.irq="10"

#
# CAPI manager driver for the IX1 active ISDN adapters
#
# These ISDN boards were originally manufactured by ITK, Germany, that is now
# part of Digi International. The boards were also sold under the name Digi
# Datafire. See ix1a(4) for further information.
#
# The CAPI manager module "kcapimgr" is also needed when this device is entered
# into a kernel configuration file.
#
# Note: Compiling this module as a separate module (i.e. not directly into the
#       kernel) is preferred. So it is better to comment out the following
#       device line.
#
# Supported flags (see ix1a(4) for detailed information):
#    0x00 - 0x03        IX1 Basic ISA, card types 1-4
#    0x10 - 0x13        IX1 Octo ISA, card types 1-4
#    0x20 - 0x27        IX1 Multimodem ISA, card types 1-8
#
# Supported options:
#    IX1A_LOG_LEVEL             initializes the log level for the driver
#
device ix1a
# IX1 Basic ISA, card number 1
hint.ix1a.0.at="isa"
hint.ix1a.0.port="0x380"
hint.ix1a.0.irq="5"
hint.ix1a.0.flags="0x00"
# IX1 Octo ISA, card number 2
hint.ix1a.0.at="isa"
hint.ix1a.0.port="0x380"
hint.ix1a.0.irq="5"
hint.ix1a.0.flags="0x11"
# IX1 Multimodem ISA, card number 8
hint.ix1a.0.at="isa"
hint.ix1a.0.port="0x380"
hint.ix1a.0.irq="5"
hint.ix1a.0.flags="0x27"

#
# i4b driver to support CAPI controllers
#
# The CAPI manager module "kcapimgr" is also needed when this device is entered
# into a kernel configuration file.
#
# Note: Compiling this module as a separate module (i.e. not directly into the
#       kernel) is preferred. So it is better to comment out the following
#       device line.
#
# Supported options:
#    I4BCAPIMGR_LOG_LEVEL       initializes the log level for i4bcapimgr,
#                               integer value
#    I4BCAPIMGR_ALLOC_MAX_BDATA_SIZE
#                               Normally incoming data blocks are forwarded to
#                               the layer 4 drivers just as they are. But there
#                               are situations (activated VJ compression and
#                               uncompression is performed in the received
#                               mbuf) where it is assumed that the received
#                               mbuf is allocated with the maximum size of 2kB.
#                               If this option is set, all incoming data blocks
#                               are copied into new mbufs of maximum size, thus
#                               wasting memory and computing time.
#
device   "i4bcapimgr"
