loopctrl(8) [suse man page]
LOOPCTRL(8) Linux System Administration LOOPCTRL(8) NAME
loopctrl - configure isdnloop ISDN driver SYNOPSIS
loopctrl [-d Driver-Id] action options ... DESCRIPTION
loopctrl is used to setup the isdnloop ISDN driver. OPTIONS
-d Driver-Id selects the virtual S0 interface named by Driver-Id. Driver-Ids are defined during driver initialisation. See isdnloop(4) for a description of the syntax to be used for modularised and monolithic driver versions. This option must be used to identify the vir- tual S0 interface if more than one S0 interface is existent. If a single virtual S0 interface is used, it may be omitted. If using more than one virtual card, support for the other cards is enabled with the add action of loopctrl. Ids may not start with digits or small x, because these values are misinterpreted as numeric parameters by insmod. For loading the module, always the newest modu- tils package should be used to avoid problems during load. The following actions may be given to loopctrl. add [id] enables support for an additional virtual card in the driver. If id is missing, adds a card with an id given by the system. with id given, adds a card with an Id given by the user. Ids are checked against conflicts, and if a conflict happens, replaced by the sys- tem in the same manner as if no Id was supplied. leased on|off switches between normal (dialup) and leased-line mode. Leased-line mode is intended for usage with S64K-lines or - if both channels are used - for S02. These lines do not have a D-channel. When leased-line mode is enabled, the driver simulates incoming calls using special "phone-numbers" for calling and called address which are generated as follows: Calling number: LEASEDx where x is the internal slot-number of the S0 interface. This number starts with 0 for the first S0 interface and is incremented by one for every S0 interface configured using the add action. Called number: x where x is equal to the channel number of the calling S0 interface starting with 1. start protocol phone1 [phone2 phone3] starts the driver with the given D-channel protocol. If protocol is 1tr6, only phone1 has to be given. It is meant to be the base number of the virtual S0 interface to which the EAZ is appended. If protocol is dss1, phone1, phone2 and phone3 have to be given and represent the three MSNs of the virtual S0 interface. dump is available if the program is configured using the --enable-dump option only. The contents of internal driver variables is dumped on stdout. BUGS
This program and the isdnloop driver are ALPHA code. The main intention for this driver is for testing the link level and applications. AUTHOR
(C) 1997 by Fritz Elfert <fritz@isdn4linux.de> SEE ALSO
isdnctrl(8), isdnloop(4), isdninfo(4), isdnctrl(4), ttyI(4). isdn4k-utils-3.13 1999/09/06 LOOPCTRL(8)
Check Out this Related Man Page
ICNCTRL(8) Linux System Administration ICNCTRL(8) NAME
icnctrl - configure ICN ISDN adaptor SYNOPSIS
icnctrl [-d Driver-Id] action options ... DESCRIPTION
icnctrl is used to setup the ICN ISDN device driver and for downloading the firmware into the ISDN card. The use of icnctrl makes sense, if you are using an ICN card only. OPTIONS
-d Driver-Id selects the S0 interface named by Driver-Id. Driver-Ids are defined during driver initialisation. See icn(4) for a description of the syntax to be used for modularised and monolithic driver versions. This option must be used to identify the S0 interface if more than one S0 interface is existent. If a single ICN-2B is used, it may be omitted. If using more than one card, support for the other cards is enabled with the add action of icnctrl. Ids may not start with digits or small x, because these values are misinter- preted as numeric parameters by insmod. For loading the module, always the newest modutils package should be used to avoid problems during load. The following actions may be given to icnctrl. add port [id1 [id2]] enables support for an additional card in the driver. If id1 and id2 are missing, adds an ICN-2B with an id given by the system. with id2 missing, adds an ICN-2B with an Id given by the user. With both Ids given, adds an ICN-4B with both Ids given by the user. There is no checking against port-conflicts. Ports are checked later during first activation while downloading the firmware and can be changed at runtime. Ids are checked against conflicts, and if a conflict happens, replaced by the system in the same manner as if no Id was supplied. It is not allowed, to add cards, after a load was done. io [base-address port] sets the address of the memory-mapped IO-region and the port-base. After loading the icn-module into kernel-space, this command should be used as the very first setup, if the hardware settings are different from the default settings below. If both parameters are omitted, prints out current settings. The default memory address is 0xD0000, the default port-base is 0x320. An ICN card uses 4 port-addresses. The memory address is globally used for all cards (cards are mapped on demand), while each card has its own port range. Memory range is 16k. leased on|1|2|off switches between normal (dialup) and leased-line mode. Leased-line mode is intended for usage with S64K-lines or - if both channels are used - for S02. If the second parameter is 1 , only one channel is enabled. If the second parameter is 2 or on both channels are enabled. Leased lines do not have a D-channel. When leased-line mode is enabled, the driver simulates incoming calls using spe- cial "phone-numbers" for calling and called address which are generated as follows: Calling number: LEASEDx where x is the internal slot-number of the S0 interface. This number starts with 0 for the first S0 interface and is incremented by one for every S0 interface configured using the add action. Called number: x where x is equal to the channel number of the calling S0 interface starting with 1. load boot-code firmware [firmware2] downloads the firmware into the card and starts operation. Using this command, after loading the icn-module into kernel-space the first real access to the hardware is done. Therefore the io action above, should be used before, if the hardware settings are dif- ferent from the default settings. Usually the images are located in @DATADIR@. The boot-code is named loadpg.bin. The firmware depends on the D-channel protocol of the ISDN line. For German 1TR6-lines, the firmware is named pc_1t_ca.bin. For Euro-ISDN-lines, it is named pc_eu_ca.bin. When loading an ICN-4B, two firmware parameters have to be supplied. The first firmware is used for the upper S0 connector, the second firmware is used for the lower S0 connector (towards the card's slot connector). dump is available if the program is configured using the --enable-dump option only. The contents of internal driver variables is dumped on stdout. FILES
@DATADIR@/loadpg.bin This is the image of the bootstrap loader, which is loaded first, then loads the firmware into the card's memory and starts execu- tion. @DATADIR@/pc_1t_ca.bin This is the image of the firmware designed for the German 1TR6 protocol. @DATADIR@/pc_eu_ca.bin This is the image of the firmware, designed for Euro ISDN. DIAGNOSTICS
The following diagnostics may be issued on stderr: Read error on boot-code The file supplied as boot-code has less than 4096 bytes length or could not be read. Read error on firmware The file supplied as firmware has less than 65536 bytes length or could not be read. BUGS
No bugs so far. AUTHOR
(C) 1997 by Fritz Elfert <fritz@isdn4linux.de> SEE ALSO
isdnctrl(8), icn(4), isdnctrl(4), ttyI(4). isdn4k-utils-3.13 1999/09/06 ICNCTRL(8)