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 kernelcapi system
20 and therewith to the isdn system. You need it also to upload the
21 firmware to any active AVM card. If an error occure please also check
22 the kernel error messages by using the command dmesg(8).
23
25 add <portbase> <irq> <type>
26 is used to add a ISA card to the kernel-capi2.0 system. The port‐
27 base can have the values 0x150, 0x250, 0x300 and 0x340 for the B1
28 ISA cards, look at the jumper on the card. For a T1-ISA (HEMA)
29 card you can select an 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.avm.de/cardware/b1/linux/firmware.
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 american protocols 5ESS and NI1.
48 reset [contrnr]
50 is used to reset a card if loading has failed. This function only
51 make sence if card is not successfully loaded.
52 contrnr is the number of the controller (card) starting from 1.
53 remove [contrnr]
55 is used to remove a card previous added. You can also remove auto‐
56 matic added cards (for example a B1-PCI card).
57 contrnr is the number of the controller (card) starting from 1.
58 trace [contrnr] [off|short|on|full|shortnodata|nodata]
60 is used to trace CAPI2.0 messages. The trace will be done as ker‐
61 nel messages, see dmesg(8).
62 contrnr is the number of the controller (card) starting from 1.
63 off switch traceing off
64 short switch one line per CAPI2.0 message tracing on
65 on | full switch on full decode tracing
66 shortnodata switch on line per CAPI2.0 message tracing on, but
67 exclude DATA_B3_IND and DATA_B3_REQ messages.
68 on | full switch on full decode tracing, but exclude DATA_B3_IND
69 and DATA_B3_REQ messages.
70 addcard <driver> <portbase> <irq> [ <membase> [ <cardnr> ] ]
72 is used to add a card, this is more generic than add.
73 driver currently b1isa or t1isa
74 portbase can have the values 0x150, 0x250, 0x300 and 0x340 for the
75 b1isa driver, look at the jumper on the card. For t1isa driver
76 you can select an wide range of ports.
77 irq can be selected from the following values: 3, 4, 5, 6, 7, 9,
78 10, 11, 12 and 15.
79 membase memory address if needed by driver
80 cardnr only usefull with driver t1isa
81
84 Carsten Paeth <calle@calle.in-berlin.de>
85
87 ttyI(4), isdnctrl(8), isdninfo(4). dmesg(8). syslogd(8).
884th Berkeley Distribution 2000/01/28 AVMCAPICTRL(8)