1998-02-07 20:32:00 +00:00
|
|
|
.\" $Id: avmcapictrl.man.in,v 1.2 1998/02/07 20:32:02 calle Exp $
|
1997-03-23 11:52:53 +00:00
|
|
|
.\"
|
1998-02-07 20:32:00 +00:00
|
|
|
.\" CHECKIN $Date: 1998/02/07 20:32:02 $
|
1997-03-23 11:52:53 +00:00
|
|
|
.\"
|
|
|
|
.TH AVMCAPICTRL 8 "@MANDATE@" isdn4k-utils-@I4LVERSION@ "Linux System Administration"
|
1997-03-05 21:23:55 +00:00
|
|
|
.UC 4
|
|
|
|
.SH NAME
|
|
|
|
avmcapictrl \- Add AVM-B1 cards and load firmware
|
|
|
|
.SH SYNOPSIS
|
1998-02-07 20:32:00 +00:00
|
|
|
avmcapictrl add <portbase> <irq> <type>
|
1997-03-05 21:23:55 +00:00
|
|
|
.br
|
1998-02-07 20:32:00 +00:00
|
|
|
avmcapictrl load <bootcode> [<contrnr> [<protocol>
|
|
|
|
.br
|
|
|
|
[P2P | <dn1>:<spid1> [<dn2>:<spid2>]]]]
|
1997-03-05 21:23:55 +00:00
|
|
|
.br
|
|
|
|
avmcapictrl reset [contrnr]
|
|
|
|
.SH DESCRIPTION
|
|
|
|
.I avmcapictrl
|
|
|
|
is used to register AVM-B1 ISA cards to the
|
|
|
|
kernelcapi system and therewith to the isdn system.
|
|
|
|
You need it also to upload the firmware to any AVM-B1 card.
|
|
|
|
.LP
|
|
|
|
The use of
|
|
|
|
.I avmcapictrl
|
|
|
|
makes sense, if you are using an AVM-B1-card only.
|
|
|
|
.LP
|
|
|
|
.SH COMMANDS
|
|
|
|
.TP 5
|
1998-02-07 20:32:00 +00:00
|
|
|
.B add <portbase> <irq> <type>
|
1997-03-05 21:23:55 +00:00
|
|
|
is used to add a card to the kernel-capi2.0 system.
|
|
|
|
The
|
|
|
|
.I portbase
|
|
|
|
can have the values 0x150, 0x250, 0x300 and 0x340,
|
|
|
|
look at the jumper on the card.
|
|
|
|
The
|
|
|
|
.I irq
|
|
|
|
can be selected from the following values:
|
|
|
|
3, 4, 5, 6, 7, 9, 10, 11, 12 and 15.
|
1998-02-07 20:32:00 +00:00
|
|
|
.I type
|
|
|
|
can be B1 or T1.
|
1997-03-05 21:23:55 +00:00
|
|
|
.LP
|
|
|
|
.TP 5
|
1998-02-07 20:32:00 +00:00
|
|
|
.B load <bootcode> [<contrnr> [<protocol>
|
|
|
|
.B [P2P | <dn1>:<spid1> [<dn2>:<spid2>]]]]
|
1997-03-05 21:23:55 +00:00
|
|
|
is used to load the firmware to a card
|
|
|
|
.I bootcode
|
|
|
|
is a t4-file. The actual versions of the t4-files for the different
|
1998-02-07 20:32:00 +00:00
|
|
|
d-channel protocols can be found at
|
|
|
|
ftp://calle.in-berlin.de/pub/linux/avmb1/firmware.
|
|
|
|
you need different t4-files for different d channel protocols:
|
|
|
|
b1-1tr6.t4 for 1TR6, b1.t4 for DSS1, D64S, D64S2, D64SD, DS01, DS02, CT1,
|
|
|
|
VN3 or AUSTEL and b1-usa.t4 for 5ESS and NI1 (DSS1 is also supported).
|
|
|
|
For M1/M2 PCMCIA cards you need m1-s10.t4 or m1-s4.t4 depending on the
|
|
|
|
handy type used.
|
1997-03-05 21:23:55 +00:00
|
|
|
.I contrnr
|
|
|
|
is the number of the controller (card) starting from 1.
|
1998-02-07 20:32:00 +00:00
|
|
|
.I protocol
|
|
|
|
can be DSS1, D64S, D64S2, D64SD, DS01, DS02, CT1, VN3, AUSTEL, 5ESS or NI1.
|
|
|
|
.I P2P
|
|
|
|
point to point
|
|
|
|
.I DN1:SPID1 DN2:SPID2
|
|
|
|
is for the american protocols 5ESS and NI1.
|
1997-03-05 21:23:55 +00:00
|
|
|
.LP
|
|
|
|
.TP 5
|
|
|
|
.B reset [contrnr]
|
|
|
|
is used to reset a card if loading has failed.
|
|
|
|
This function only make sence if card is not successfully loaded.
|
|
|
|
.I contrnr
|
|
|
|
is the number of the controller (card) starting from 1.
|
|
|
|
|
|
|
|
.SH AUTHOR
|
|
|
|
Carsten Paeth <calle@calle.in-berlin.de>
|
|
|
|
.LP
|
|
|
|
.SH SEE ALSO
|
|
|
|
.I ttyI\c
|
|
|
|
\&(4),
|
|
|
|
.I isdnctrl\c
|
|
|
|
\&(8),
|
|
|
|
.I isdninfo\c
|
|
|
|
\&(4).
|