1. 9999999999_116.zip Driver
2. TSUM_REL.TXT File Contents

TSUM_REL.TXT Driver File Contents (9999999999_116.zip)

			  Release Notes for
	Digital Semiconductor 2104x/2114x 10/100 mbps Ethernet Controller
   		   SCO Unix MDI Driver - Version 4.2.2

			      (SUM422T)

			      13-Mar-98




New Fetures:
============

Versions 4.2.2 and 4.2.0 (changes since 3.3.5)
----------------------------------------------

Versions 4.2.2 and 4.2.0 are almost identical.
The major version number is now 4 to keep the same number as the newely
introduced driver for UnixWare 7.

4.2.0 was tested and certified by SCO. It is fully supported by SCO and included
in the next release of OpenServer 5.

- 4.2.2 only: The user may now choose the default media type globally by setting
  the XXX_DC21X4_SERIAL_MODE macro in the space.c file. This manual setting will
  not show in the "modify hardware settings"->"advanced options" dialog which
  relates to a single adapter at a time and, thus, overriding the global
  default.  (In earlier versions XXX_DC21X4_SERIAL_MODE was ignored).

- Enhanced support for multiple adapters of different 21x4x chip types.

- Added support for the newest member of the 21143 adapter family.

- Added support for more SROM chip types including bigger 4Kbit chips.

- Fixed a bug in the MII reset sequence which prevented some adapter designs
  from working.

- Fixed a bug sometimes causing a kernel panic when packets are received with
  an unknown destination address.

- All needed symbols are now scrambled to have the driver's prefix. This makes
  the driver "symbol proof".

- IRQ binding to driver instance now supports APIC chips which have more IRQ
  lines available.

- Fixed a bug in TX statistics collection while in full duplex modes.

- Added suport for more motherboards having trouble supporting a few PCI bus
  transfere modes.

- Fixed the media type printed by printcfg in cases where autosensing doesn't
  finish by the time we call printcfg. The media "Auto" is displayed.

- Added dynamic link state indication for chips and media which support link
  state interrupts.

- Code changes are documented in a separate programmers' notes which are part
  of the source kit.




History:
========

Last 3.X.X version was 3.3.5.




Known Limitations:
==================

-  When the netconfig utility searches for known boards, it may suggest a list
   of a few drivers supporting various 21x4x controller based adapters or none
   at all. Most OpenServer versions use the PCI Sub-Vendor ID to match the
   driver which recignizes that Sub-Vendor ID. However ther a few cases when
   this doesn't work:

   Cases for showing a list of drivers for a given adapter:
   - Some adapters don't have a PCI Sub-Vendor ID burnt into them.
   - Not all BIOSes support the PCI spec version which defines the Sub-Vendor ID
     field.
   A user should manually choose the driver which looks best suited fo the
   adapter.

   Cases for not showing any drivers for a given adapter:
   - Adapters which do have a PCI Sub-Vendor ID burnt into them but don't have
     one listed for any driver.
   - Some versions of OpenServer have a bug dealing with the Sub-Vendor ID
     field. This was fixed in newer versions of OpenServer and there are also
     patches available from SCO, included in some AHS floppies.
   The user should manually choose the proper driver form the list of all
   supported drivers and fill in the missing information. To get this
   information we sugget the use of the following command form a shell command
   prompt (please copy the reversed quotes as is and dont add spaces):

     `llipathmap`/bin/pcislot

-  The driver supports up to 4 controllers simultaneously.

-  The driver support only boards that their SROM was programmed in the
   format of version 1.0, 3.X or 4.X and the boards that their SROM
   was programmed in the classic version (32 bytes of Ethernet address
   and checksum) for DS21140 boards only.

-  The driver doesn't support changing parameters at boot time.

-  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 received packet after SW/HW reset.
   This cause the ANT tests to fail (the tests get out of sync).

-  When testing EB142/3 with National PHY, under IPX test in TP mode
   the test fails due to loss of carrier - this is under investigation.

-  The driver supports only boards with a single MII PHY.

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

-  In cases of boards with MII PHY, the driver performs the autosense algorithm
   on MII PHY media only.

-  In cases of boards with DS21142/3 without MII PHY, the driver performs thes
   SIA's power-up autosense algorithm and not the SIA's dynamic autosense
   algorithm.

-  In case of boards with 21143 and SYM Phy, when the driver is in
   AUTOSENSE/Nway mode, the Nway Algorithm will not detect 100Mb/sec link
   until any Protocol was started (and an Open command issued to driver).

-  The DS21143 + QSI 6611 SYM Phy was run in the ANT testing only in Force Media
   (TP or 100-TX) not in Nway.

-  The Driver supports enabling of Extended PCI commands, (the commands new as
   of PCI spec 2.1), for those 2104x/2114x devices which support the commands.
   As a default, the driver will enable the maximum possible number of
   the three Extended PCI Commands,
   	 Memory Write Invalidate (MWI);
	 Memory Read Line (MRL);
	 Memory Read Multiple (MRM);
   after verifying that the system implementation (PCI bridge chipset
   and BIOS) supports it.

   The devices for which the commands will be enabled:
	 21140A rev >= 21 ,
   	 21143 rev >= 20.

   Due to incompatibility problems with certain PCI host bridges
   and PCI-to-PCI bridges, the driver currently does not enable
   the Memory Write Invalidate (MWI) and Memory Read Line (MRL) commands
   simultaneously. The driver will only enable one of the two commands;
   by default, MRL will be enabled.

-  A few of Award's Multi Processor BIOS versions (3.0x) have a known problem
   constructing the MP interrupt routing tables. This problem exists for all
   PCI/ISA/EISA adapters with SCO's operating systems, ours included.