patch-2.1.99 linux/Documentation/isdn/README.sc

• Lines: 211
• Date: Tue Apr 28 14:22:04 1998
• Orig file: v2.1.98/linux/Documentation/isdn/README.sc
• Orig date: Thu Feb 27 10:57:29 1997

diff -u --recursive --new-file v2.1.98/linux/Documentation/isdn/README.sc linux/Documentation/isdn/README.sc
@@ -9,7 +9,7 @@
 bugs and defects either known or unknown. Use this software at your own
 risk. There is NO SUPPORT for this software. Some help may be available
 through the web site or the mailing list but such support is totally at
-our own option and without warrantee. If you choose to assume all and
+our own option and without warranty. If you choose to assume all and
 total risk by using this driver, we encourage you to join the beta
 mailing list.
 
@@ -17,7 +17,7 @@
 majordomo@spellcast.com with the words "subscribe linux-beta" as the only
 contents of the message. Do not include a signature. If you choose to
 remove yourself from this list at a later date, send another message to
-the same address with the words "unsubscribe linux-beta" as it's only
+the same address with the words "unsubscribe linux-beta" as its only
 contents.
 
 TABLE OF CONTENTS
@@ -42,7 +42,7 @@
 ---------------
 
 The revision 2 Linux driver for SpellCaster ISA ISDN adapters is built
-upon ISDN4Linux available seperately or as included in Linux 2.0 and later.
+upon ISDN4Linux available separately or as included in Linux 2.0 and later.
 The driver will support a maximum of 4 adapters in any one system of any
 type including DataCommute/BRI, DataCommute/PRI and TeleCommute/BRI for a
 maximum of 92 channels for host. The driver is supplied as a module in
@@ -74,14 +74,14 @@
 	  allow us to utilize all of the available RAM on the adapter through
 	  only one 16K page.
 	- Better detection of available upper memory. The probing routines
-	  have been improved to better detect avaialble shared RAM pages and
+	  have been improved to better detect available shared RAM pages and
 	  used pages are now locked.
 	- Decreased loading time and a wider range of I/O ports probed.
 	  We have significantly reduced the amount of time it takes to load
 	  the driver and at the same time doubled the number of I/O ports
-	  probed increasing the likelyhood of finding an adapter.
+	  probed increasing the likelihood of finding an adapter.
 	- We now support all ISA adapter models with a single driver instead
-	  of seperate drivers for each model. The revision 2 driver supports
+	  of separate drivers for each model. The revision 2 driver supports
 	  the DataCommute/BRI, DataCommute/PRI and TeleCommute/BRI in any
 	  combination up to a maximum of four adapters per system.
 	- On board PPP protocol support has been removed in favour of the
@@ -115,7 +115,7 @@
 
 2.1 Unpacking and installing the driver
 
-	1. As root, create a directory in a convienient place. We suggest
+	1. As root, create a directory in a convenient place. We suggest
 	   /usr/src/spellcaster.
 	
 	2. Unpack the archive with :
@@ -170,36 +170,38 @@
 
 2.6 How to setup ISDN4Linux with the driver
 
-There are two main configurations which you can use with the driver:
+There are three main configurations which you can use with the driver:
 
 A)	Basic HDLC connection
 B)	PPP connection
 C)	MLPPP connection
 
-It should be mentioned here that you may also use a tty connection if you desire. 
-The Documentation directory of the isdn4linux subsystem offers a good documentation
-on this feature.
+It should be mentioned here that you may also use a tty connection if you
+desire. The Documentation directory of the isdn4linux subsystem offers good
+documentation on this feature.
 
 A) 10 steps to the establishment of a basic HDLC connection
 -----------------------------------------------------------
 
 - please open the isdn-hdlc file in the examples directory and follow along...
 	
-	This file is a script used to configure a BRI ISDN TA to establish a basic HDLC
-	connection between its two channels.  There two network interfaces which are 
-	created and two routes added between the channels.
+	This file is a script used to configure a BRI ISDN TA to establish a 
+	basic HDLC connection between its two channels.  Two network 
+	interfaces are created and two routes added between the channels.
 
-	i)   using the isdnctrl utitity, add an interface with "addif" and name it "isdn0"
+	i)   using the isdnctrl utitity, add an interface with "addif" and 
+	     name it "isdn0"
 	ii)  add the outgoing and inbound telephone numbers
 	iii) set the Layer 2 protocol to hdlc
-	iv)  set the eaz of the interface to be the phone number of that specific channel
+	iv)  set the eaz of the interface to be the phone number of that 
+	     specific channel
 	v)   to turn the callback features off, set the callback to "off" and
 	     the callback delay (cbdelay) to 0.
 	vi)  the hangup timeout can be set to a specified number of seconds
-	vii) the hangup upon incomming call can be set on or off 
-	viii) use the ifconfig command to bring-up the network interface with a specific
-	     IP address and point to point address
-	viv) add a route to the IP address through the isdn0 interface
+	vii) the hangup upon incoming call can be set on or off 
+	viii) use the ifconfig command to bring up the network interface with 
+	      a specific IP address and point to point address
+	ix)  add a route to the IP address through the isdn0 interface
 	x)   a ping should result in the establishment of the connection
 
 	
@@ -208,13 +210,15 @@
 
 - please open the isdn-ppp file in the examples directory and follow along...
 	
-	This file is a script used to configure a BRI ISDN TA to establish a PPP connection 
-	between the two channels.  The file is almost identical to the HDLC connection
-	example except that the packet ecapsulation type has to be set.
-	
-	use the same procedure as in the HDLC connection from steps i) to iii) then, 
-	after the Layer 2 protocol is set, set the encapsulation  "encap" to syncppp.
-	With this done, the rest of the steps, iv) to x) can be followed from above.
+	This file is a script used to configure a BRI ISDN TA to establish a 
+	PPP connection 	between the two channels.  The file is almost 
+	identical to the HDLC connection example except that the packet 
+	ecapsulation type has to be set.
+	
+	use the same procedure as in the HDLC connection from steps i) to 
+	iii) then, after the Layer 2 protocol is set, set the encapsulation 
+	"encap" to syncppp. With this done, the rest of the steps, iv) to x) 
+	can be followed from above.
 
 	Then, the ipppd (ippp daemon) must be setup:
 	
@@ -223,52 +227,55 @@
 	xiii) set the mru size to 2000
 	xiv)  link the two /dev interfaces to the daemon
 
-NOTE:  A "*" in the inbound telephone number specifies that a call can be accepted
-       on any number.
+NOTE:  A "*" in the inbound telephone number specifies that a call can be 
+accepted on any number.
 
 C) Establishment of a MLPPP connection
 --------------------------------------
 
 - please open the isdn-mppp file in the examples directory and follow along...
 	
-	This file is a script used to configure a BRI ISDN TA to accept a Multi Link PPP
-	connection. 
+	This file is a script used to configure a BRI ISDN TA to accept a 
+	Multi Link PPP connection. 
 	
-	i)   using the isdnctrl utitity, add an interface with "addif" and name it "ippp0"
+	i)   using the isdnctrl utitity, add an interface with "addif" and 
+	     name it "ippp0"
 	ii)  add the inbound telephone number
-	iii) set the Layer 2 protocol to hdlc and the Layer 3 protocol to trans (transparent)
+	iii) set the Layer 2 protocol to hdlc and the Layer 3 protocol to 
+	     trans (transparent)
 	iv)  set the packet encapsulation to syncppp
-	v)   set the eaz of the interface to be the phone number of that specific channel
-	vi)   to turn the callback features off, set the callback to "off" and
+	v)   set the eaz of the interface to be the phone number of that 
+	     specific channel
+	vi)  to turn the callback features off, set the callback to "off" and
 	     the callback delay (cbdelay) to 0.
 	vi)  the hangup timeout can be set to a specified number of seconds
-	vii) the hangup upon incomming call can be set on or off 
+	vii) the hangup upon incoming call can be set on or off 
 	viii) add a slave interface and name it "ippp32" for example
-	viv)  set the similar parameters for the ippp32 interface
-	x)    use the ifconfig command to bring-up the ippp0 interface with a specific
-	     IP address and point to point address
+	ix)  set the similar parameters for the ippp32 interface
+	x)   use the ifconfig command to bring-up the ippp0 interface with a 
+	     specific IP address and point to point address
 	xi)  add a route to the IP address through the ippp0 interface
 	xii) use the ipppd function found in /sbin/ipppd to set the following:
 	xiii) take out (minus) bsd compression
 	xiv) set the mru size to 2000
 	xv)  add (+) the multi-link function "+mp"
-	xv)  link the two /dev interfaces to the daemon
+	xvi)  link the two /dev interfaces to the daemon
 
-NOTE:  To use the MLPPP connection to dial OUT to a MLPPP connection, change the 
-       inbound telephone numbers to the outgoing telephone numbers of the MLPPP 
-       host.
+NOTE:  To use the MLPPP connection to dial OUT to a MLPPP connection, change 
+the inbound telephone numbers to the outgoing telephone numbers of the MLPPP 
+host.
 
 	
 3. Beta Change Summaries and Miscellaneous Notes
 ------------------------------------------------
-When using the "scctrl" utility to upload firmware revisions on the board, please
-note that the byte count displayed at the end of the operation may be different 
-than the total number of bytes in the "dcbfwn.nn.sr" file.  Please disregard the 
-displayed byte count.
-
-It was noted that in Beta Release 1, the module would fail to load and result in a
-segmentation fault when insmod"ed".  This problem was created when one of the 
-isdn4linux parameters, (isdn_ctrl, data field) was filled in.  In some cases, this
-data field was NULL, and was left unchecked, so when it was referenced.. segv.  
-The bug has been fixed around line 63-68 of event.c.
+When using the "scctrl" utility to upload firmware revisions on the board,
+please note that the byte count displayed at the end of the operation may be
+different from the total number of bytes in the "dcbfwn.nn.sr" file. Please
+disregard the displayed byte count.
+
+It was noted that in Beta Release 1, the module would fail to load and result
+in a segmentation fault when 'insmod'ed. This problem was created when one of
+the isdn4linux parameters, (isdn_ctrl, data field) was filled in. In some
+cases, this data field was NULL, and was left unchecked, so when it was
+referenced... segv. The bug has been fixed around line 63-68 of event.c.