1AVMCAPICTRL(8) Linux System Administration AVMCAPICTRL(8)
2
6 avmcapictrl - Add, reset or remove active AVM cards and load firmware
7
9 avmcapictrl add <portbase> <irq> <type>
10 avmcapictrl load <bootcode> [<contrnr> [<protocol>
11 [P2P | <dn1>:<spid1> [<dn2>:<spid2>]]]]
12 avmcapictrl reset [contrnr]
13 avmcapictrl remove [contrnr]
14 avmcapictrl trace [contrnr] [off|short|on|full|shortnodata|nodata]
15 avmcapictrl addcard <driver> <portbase> <irq> [ <membase> [ <cardnr> ]
16 ]
17
19 avmcapictrl is used to register active AVM ISA cards to the kernelcapi
20 system and therewith to the ISDN system. You need it also to upload the
21 firmware to any active AVM card. If an error occurs please also check
22 the kernel error messages using the command dmesg(8).
23
25 add <portbase> <irq> <type>
26 is used to add an ISA card to the kernel-capi2.0 system. The
27 portbase can have the values 0x150, 0x250, 0x300 and 0x340 for the
28 B1 ISA cards, look at the jumper on the card. For a T1-ISA (HEMA)
29 card you can select a wide range of ports.
30 irq can be selected from the following values:
31 3, 4, 5, 6, 7, 9, 10, 11, 12 and 15.
32 type can be B1 or T1.
33 load <bootcode> [<contrnr> [<protocol>
35 [P2P | <dn1>:<spid1> [<dn2>:<spid2>]]]] is used to load the
36 firmware to a card bootcode is a t4-file. The actual versions of
37 the t4-files for the different D channel protocols can be found at
38 ftp://ftp.in-berlin.de/pub/capi4linux/firmware/b1/
39 You need different t4-files for different D channel protocols:
40 b1-1tr6.t4 for 1TR6, b1.t4 for DSS1 and
41 b1-usa.t4 for 5ESS and NI1 (DSS1 is also supported).
42 For M1/M2 PCMCIA cards you need m1-s10.t4 or m1-s4.t4 depending on
43 the handy type used.
44 contrnr is the number of the controller (card) starting from 1.
45 protocol can be DSS1, CT1, VN3, AUSTEL, 5ESS or NI1.
46 P2P point to point
47 DN1:SPID1 DN2:SPID2 is for the North American 5ESS and NI1 proto‐
48 cols.
49 reset [contrnr]
51 is used to reset a card if loading has failed. This function only
52 makes sense if a card is not successfully loaded.
53 contrnr is the number of the controller (card) starting from 1.
54 remove [contrnr]
56 is used to remove a card previously added. You can also remove
57 cards added automatically (for example a B1-PCI card).
58 contrnr is the number of the controller (card) starting from 1.
59 trace [contrnr] [off|short|on|full|shortnodata|nodata]
61 is used to trace CAPI2.0 messages. The trace will be done as ker‐
62 nel messages, see dmesg(8).
63 contrnr is the number of the controller (card) starting from 1.
64 off switch off tracing
65 short switch on "one line per CAPI2.0 message" tracing
66 on | full switch on "full decode" tracing
67 shortnodata switch on "one line per CAPI2.0 message" tracing, but
68 exclude DATA_B3_IND and DATA_B3_REQ messages.
69 on | full switch on full decode tracing, but exclude DATA_B3_IND
70 and DATA_B3_REQ messages.
71 addcard <driver> <portbase> <irq> [ <membase> [ <cardnr> ] ]
73 is used to add a card, this is more generic than add.
74 driver currently b1isa or t1isa
75 portbase can have the values 0x150, 0x250, 0x300 and 0x340 for the
76 b1isa driver, look at the jumper on the card. For t1isa driver
77 you can select an wide range of ports.
78 irq can be selected from the following values: 3, 4, 5, 6, 7, 9,
79 10, 11, 12 and 15.
80 membase memory address if needed by driver
81 cardnr only useful with driver t1isa
82
85 Carsten Paeth <calle@calle.in-berlin.de>
86
88 ttyI(4), isdnctrl(8), isdninfo(4). dmesg(8). syslogd(8).
894th Berkeley Distribution 2000/01/28 AVMCAPICTRL(8)