Release Notes: SST Driver for Solaris
Installation Instructions
The zip download file is in "dd - compressed" UNIX file format. You must run "uncompress" then "dd" the file to a 1.44 MB disk device to create an install diskette and use "installpkg" to install the driver. View SOL_DNLD.TXT for additional installation information.
Release Notes
Version 3.45
· Added support for SST-4P/LP ( Low Profile) board.
Version 3.44
· On some occasions the restoration of panels after a loss of the Ring Clock would result in ports remaining in a bad state.
· Added additional code to the Expansion Bus management code to ensure that the SSP state machine is in a correct state and that the SSP Input registers are set to the correct values. In particular, a debounce delay was added when the driver sees the ring clock being restored after an outage and the register values are validated for an additional period after restoring the panels to an online state. This results in two delay periods of approximately 1 second
each (about 800 milliseconds).
· Provides a fix for Multiplexer Interface Modules (MIM-1) and Cluster Multiplexers (CMX16-DB and CMX16-RJ). With the previous release, these board pairs would never go "online".
Version 3.43
1) Added fixes for the 25' Expansion Bus problem (originally reported by HP) with newer SSP parts (ATMEL fix).
2) Added code to set the Memory Configured bit on SSP4 based boards with the problem part.
3) Added a fix to prevent potential hung ports resulting from interactions between data flushes and arriving data (the problem was originally observed on the UnixWare SST driver and the Solaris code had the same flaw).
4) Added support for the SST-16P CP16-DB9 panel.
Version 3.42
· Fixed coding problem that could result in stalled output.
· Add support for the Solaris documented "ttymodes" default open termios parameters.
Version 3.41
· This release adds support for the following new SST products:
o SST-4I,PWR
o SST-8I,PWR
o SST-4P,PWR
o SST-8P,PWR
Version 3.40
· The multiprocessing synchronization routines have been modified to allow the driver to link (work) with Solaris 7 (Solaris 7 deleted interfaces present in Solaris 2.1 - 2.6 and used by our driver -- it was necessary to modify the Equinox driver to call different functions).
· A problem introduced in 3.38 with modem pools configured on ISA cards has been corrected.
· A problem with using the Solaris native extended baud rate settings has been corrected. This problem resulted from applications setting split baud rates (i.e., setting the input and output baud rates independently). Applications not using split buad rates or extended baud rates would never see the problem. This problem was discovered during internal Validation testing at Equinox.
· A problem with deferring processing of received data because upstream streams modules were unable to take the data at a point in time was resolved. This only happened when the LAST incoming data arrived and was unable to be processed and no further data arrived. It resulted in the driver leaving data buffered on the board even though an application had posted a read. If any more data arrived, then the data would be moved. This was seen in testing with a
stress test that writes a fixed amount of data to the ports. It is unlikely to impact customer applications.
Version 3.39
· Added support for new PCI RJ boards: SST-8P/RJ and SST-4P/RJ.
· The TIOCMGET ioctl was fixed to return the correct state of the outbound control signals. Previously, if the port was in a flow control state, TIOCMGET would incorrectly indicate that the control signal (RTS or DTR) was still high.
· The TIOCGSOFTCAR and TIOCSSOFTCAR ioctls now mimic the behavior of the COMM port. The COMM port returns (1) true and (0) false to the G(et)SOFTCAR ioctl. Previously, the Equinox driver:
o - returned the hex value of CLOCAL rather than a 1 (and erroneously always returned true); and,
o - set CLOCAL in the tty structure when SOFTCAR was set (the COMM port does not).
· The TIOCMBIC, TIOCMBIS, and TIOCMSET ioctls now set/clear both the standard control signal and the overload control signal. Previously, they set only the standard control signal. This could result in incorrect behavior when in an overload (flow control) state. Further, these ioctls will not allow a signal being used for flow control to be programmatically altered (e.g., a request to change the state of RTS will be ignored if RTSXOFF is enabled).
· The driver now sets the termios settings to the documented Solaris defaults (see the termios man page) on the initial open of a port. The driver does not use the user modifiable defaults settable in /kernel/drv/options.conf per Solaris documentation. It is not clear how the driver can read these settings, thus that capability has been deferred to a future release.
· The Solaris driver now honors the CRTSXOFF (use RTS hardware flow control) and CRTSCTS (use CTS hardware flow control) flags in the termios c_cflag parameter. Previously, hardware flow control could only be set using the termiox ioctls.
Version 3.36
· The driver did not preserve termios settings when a termio TCSETA* ioctl was issued. This caused the driver to lose information, including the Extended Baud rate flags. Since the Solaris "login" process issues a TCSETA, it was impossible to configure a ttymon to use baud rates higher than 38400 on an Equinox port. The Equinox driver has been modified to mimic the behavior of the COM port driver when TCSETA* ioctls are issued. This change fixes the
problem.
|
