
                        Release Notes for
   DS21x4 PCI Ethernet / Fast Ethernet Adapter SCO Unix MDI driver

                     SUM310T - Release 03.10
                          14-Jan-1995


Copying the distribution files
------------------------------

Version 03.10 of the SCO Unix MDI driver for the DS21x4 PCI Ethernet
adapter is now available.

The distribution files are:

   SUM310TD.Z (48493)     - the compressed image of the distribution diskette
   TSUM_INS.TXT           - Installation Guide for the DS21x4 MDI driver
   TSUM_REL.TXT           - release notes for this release (this file)


   1.  Copy the file SUM310TD.Z to SUM310T.dd.Z on a SCO Unix machine.
       The number in parentheses near the file's name (above) is the checksum
       for the file. To verify, use:
          sum -r SUM310T.dd.Z
       and compare the results.                                   
   3.  Uncompress SUM310T.dd.Z to SUM310T.dd, using:
          uncompress SUM310T.dd
   4.  Copy the file to a diskette. To create a 3.5" floppy in drive 0, use:
          dd if=SUM310T.dd of=/dev/rfd0135ds18
       Mark the diskette: 
         DS21x4 PCI Ethernet Adapter MDI driver
         Rel.03.10







Version 03.10
-------------

New features and modifications:

1. Fix bug in updating CSR6 register during DS21140 autosense algorithm.
2. Update all driver's prefix from "DCE" to "dce"
3. Fix bug in updating the autosense information that was read from the SROM.
4. Add support to SROM version 3.0
5. Update driver to stop TX or/and RX machines while updating CSR6.
6. Update port selesct bit in CSR6 before SW.
7. Changes in netconfig parameters :
   
   In "media" option:
   - Change SYM_SCR to 100TX.
   - Change SYM_SCR_FD to 100TX_FD.
   - Add 100FX, 100FX_FD, 100T4

8. Add support to MII PHY chips.
9. Add support toDS21140A


Limitations:

Following are the known limitations of version 03.10:

1. The driver supports up to 1 port.

2. The driver support only boards that their SROM was programmed in the
   format of version 1.0, 3.0 and the boards that their SROM was programmed in 
   the classic version (32 bytes of Ethernet address and checksum).

3. The driver was tested under TCP and NFS protocols. The MDI interface
   was also tested. All tests that were run passed successfully.     

4. The driver doesn't support changing parameters in boot time.

5. When the system does an autosearch on boards it connect different drivers 
   to the same board if they both support controllers with DS2104x/DS21140 
   chip on them. This will be solved in the next release with the SubSystem
   verdor ID and SubSystem ID parameters.

6. The driver doesn't print an error when there is no link due to cabale fault.

7. The driver was tested with boards that have National PHY and boards that
   have Broadcom PHY.
   When setting the connection in boards with Broadcom PHY to 100T4 connection,
   the Broadcom PHY losses the first recieved packet after SW/HW reset.
   This cause the ANT tests to fail (the tests get out of synchronize.
   
8. The driver supports only boards with 1 MII PHY only

9. The driver doesn't support boards that both SymScr and MII PHY on the
   same board

10.On boards with MII PHY, the driver performs the autosense algorithm 
   on MII PHY media only.




History
=======

Version 03.00
-------------

This is the first version that support MDI interface.

Limitations:

Following are the known limitations of version 02.10:

1. The driver supports up to 1 port.

2. The driver support only boards that their SROM was programmed in the
   format of version 1.0 and the boards that their SROM was programmed in 
   the classic version (32 bytes of Ethernet address and checksum).

3. The driver was tested under TCP and NFS protocols. The MDI interface
   was also tested. All tests that were run passed successfully.     

4. The driver doesn't support changing parameters in boot time.

5. When the system does an autosearch on boards it connect different drivers 
   to the same board if they both support controllers with DS2104x/DS21140 
   chip on them. This will be solved in the next release with the SubSystem
   verdor ID and SubSystem ID parameters.

6. The driver doesn't print an error when there is no link due to cabale fault.





