




			    Release Notes 93000360D

	     Digi DataFire/AccelePort RAS and AccelePort Xp package
				  DGAP V1.0.3a
				      for
			       SCO OpenServer 5.x

			 Diskette #1 P/N 40002091D (3")
			   Source file P/N 81000140D

				  May 10, 2002

			 Device	Driver Version V1.0.7a
	      AccelePort/DataFire RAS firmware release_80006691_M
			   AccelePort Xp firmware DO

	  This	dgap  software	package	 includes  device  drivers for
	  Digi's  AccelePort  RAS,  Datafire  RAS  and	AccelePort  Xp
	  adapters.   The package also contains	Digi's Port Configura-
	  tion	Utility	 (PCU),	 Digi  Port  Authority	(DPA),	ditty,
	  dm_gui,  dmadmin,  dm_bb,  ras_trace and an agent for	Digi's
	  Port Assist Manager (PAM).

	   DGAP	V1.0.3a:

	  1. Supported Products

	  Digi AccelePort RAS 4	and 8 port adapters, Digi DataFire RAS
	  B4U,	B4ST,  PT1, PT2, PE1 and PE2 adapters and Digi Accele-
	  Port 2p, 4p, 8p and 16p adapters.

	  2. Enhancements

	     Upgraded RAS firmware to version M.

	  3. Bug Fixes

	     Fixed problem where Transparent Printing would not	 work.

	     Fixed problem where SCO PPP would fail to work on a port.

	     Fixed UUCP	binary file transfer problems.

	  4. Known Limitations

	  During bootup, you might  receive  errors  about  ports  not
	  being	"Ready".  On these systems, it may be necessary	to add
	  a "sleep 30" at the very bottom of /etc/rc2.d/S30dxbdl. This
	  will allow some extra	time for the firmware to be downloaded
	  to the board.

	  While	in loopback mode on the	Acceleport Xp products,	either
	  in  dpa or PAM, you cannot use PCU on	that specific adapter.
	  You MUST stop	the loopback test before using PCU.




				      -	1 -






	  This package will link into the kernel even if there	is  no
	  supported  board  installed  in the system.  When the	system
	  boots	up, the	driver searches	for supported  adapters.   The
	  first	 board	detected  will get his devices assigned	first.
	  If there are multiple	boards of a particular type  installed
	  in  the  system, the lowest slot number is configured	first.
	  Therefore, board ordering is important to how	 the  adapters
	  are  configured.   As	 an example:  If you have 2 AccelePort
	  RAS 8	adapters that have been	configured in you system, then
	  you decide later to add an AccelePort	RAS 4, when the	system
	  boots	up, the	Acceleport RAS in the lowest slot number  will
	  be  assigned	the  first  set	 of  device  nodes, the	second
	  detected AccelePort RAS adapter will get the second  set  of
	  device  nodes,  and  the third detected adapter will get the
	  third	set of device nodes.  If the newly added  adapter  was
	  not  added  in  a  slot higher than the previous 2 adapters,
	  device mapping will now be incorrect.	 NOTE:	A message will
	  print	 to the	system console at boot time if there have been
	  any boards added or removed from the system that this	driver
	  package knows	about.

	  The  DataFire	RAS PT1, PT2, PE1 and PE2 adapters have	device
	  names	in the format "/dev/ttyh[x]_[yy]" where	"x" is the  -1
	  of  the  adapter  and	 "yy" is the port -1 from 01-24	(PT1),
	  01-48	(PT2), 01-30 (PE1) or 01-60 (PE2).  All	other adapters
	  have	the  naming of "/dev/ttyh[x][a-pA-P]" where "x"	is the
	  -1 of	the adapter.

	  The Port Assist agent	is turned off by default.  It  can  be
	  enabled  by  removing	 the comment from the only line	in the
	  script /etc/rc2.d/S95apras.

	  There	is a tool called "dm_admin"  found  in	/usr/bin  that
	  will	allow you to configure AccelePort RAS and DataFire RAS
	  adapters.  There is a	man page "man dm_admin"	that describes
	  the programs usage.

	  There	 is a tool called "dm_gui" available under the graphi-
	  cal login that will allow you	to configure and  monitor  all
	  installed  adapters  that are	supported by this driver pack-
	  age.

	  There	is a tool called "ras_trace" found  in	/usr/bin  that
	  will allow you to trace serial, b-channel and	d-channel data
	  and status on	the supported adapters.	 There is a  man  page
	  "man ras_trace" that describes the programs usage.

	  The  tools dpa, pcu and ditty	can be found in	/usr/bin. They
	  can be used to assist	 you  in  configuring  and  monitoring
	  ports	that were configured through this package.

	  A   copy   of	  these	  release   notes   can	 be  found  in
	  "/etc/dgap/rnotes".

	  5. History




				      -	2 -






	    DGAP 1.0.2a

	  The driver now recognizes the	following ditty	options, which
	  were	 not  supported	 in  past  driver  versions:  CTSPACE,
	  RTSPACE, DTRPACE, DCDPACE, DSRPACE, FORCEDCD and PRINTER.

	  Added	support	for the	TIOCSDTR and TIOCCDTR ioctls.

	  Updated all supporting libraries. We now use TCL  8.0.5,  TK
	  8.0.5, and Tix 4.1.8.0

	  Fixed	 problem  when	using  Morningstar PPP.	 Under certain
	  conditions, it was possible that the pppd daemon would  can-
	  cel its open to the Digi port	at exactly the "wrong" moment.
	  This would cause the port to	lock  up  and  cause  all  new
	  attempts to open the port to fail.

	  Fixed	 problem where IOC_SELECT was giving false indications
	  that data was	ready to be read, when it was really not, thus
	  waking up the	select() syscall and causing read() to indefi-
	  nately block.	 This problem occurred on both the  Acceleport
	  RAS and Xp products.

	  Fixed	 problem  where	 concurrent  dm_gui's, dpa's, or pam's
	  running could	cause the driver to send the incorrect	infor-
	  mation  back to each respective application. This required a
	  driver change, along with reworking how the management chan-
	  nel was dealt	with in	dpa, pam, dm_gui and dm_admin.

	  Fixed	problem	where a	baud rate change to 0 did NOT drop DTR
	  and RTS.  This problem occurred on all support products.

	  Fixed	problem	where a	2nd open  to  a	 waiting-for-DCD  port
	  could	 trounce the CLOCAL setting of the 1st open to a wait-
	  ing-for-DCD port.  This  problem  was	 most  noticable  when
	  using	 the "ct" command, and occurred	on all supported prod-
	  ucts.

	  Fixed	problem	where RTS and DTR would	always be  dropped  on
	  port close, even when	HUPCL was turned off. This problem was
	  most noticable when using the	"ct" command, and occurred  on
	  all supported	products.

	  Fixed	 problem  where	 RTS and DTR would not be dropped when
	  disabling a getty on a waiting-for-DCD  port.	 This  problem
	  only occurred	with the Acceleport RAS	products.

	  Fixed	pcu to add the correct speed for a port	to the Devices
	  file when used as a "mio" or "mout" device.

	  Fixed	our driver reporting to	printcfg(D3oddi) to  correctly
	  report  the  starting	 and  ending IO	addresses of each sup-
	  ported Digi PCI card found. This bug would  show  itself  by
	  giving false "conflict" messages when	running	"hwconfig -c".

	    DGAP 1.0.1d



				      -	3 -






	     Fixed a driver bug	that caused a kernel panic if
	     several stty or ditty commands were issued
	     back to back for a	particular device.

	    DGAP 1.0.1c

	      Fixed the	ALL_CALL_STATUS	command	to correspond with the
	      latest changes in	the firmware.

	      Added driver names and versions for PAM to display.

	      Fixed  PCU  so that all supported	adapters are displayed
	  correctly.

	    DGAP 1.0.1b

	      Add support for DataFire RAS and Xp adapters.

	      Added the	ras_trace tool.

	      Added the	dm_gui configuration/monitoring	tool.

	      Added the	dm_bb utility and dxbram[x] devices
	      used to dump adapter memory on RAS adapters.

	    DGAP 1.0.0

	      Initial release for AccelePort RAS.































				      -	4 -


