TSUG_REL.TXT Driver File Contents (FASTLine.zip)

			  Release Notes for
	    Intel 21x4x based 10/100 Mbps Ethernet Controller Driver
   		 SCO Unix UnixWare7 Driver - Version 4.3.0



Legal Notice:

These Release Notes as well as the software described in it is 
furnished under license and may only be used or copied in accordance with
the terms of the license. The information in this manual is furnished for 
informational use only, is subject to change without notice, and should not
be construed as a commitment by Intel Corporation. Intel Corporation assumes
no responsibility or liability for any errors or inaccuracies that may
appear in this document or any software that may be provided in association
with this document. 
Except as permitted by such license, no part of this document may be
reproduced, stored in a retrieval system, or transmitted in any form or by
any means without the express written consent of Intel Corporation.

New Fetures in version 4.3.0:

- The default media type is now read from the SROM. This allows the board
  designer to choose the best media option for the specific board.

- Moved the setting of the medium type from the space.c file into the GUI netcfg
  utility. A user can now change the medium type without relinking the kernel.
  See the installation guide for instructions on avoiding the need to reboot

- Driver complies with SCO's new failover spec. *.bcfg files were changed to
  reflect this fact.

- Fixed the permissions in the installable package. The shared directories are
  now given the default permissions set by the initial OS installation instead
  of becoming read-only.

- The installable driver package is now distributed in a single installable
  (datastream) file. This saves the need to 'untar' the directory tree before
  installation. (see the installation guide).

- Node and Drvmap configuration files were fixed. Node file now lists uid/gid
  instead of names. Drvmap no longer points to non existent *.bcfg files. (These
  should both be transparent to users).

- Fixed the loopback function during promiscuous mode.

- When hardware problems are detected during the open() routine, driver no
  longer panics the kernel. Panic used to occur while trying to send
  MAC_HWFAIL_IND messages during the open() routine (i.e. before a queue is
  initialized/bound). Hardware problems continue to be properly reported by
  returning an error code from the open() routine.

- All messages and documentation were ported from Digital Semiconductor to


Versions 4.2.2 and 4.2.1

The two versions are almost identical.

4.2.1 is undergoing a certification process and will be fully supported by SCO.
It will be placed on SCO's official FTP site and included in future releases of
the UnixWare 7 operating system.

- 4.2.2 only: Fixed a bug which prevented the recognition of supported adapters
  in the presence of other, non 21x4x Ethernet PCI controllers. The driver
  stopped looking for supported adapters byond other Ethernet PCI adapters.
  A simple user workaround for version 4.2.1 is to place the supported adapters
  in lower slots than the others.

- 4.2.1 is the first externally released version for the coming UnixWare 7 OS. 

Ancient History:

Versions prior to 4.2.1 are engineering versions not intended for public use.
Therefore they are not covered here.

Known Limitations:

-  Version 4.2.1 only: The driver does not find supported adapters which are put
   in PCI slots higher than non 21x4x based Ethernet PCI adapters. It stopps
   looking for supported adapters once it encounteres other Ethernet PCI
   adapters based on non 21x4x controllers.
   A simple user workaround is to place the supported adapters in lower slots
   than the others.

-  The driver supports up to 4 controllers simultaneously.

   A sophisticated user may add more adapters by changing the XXX_MAX_BOARDS
   macro in the space.c file and duplicating the initialization of data objects
   such as the items of XXX_info which, as supplied, only deal with 4 items.
   Users doing so are taking full responsibility for their actions. It was not
   tested. Any party involved in the driver or adapter will not be held

-  Printing of messages related to link failure and establishment is currently

-  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 does not support changing any parameters through the "modify ..."
   menu item of the netcfg utility.

-  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

-  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.

Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web5, load: 0.85