1. xavi.zip Driver
2. readme.txt File Contents

readme.txt Driver File Contents (xavi.zip)

GlobespanVirata Linux Driver for Viking version 1.4 boards 
-----------------------------------------------------------

Introduction
-------------
  This file describes the Linux LAN driver for the GlobespanVirata Viking
Atlas 
  ELD version 1.4 boards

  The Linux kernel 2.4.19 onwards include the sources of driver for CDC
  Ethernet networking control model compliant devices. The driver being
  provided by GlobespanVirata is modified from the above said sources 
  available with Linux kernel 2.4.19.

  This driver supports Linux-2.4 kernel. The Linux kernel sources can be
download from:
    http://www.kernel.org/pub/linux/kernel/v2.4/

  Customer needs to have kernel source to compile the GlobespanVirata drivers.
  The installed system should already have the kernel sources
  installed in the /usr/src/linux directory. If they are not there,
  try to get them off the installation disks for your distribution,
  or download the latest Linux-2.4 kernel , and configure and
  build that. There are lots of books and documents available
  describing how to extract, configure and build the kernel from
  it's sources...

  After untarring the linux kernel source to /usr/src/linux, go to
/usr/src/linux directory
    and perform following commands.

    - make menuconfig
    - make clean
    - make dep

History
--------
  v1.0.0E (05/05/2003)
    - Initial release of driver with support for Linux-2.4 kernel.
  v1.0.1E (14/05/2003)
    - Fixed bug for VTAen25934 and Enhancement for VTAen25935. 
      For details see Release note.


Package Information
--------------------
Everything shown below is a directory. "+" means directory is NOT expanded and
"-" means directory is expanded.

   - viking       /* Main directory                   */
     |
     + inc          /* Driver header files              */
     |
     + src          /* Directory containing the sources */

Compiling the Driver
---------------------
To compile the driver simply run make in "viking" directory. This will create
binary
driver with name VKGEther.

    % make

Loading the module
-------------------
To load the VKGEther module enter the following command as root in directory
"viking"
  Syntax:
   % insmod ./VKGEther {Module Options}

    Module Options
    --------------
    multicast_filter_limit      default: 32767
	quick_sync_count			default: 20

The module option quick_sync_count can be useful at startup time. The
driver drops all packets which arrive out of sequence from the Viking board.
As soon as driver's synchronization counter matches that of the Viking as
received in the packets the driver starts forwarding the packets over to the
network interface. Sometimes this process of getting into sync with Viking
board may take unusually long times. To bring this time down user can set the
module parameter "quick_sync_count" to the maximum number of packets which can
be dropped before driver resets its own synchronization counter to match the
counter received in packets from Viking board. This helps in quickly bringing 
the network interface to operational status.

When using the module with the kernel module autoloader, the module can
be loaded on demand when the device is referenced. The driver need to be
copied to /lib/modules/2.4.x/kernel/drivers/usb directory. 2.4.x in previous
line refers to the kernel version. Kernel version can be found using command
'uname -a'. In addition to the demand loading specification, module parameters
can also be specified in the file /etc/modules.conf as follows:

    alias eth? VKGEther

The ? in above line will depend on the number of ethernet interface
corresponding to the Viking device. A new file (ifcfg-eth?) needs
to be added to /etc/sysconfig/network-scripts. The contents of this
file will be somewhat as given below

DEVICE=eth?
BOOTPROTO=static
BROADCAST=192.168.255.255
IPADDR=192.168.1.200
NETMASK=255.255.0.0
NETWORK=192.168.0.0
ONBOOT=yes


Unloading the module
---------------------
  To unload an unused module:
    % rmmod VKGEther

  You will need to exit or disconnect any program currently using the module
  before it will unload. If the module was configured for LAN, shutdown
  the ethernet interface:
    % ifconfig eth1 down

  The ethernet interface associated with the VKGEther driver was "eth1" that's
  why interface name is eth1 in above line.

LAN Configuration
------------------
  To enable LAN traffic over the ethernet interface:
    % ifconfig eth1 192.168.1.200 up

  You may also need to modify the netmask and route for the interface.
  Refer to the manual pages for ifconfig and route for more information.

  To test the LAN connection is alive by pinging the remote side:
    % ping 192.168.1.1

  To disconnect the LAN inteface:
    % ifconfig eth1 down

Things to note
--------------
  * New version of modutils (version 2.3.18 or later) required. Sources
    for the module utilities can be downloaded from:
      ftp://ftp.kernel.org/pub/linux/utils/kernel/modutils/v2.3/

  * Updates are required to RedHat distributions to support Linux-2.4
    including the latest RedHat 7.0 distribution. Check on the RedHat
    site (http://www.redhat.com) for information on upgrading to the
    Linux-2.4 kernel.