2002-06-03 22:30:51 +00:00
|
|
|
$FreeBSD$
|
|
|
|
FreeBSD* Driver for the Intel(R) PRO/1000 Family of Adapters
|
|
|
|
============================================================
|
|
|
|
|
2006-08-03 09:20:11 +00:00
|
|
|
May 2, 2006
|
2002-06-03 22:30:51 +00:00
|
|
|
|
|
|
|
|
|
|
|
Contents
|
|
|
|
========
|
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
- Overview
|
2005-05-26 23:33:24 +00:00
|
|
|
- Identifying Your Adapter
|
2002-06-03 22:30:51 +00:00
|
|
|
- Building and Installation
|
|
|
|
- Speed and Duplex Configuration
|
|
|
|
- Additional Configurations
|
|
|
|
- Known Limitations
|
|
|
|
- Support
|
|
|
|
- License
|
|
|
|
|
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
Overview
|
|
|
|
========
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
This file describes the FreeBSD* driver for the Intel(R) PRO/1000 Family of
|
2006-08-03 09:20:11 +00:00
|
|
|
Adapters. This driver has been developed for use with FreeBSD, Release 6.x.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
For questions related to hardware requirements, refer to the documentation
|
|
|
|
supplied with your Intel PRO/1000 adapter. All hardware requirements listed
|
2002-06-03 22:30:51 +00:00
|
|
|
apply to use with FreeBSD.
|
|
|
|
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
Identifying Your Adapter
|
|
|
|
========================
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
For information on how to identify your adapter, go to the Adapter &
|
|
|
|
Driver ID Guide at:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
http://support.intel.com/support/network/sb/cs-012904.htm
|
2003-03-21 21:47:31 +00:00
|
|
|
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
For the latest Intel network drivers for FreeBSD, see:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
http://downloadfinder.intel.com/scripts-df-external/support_intel.aspx
|
2002-06-03 22:30:51 +00:00
|
|
|
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
NOTE: Mobile adapters are not fully supported.
|
2006-08-03 09:20:11 +00:00
|
|
|
NOTE: The Intel(R) 82562v 10/100 Network Connection only provides 10/100
|
|
|
|
support.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
|
|
|
Building and Installation
|
|
|
|
=========================
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
NOTE: The driver can be installed as a dynamic loadable kernel module or
|
|
|
|
compiled into the kernel. You must have kernel sources installed in
|
2003-03-21 21:47:31 +00:00
|
|
|
order to compile the driver module.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
In the instructions below, x.x.x is the driver version as indicated in the
|
2003-03-21 21:47:31 +00:00
|
|
|
name of the driver tar file.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
1. Move the base driver tar file to the directory of your choice. For
|
2002-06-03 22:30:51 +00:00
|
|
|
example, use /home/username/em or /usr/local/src/em.
|
|
|
|
|
|
|
|
2. Untar/unzip the archive:
|
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
tar xvfz em-x.x.x.tar.gz
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
This will create an em-x.x.x directory.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
3. To create a loadable module, perform the following steps.
|
2003-03-21 21:47:31 +00:00
|
|
|
NOTE: To compile the driver into the kernel, go directly to step 4.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
a. To compile the module
|
|
|
|
|
|
|
|
cd em-x.x.x
|
|
|
|
make
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
b. To install the compiled module in system directory:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
make install
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
c. If you want the driver to load automatically when the system is booted:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
1. Edit /boot/loader.conf, and add the following line:
|
|
|
|
|
|
|
|
if_em_load="YES"
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
4. To compile the driver into the kernel:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
cd em-x.x.x/src
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
cp if_em* /usr/src/sys/dev/em
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-06-05 17:51:38 +00:00
|
|
|
cp Makefile.kernel /usr/src/sys/modules/em/Makefile
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2006-08-03 09:20:11 +00:00
|
|
|
Edit the /usr/src/sys/conf/files file, and add the following lines only if
|
2005-05-26 23:33:24 +00:00
|
|
|
they don't already exist:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
dev/em/if_em.c optional em
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
dev/em/if_em_hw.c optional em
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2006-08-03 09:20:11 +00:00
|
|
|
Remove the following lines from the /usr/src/sys/conf/files file,
|
2003-03-21 21:47:31 +00:00
|
|
|
if they exist:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
dev/em/if_em_fxhw.c optional em
|
|
|
|
dev/em/if_em_phy.c optional em
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
Edit the kernel configuration file (i.e., GENERIC or MYKERNEL) in
|
2003-03-21 21:47:31 +00:00
|
|
|
/usr/src/sys/i386/conf, and ensure the following line is present:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
device em
|
|
|
|
|
|
|
|
Compile and install the kernel. The system must be rebooted for the kernel
|
2005-05-26 23:33:24 +00:00
|
|
|
updates to take effect. For additional information on compiling the
|
2003-03-21 21:47:31 +00:00
|
|
|
kernel, consult the FreeBSD operating system documentation.
|
|
|
|
|
|
|
|
5. To assign an IP address to the interface, enter the following:
|
|
|
|
|
|
|
|
ifconfig em<interface_num> <IP_address>
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
6. Verify that the interface works. Enter the following, where <IP_address>
|
|
|
|
is the IP address for another machine on the same subnet as the interface
|
|
|
|
that is being tested:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
ping <IP_address>
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
7. To configure the IP address to remain after reboot, edit /etc/rc.conf,
|
|
|
|
and create the appropriate ifconfig_em<interface_num>entry:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
ifconfig_em<interface_num>="<ifconfig_settings>"
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
Example usage:
|
|
|
|
|
|
|
|
ifconfig_em0="inet 192.168.10.1 netmask 255.255.255.0"
|
|
|
|
|
|
|
|
NOTE: For assistance, see the ifconfig man page.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
|
|
|
|
|
|
|
Speed and Duplex Configuration
|
|
|
|
==============================
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
By default, the adapter auto-negotiates the speed and duplex of the
|
|
|
|
connection. If there is a specific need, the ifconfig utility can be used to
|
2002-06-03 22:30:51 +00:00
|
|
|
configure the speed and duplex settings on the adapter. Example usage:
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
ifconfig em<interface_num> <IP_address> media 100baseTX mediaopt
|
2002-06-03 22:30:51 +00:00
|
|
|
full-duplex
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
NOTE: Only use mediaopt to set the driver to full-duplex. If mediaopt is
|
|
|
|
not specified and you are not running at gigabit speed, the driver
|
2002-06-03 22:30:51 +00:00
|
|
|
defaults to half-duplex.
|
|
|
|
|
|
|
|
|
|
|
|
This driver supports the following media type options:
|
|
|
|
|
|
|
|
autoselect - Enables auto-negotiation for speed and duplex.
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
10baseT/UTP - Sets speed to 10 Mbps. Use the ifconfig mediaopt
|
2002-06-03 22:30:51 +00:00
|
|
|
option to select full-duplex mode.
|
|
|
|
|
|
|
|
100baseTX - Sets speed to 100 Mbps. Use the ifconfig mediaopt
|
|
|
|
option to select full-duplex mode.
|
|
|
|
|
|
|
|
1000baseTX - Sets speed to 1000 Mbps. In this case, the driver
|
|
|
|
supports only full-duplex mode.
|
|
|
|
|
|
|
|
1000baseSX - Sets speed to 1000 Mbps. In this case, the driver
|
|
|
|
supports only full-duplex mode.
|
|
|
|
|
|
|
|
For more information on the ifconfig utility, see the ifconfig man page.
|
|
|
|
|
|
|
|
|
|
|
|
Additional Configurations
|
|
|
|
=========================
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
The driver supports Transmit/Receive Checksum Offload and Jumbo Frames on
|
2006-04-06 17:09:03 +00:00
|
|
|
all but the 82542-based adapters. For specific adapters, refer to the
|
2005-05-26 23:33:24 +00:00
|
|
|
Identifying Your Adapter section.
|
2003-03-21 21:47:31 +00:00
|
|
|
|
2002-06-03 22:30:51 +00:00
|
|
|
Jumbo Frames
|
|
|
|
------------
|
2006-04-06 17:09:03 +00:00
|
|
|
To enable Jumbo Frames, use the ifconfig utility to set the Maximum
|
|
|
|
Transport Unit (MTU) frame size above its default of 1500 bytes.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
The Jumbo Frames MTU range for Intel Adapters is 1500 to 16110. To modify
|
|
|
|
the setting, enter the following:
|
2003-03-21 21:47:31 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
ifconfig em<interface_num> <hostname or IP address> mtu 9000
|
2005-05-26 23:33:24 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
To confirm the MTU used between two specific devices, use:
|
2005-05-26 23:33:24 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
route get <destination_IP_address>
|
2005-05-26 23:33:24 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
Notes:
|
2003-03-21 21:47:31 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
- Only enable Jumbo Frames if your network infrastructure supports them.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
- To enable Jumbo Frames, increase the MTU size on the interface beyond
|
|
|
|
1500.
|
|
|
|
|
|
|
|
- The Jumbo Frames setting on the switch must be set to at least 22 bytes
|
|
|
|
larger than that of the MTU.
|
|
|
|
|
|
|
|
- The maximum MTU setting for Jumbo Frames is 16110. This value coincides
|
|
|
|
with the maximum Jumbo Frames size of 16128.
|
|
|
|
|
|
|
|
- Some Intel gigabit adapters that support Jumbo Frames have a frame size
|
|
|
|
limit of 9238 bytes, with a corresponding MTU size limit of 9216 bytes.
|
|
|
|
The adapters with this limitation are based on the Intel(R) 82571EB,
|
|
|
|
82572EI, 82573L and 80003ES2LAN controller. These correspond to the
|
|
|
|
following product names:
|
|
|
|
Intel(R) PRO/1000 PT Server Adapter
|
|
|
|
Intel(R) PRO/1000 PT Desktop Adapter
|
|
|
|
Intel(R) PRO/1000 PT Network Connection
|
|
|
|
Intel(R) PRO/1000 PT Dual Port Server Adapter
|
|
|
|
Intel(R) PRO/1000 PT Dual Port Network Connection
|
|
|
|
Intel(R) PRO/1000 PF Server Adapter
|
|
|
|
Intel(R) PRO/1000 PF Network Connection
|
|
|
|
Intel(R) PRO/1000 PF Dual Port Server Adapter
|
|
|
|
Intel(R) PRO/1000 PB Server Connection
|
|
|
|
Intel(R) PRO/1000 PL Network Connection
|
|
|
|
Intel(R) PRO/1000 EB Network Connection with I/O Acceleration
|
|
|
|
Intel(R) PRO/1000 EB Backplane Connection with I/O Acceleration
|
|
|
|
|
|
|
|
- Adapters based on the Intel(R) 82542 and 82573V/E controller do not
|
|
|
|
support Jumbo Frames. These correspond to the following product names:
|
|
|
|
Intel(R) PRO/1000 Gigabit Server Adapter
|
|
|
|
Intel(R) PRO/1000 PM Network Connection
|
|
|
|
|
|
|
|
- Using Jumbo Frames at 10 or 100 Mbps may result in poor performance or
|
|
|
|
loss of link.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2006-08-03 09:20:11 +00:00
|
|
|
- The following adapters do not support Jumbo Frames:
|
|
|
|
Intel(R) 82562V 10/100 Network Connection
|
|
|
|
Intel(R) 82566DM Gigabit Network Connection
|
|
|
|
Intel(R) 82566DC Gigabit Network Connection
|
|
|
|
Intel(R) 82566MM Gigabit Network Connection
|
|
|
|
Intel(R) 82566MC Gigabit Network Connection
|
|
|
|
|
2002-06-03 22:30:51 +00:00
|
|
|
|
|
|
|
VLANs
|
|
|
|
-----
|
2005-05-26 23:33:24 +00:00
|
|
|
To create a new VLAN interface:
|
2003-03-21 21:47:31 +00:00
|
|
|
|
|
|
|
ifconfig <vlan_name> create
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
To associate the VLAN interface with a physical interface and
|
2003-03-21 21:47:31 +00:00
|
|
|
assign a VLAN ID, IP address, and netmask:
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
ifconfig <vlan_name> <ip_address> netmask <subnet_mask> vlan
|
2003-03-21 21:47:31 +00:00
|
|
|
<vlan_id> vlandev <physical_interface>
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
ifconfig vlan10 10.0.0.1 netmask 255.255.255.0 vlan10 vlandev em0
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
In this example, all packets will be marked on egress with 802.1Q VLAN
|
2003-03-21 21:47:31 +00:00
|
|
|
tags, specifying a VLAN ID of 10.
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
To remove a VLAN interface:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
ifconfig <vlan_name> destroy
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
Polling
|
|
|
|
-------
|
2005-05-26 23:33:24 +00:00
|
|
|
To enable polling in the driver, add the following options to the kernel
|
2003-03-21 21:47:31 +00:00
|
|
|
configuration, and then recompile the kernel:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2003-03-21 21:47:31 +00:00
|
|
|
options DEVICE_POLLING
|
|
|
|
options HZ=1000
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
At runtime use:
|
2006-04-06 17:09:03 +00:00
|
|
|
ifconfig em0 polling to turn polling on
|
2005-05-26 23:33:24 +00:00
|
|
|
Use:
|
2006-04-06 17:09:03 +00:00
|
|
|
ifconfig em0 -polling to turn polling off
|
|
|
|
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
Checksum Offload
|
|
|
|
----------------
|
|
|
|
Checksum offloading is not supported on 82542 Gigabit adapters.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
Checksum offloading supports both TCP and UDP packets and is
|
|
|
|
supported for both transmit and receive.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
Checksum offloading can be enabled or disabled using ifconfig.
|
|
|
|
Both transmit and receive offloading will be either enabled or
|
|
|
|
disabled together. You cannot enable/disable one without the other.
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
To enable checksum offloading:
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
ifconfig <interface_num> rxcsum
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
To disable checksum offloading:
|
2003-08-27 21:52:37 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
ifconfig <interface_num> -rxcsum
|
2003-08-27 21:52:37 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
To confirm the current setting:
|
2003-08-27 21:52:37 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
ifconfig <interface_num>
|
2003-08-27 21:52:37 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
Look for the presence or absence of the following line:
|
|
|
|
|
|
|
|
options=3 <RXCSUM,TXCSUM>
|
|
|
|
|
|
|
|
See the ifconfig man page for further information.
|
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
Known Limitations
|
|
|
|
=================
|
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
In FreeBSD version 4.x with Symmetric MultiProcessing (SMP), there is a known
|
|
|
|
issue on some newer hardware. The problem is generic kernel and only in SMP
|
|
|
|
mode. The workaround is to either use FreeBSD version 4.x in single processor
|
|
|
|
mode, or use FreeBSD 5.4 or later.
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
There are known performance issues with this driver when running UDP traffic
|
|
|
|
with Jumbo Frames.
|
|
|
|
|
|
|
|
There is a known compatibility issue where time to link is slow or link is not
|
|
|
|
established between 82541/82547 controllers and some switches. Known switches
|
|
|
|
include:
|
2003-08-27 21:52:37 +00:00
|
|
|
Planex FXG-08TE
|
|
|
|
I-O Data ETG-SH8
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
The driver can be compiled with the following changes:
|
2003-08-27 21:52:37 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
Edit ./em.x.x.x/src/if_em.h to uncomment the #define EM_MASTER_SLAVE
|
|
|
|
from within the comments. For example, change from:
|
2003-08-27 21:52:37 +00:00
|
|
|
|
|
|
|
/* #define EM_MASTER_SLAVE 2 */
|
2005-05-26 23:33:24 +00:00
|
|
|
to:
|
|
|
|
#define EM_MASTER_SLAVE 2
|
2003-08-27 21:52:37 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
Use one of the following options:
|
2003-08-27 21:52:37 +00:00
|
|
|
1 = Master mode
|
|
|
|
2 = Slave mode
|
|
|
|
3 = Auto master/slave
|
2005-05-26 23:33:24 +00:00
|
|
|
Setting 2 is recommended.
|
2003-08-27 21:52:37 +00:00
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
Recompile the module:
|
|
|
|
a. To compile the module
|
|
|
|
cd em-x.x.x
|
|
|
|
make clean
|
|
|
|
make
|
2003-08-27 21:52:37 +00:00
|
|
|
|
|
|
|
b. To install the compiled module in system directory:
|
2005-05-26 23:33:24 +00:00
|
|
|
make install
|
2002-06-03 22:30:51 +00:00
|
|
|
|
|
|
|
|
|
|
|
Support
|
|
|
|
=======
|
|
|
|
|
|
|
|
For general information and support, go to the Intel support website at:
|
|
|
|
|
|
|
|
http://support.intel.com
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
If an issue is identified, support is through email only at:
|
|
|
|
freebsdnic@mailbox.intel.com
|
2002-06-03 22:30:51 +00:00
|
|
|
|
2006-04-06 17:09:03 +00:00
|
|
|
|
2002-06-03 22:30:51 +00:00
|
|
|
License
|
|
|
|
=======
|
|
|
|
|
2005-05-26 23:33:24 +00:00
|
|
|
This software program is released under the terms of a license agreement
|
|
|
|
between you ('Licensee') and Intel. Do not use or load this software or any
|
|
|
|
associated materials (collectively, the 'Software') until you have carefully
|
|
|
|
read the full terms and conditions of the LICENSE located in this software
|
|
|
|
package. By loading or using the Software, you agree to the terms of this
|
|
|
|
Agreement. If you do not agree with the terms of this Agreement, do not
|
2002-06-03 22:30:51 +00:00
|
|
|
install or use the Software.
|
|
|
|
|
|
|
|
* Other names and brands may be claimed as the property of others.
|