README.icn 5.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148
  1. $Id: README.icn,v 1.1.1.1 2007/06/12 07:27:12 eyryu Exp $
  2. You can get the ICN-ISDN-card from:
  3. Thinking Objects Software GmbH
  4. Versbacher Röthe 159
  5. 97078 Würzburg
  6. Tel: +49 931 2877950
  7. Fax: +49 931 2877951
  8. email info@think.de
  9. WWW http:/www.think.de
  10. The card communicates with the PC by two interfaces:
  11. 1. A range of 4 successive port-addresses, whose base address can be
  12. configured with the switches.
  13. 2. A memory window with 16KB-256KB size, which can be setup in 16k steps
  14. over the whole range of 16MB. Isdn4linux only uses a 16k window.
  15. The base address of the window can be configured when loading
  16. the lowlevel-module (see README). If using more than one card,
  17. all cards are mapped to the same window and activated as needed.
  18. Setting up the IO-address dipswitches for the ICN-ISDN-card:
  19. Two types of cards exist, one with dip-switches and one with
  20. hook-switches.
  21. 1. Setting for the card with hook-switches:
  22. (0 = switch closed, 1 = switch open)
  23. S3 S2 S1 Base-address
  24. 0 0 0 0x300
  25. 0 0 1 0x310
  26. 0 1 0 0x320 (Default for isdn4linux)
  27. 0 1 1 0x330
  28. 1 0 0 0x340
  29. 1 0 1 0x350
  30. 1 1 0 0x360
  31. 1 1 1 NOT ALLOWED!
  32. 2. Setting for the card with dip-switches:
  33. (0 = switch closed, 1 = switch open)
  34. S1 S2 S3 S4 Base-Address
  35. 0 0 0 0 0x300
  36. 0 0 0 1 0x310
  37. 0 0 1 0 0x320 (Default for isdn4linux)
  38. 0 0 1 1 0x330
  39. 0 1 0 0 0x340
  40. 0 1 0 1 0x350
  41. 0 1 1 0 0x360
  42. 0 1 1 1 NOT ALLOWED!
  43. 1 0 0 0 0x308
  44. 1 0 0 1 0x318
  45. 1 0 1 0 0x328
  46. 1 0 1 1 0x338
  47. 1 1 0 0 0x348
  48. 1 1 0 1 0x358
  49. 1 1 1 0 0x368
  50. 1 1 1 1 NOT ALLOWED!
  51. The ICN driver may be built into the kernel or as a module. Initialization
  52. depends on how the driver is built:
  53. Driver built into the kernel:
  54. The ICN driver can be configured using the commandline-feature while
  55. loading the kernel with LILO or LOADLIN. It accepts the following syntax:
  56. icn=p,m[,idstring1[,idstring2]]
  57. where
  58. p = portbase (default: 0x320)
  59. m = shared memory (default: 0xd0000)
  60. When using the ICN double card (4B), you MUST define TWO idstrings.
  61. idstring must start with a character! There is no way for the driver
  62. to distinguish between a 2B and 4B type card. Therefore, by supplying
  63. TWO idstrings, you tell the driver that you have a 4B installed.
  64. If you like to use more than one card, you can use the program
  65. "icnctrl" from the utility-package to configure additional cards.
  66. You need to configure shared memory only once, since the icn-driver
  67. maps all cards into the same address-space.
  68. Using the "icnctrl"-utility, portbase and shared memory can also be
  69. changed during runtime.
  70. The D-channel protocol is configured by loading different firmware
  71. into the card's memory using the "icnctrl"-utility.
  72. Driver built as module:
  73. The module icn.o can be configured during "insmod'ing" it by
  74. appending its parameters to the insmod-commandline. The following
  75. syntax is accepted:
  76. portbase=p membase=m icn_id=idstring [icn_id2=idstring2]
  77. where p, m, idstring1 and idstring2 have the same meanings as the
  78. parameters described for the kernel-version above.
  79. When using the ICN double card (4B), you MUST define TWO idstrings.
  80. idstring must start with a character! There is no way for the driver
  81. to distinguish between a 2B and 4B type card. Therefore, by supplying
  82. TWO idstrings, you tell the driver that you have a 4B installed.
  83. Using the "icnctrl"-utility, the same features apply to the modularized
  84. version like to the kernel-builtin one.
  85. The D-channel protocol is configured by loading different firmware
  86. into the card's memory using the "icnctrl"-utility.
  87. Loading the firmware into the card:
  88. The firmware is supplied together with the isdn4k-utils package. It
  89. can be found in the subdirectory icnctrl/firmware/
  90. There are 3 files:
  91. loadpg.bin - Image of the bootstrap loader.
  92. pc_1t_ca.bin - Image of firmware for german 1TR6 protocol.
  93. pc_eu_ca.bin - Image if firmware for EDSS1 (Euro-ISDN) protocol.
  94. Assuming you have installed the utility-package correctly, the firmware
  95. will be downloaded into the 2B-card using the following command:
  96. icnctrl -d Idstring load /etc/isdn/loadpg.bin /etc/isdn/pc_XX_ca.bin
  97. where XX is either "1t" or "eu", depending on the D-Channel protocol
  98. used on your S0-bus and Idstring is the Name of the card, given during
  99. insmod-time or (for kernel-builtin driver) on the kernel commandline.
  100. To load a 4B-card, the same command is used, except a second firmware
  101. file is appended to the commandline of icnctrl.
  102. -> After downloading firmware, the two LEDs at the back cover of the card
  103. (ICN-4B: 4 LEDs) must be blinking intermittently now. If a connection
  104. is up, the corresponding led is lit continuously.
  105. For further documentation (adding more ICN-cards), refer to the manpage
  106. icnctrl.8 which is included in the isdn4k-utils package.