DigiWARE Release Notes 93000186H for Digi AccelePort Device Driver Digital UNIX (formerly OSF/1) V3.X & 4.X Software Package P/N 75000186H Diskette P/N 40001180H V1.4.2 (3.5") Software Manual P/N 92000186D July 10, 1998 This DigiWARE software package includes device drivers for the following product families: AccelePort C/X ISA/EISA/PCI AccelePort EPC/X ISA/EISA/PCI AccelePort Xem ISA/EISA/PCI AccelePort Xr ISA/PCI AccelePort Xr 920 ISA/PCI Enhancements: Version 1.4.1: This version of the Digital UNIX driver now supports the use of the following hardware: 4 and 8 port Digi AccelePort Xr 920 ISA 4 and 8 port Digi AccelePort Xr 920 PCI The driver installation and configuration procedures have been modified to: Correctly name the installed package with the same three digit code as the version number of the de- vice driver. Allow the reconfiguration of an installed device driver. Save driver configuration across driver updates. To determine the installed driver package, enter the following command: sseettlldd --ii || ggrreepp DDGGII Digital Unix V3.X & 4.x - 1 - Release Notes The installed package has the keyword _i_n_s_t_a_l_l_e_d next to it in the listing. To reconfigure an installed device driver: sseettlldd --cc <> ccoonnffiigg Where _p_a_c_k_a_g_e is replaced by the installed package name as determined above. The new driver package will ask if you would like to save the current configuration if you remove it with the ``_s_e_t_l_d _-_d'' command, and will ask if you would like to use this saved configuration if it detects one during the install process. Version 1.4.0: This version of the Digital UNIX driver now supports the use of the following hardware: 4 and 8 Port Modem/Xem EBI modules The driver has been modified so that users may enable (with a ditty option) processing in the device driver which correctly handles the CRTSCTS control flag avail- able in the _t_e_r_m_i_o_s structure in Digital UNIX 4.x. This flag is used by the _c_r_t_s_c_t_s option of _s_t_t_y in Digital UNIX 4.x and provides a user mode method for setting and clearing hardware pacing, normally only available via Digi's ditty utility. The _d_i_t_t_y utility has been modified to include a new option: _o_s_r_t_s_c_t_s. This option, by default, is off, and should NOT be turned on by users of Digital UNIX 3.2x. Digital UNIX 4.x users can turn this feature on to en- able the _c_r_t_s_c_t_s functionality of the stty utility to get and set the status of RTS/CTS hardware flow con- trol. With this driver revision, Digital UNIX 4.x customers can use the _d_i_t_t_y utility to turn on the _o_s_r_t_s_c_t_s flag for a port. Once on, hardware flow control can be con- trolled by the _s_t_t_y _c_r_t_s_c_t_s command. When the _o_s_r_t_s_c_t_s flag is enabled, applications which do nnoott set the CRTSCTS flag in the _c_f_l_a_g_s of their termios structures will cause hardware flow control to be disabled, even for the _m_o_d_e_m _c_o_n_t_r_o_l devices (those ending in the let- ter `m'). Digital Unix V3.X & 4.x - 2 - Release Notes Bug Fixes: Version 1.4.2: The device driver incorrectly handled a particular set of circumstances involving software flow control. The following set of conditions will demonstrate the prob- lem in older revisions of the driver (other sets of conditions may also produce the same effect due to the bug): Both the sender and receiver are using software flow control, The sender uses an application which inserts an in-band ioctl inbetween two _b_u_r_s_t_s of data, The very last character of the first _b_u_r_s_t of data causes the receiver to transmit an XOFF character, The ioctl processing (which is allowed to continue immediately because the transmitter is empty) com- pletes before the receiver transmits the XON char- acter, The second _b_u_r_s_t is transmitted as soon as the ioctl returns a successful status. When all of the above conditions were met, the driver began transmitting the second _b_u_r_s_t before the XON was received from the receiver due to a bug in the driver. As a result, a chance existed for the receiver to over- run, and for data loss to occur. This hole in the handling of software flow control within the ioctl processing has been fixed in the 1.4.1.1 device driver. In the unlikely case that an installation depends on the questionable behavior of the driver forcing the re- sumption of transmission during the processing of in- band ioctls (after waiting for drain), the behavior may be re-enabled with the hidden _d_i_t_t_y switch _i_o_c_t_l_r_e_s (standing for _I_O_C_T_L _p_r_o_c_e_s_s_i_n_g _f_o_r_c_e_s _R_E_S_u_m_p_t_i_o_n). Version 1.4.1: The firmware shipped with the 1.4.0 device driver for use with the C/X product line had a bug in it which in- hibited normal operation. All of the firmware images have been updated in this revision of the software to address this bug. The Digi _f_a_s_t_b_a_u_d flag used to be oonn by default, caus- Digital Unix V3.X & 4.x - 3 - Release Notes ing problems for applications trying to use slower baud rates with freshly installed packages. The _f_a_s_t_b_a_u_d flag now defaults in the ooffff state. As always, the _d_i_t_t_y utility may be used to toggle this flag. Version 1.4.0: The driver would sometimes fail after about 24 1/4 days of system uptime due to the incorrect handling of an internal counter. This problem has been eliminated. The entries in the /etc/inittab file which are added during adapter configuration were written incorrectly on Digital UNIX 4.x systems; this behavior has been corrected. A minor modem signaling bug on the Xr and Xem adapters has been addressed via the updating of the firmware im- ages accompanying the driver. The TCSBRK, TIOCSBRK, and TIOCCBRK ioctls would not wait for buffered output data to drain from the adapter before being processed. As a result, requests to set and clear _b_r_e_a_k would not execute in sequence with the data stream. Also, code which depends on the _d_r_a_i_n_i_n_g of output data as a side effect of setting break (i.e. the _t_c_d_r_a_i_n function, which causes a TCSBRK ioctl to be sent to the driver) would not wait for drain as expect- ed. This behavior has been fixed in the current revi- sion. The device driver was not properly enabling the default flow control scheme at device open time, resulting in instances in which the modem control devices (or `m' devices) would not have RTS/CTS flow control enabled immediately after opening. This has been corrected. Known Limitations: This version of the Digital UNIX 4.0 driver does nnoott cur- rently support the boot-linked kernel option of this operat- ing system. Digital Unix V3.X & 4.x - 4 - Release Notes Digital Qualification: Certain versions of the Digital UNIX device driver software have passed Digital's software qualification process in ac- cordance with the following table. This information is pro- vided solely for the convenience of our customers. +----------------------------------------------------------------+ | Diskette Part Number: 40001180E | | Software Revision: 1.3.0 | +----------------------------------------------------------------+ | Digital Qualified Operating System | | Hardware Platform Digi Hardware Version | +----------------------------------------------------------------+ | AlphaStation 255/233 PCI/4r Digital UNIX 3.2g | | AlphaStation 255/300 PCI/8r | | AlphaStation 500/266 | | AlphaStation 500/333 | | AlphaStation 500/400 | | AlphaStation 500/500 | | AlphaStation 600/266 | | AlphaStation 600/333 | +----------------------------------------------------------------+ +----------------------------------------------------------------+ | Diskette Part Number: 40001180F | | Software Revision: 1.4.0 | +----------------------------------------------------------------+ | Digital Qualified Operating System | | Hardware Platform Digi Hardware Version | +----------------------------------------------------------------+ | AlphaServer 300 ISA/16em Digital UNIX 3.2g | | AlphaServer 400 ISA/EPC Digital UNIX 4.0b | | AlphaServer 800 | | AlphaServer 1000 | | AlphaServer 1000A | | AlphaServer 2100 | | AlphaServer 2100A | | AlphaServer 8200 | +----------------------------------------------------------------+ | AlphaServer 4100 ISA/16em Digital UNIX 3.2g | | ISA/EPC Digital UNIX 4.0b | | PCI/4r | | PCI/8r | | PCI/16em | +----------------------------------------------------------------+ | AlphaServer 8400 PCI/4r Digital UNIX 3.2g | | PCI/8r Digital UNIX 4.0b | | PCI/16em | +----------------------------------------------------------------+ Digital Unix V3.X & 4.x - 5 - Release Notes