--- a/INSTALL Fri Feb 01 21:22:22 2008 +0000
+++ b/INSTALL Fri Feb 01 21:34:35 2008 +0000
@@ -9,14 +9,12 @@
Building and installing
=======================
-The building and installation procedure is described in section 2.1 in the
-EtherCAT master documentation available from http://etherlab.org/ethercat.
+The build and installation procedure is described in section 2.1 in the
+documentation available from http://etherlab.org/en/ethercat.
-------------------------------------------------------------------------------
-For the impatient:
-
-The procedure mainly consists of calling
+For the impatient: The procedure mainly consists of calling
$ ./configure
$ make modules
@@ -26,7 +24,7 @@
# make install
# make modules_install
-...and copying the init script and sysconfig file from $prefix/etc to the
+...and copying the init script and sysconfig file from $PREFIX/etc to the
appropriate locations and customizing the sysconfig file.
-------------------------------------------------------------------------------
--- a/README Fri Feb 01 21:22:22 2008 +0000
+++ b/README Fri Feb 01 21:34:35 2008 +0000
@@ -16,10 +16,10 @@
1) General Information
======================
-This is an Open-Source EtherCAT master implementation for Linux 2.6.
+This is an open-source EtherCAT master implementation for Linux 2.6.
See the FEATURES file for a list of features. For more information, see
-http://etherlab.org/ethercat.
+http://etherlab.org/en/ethercat.
or contact
@@ -41,9 +41,9 @@
2) Hardware requirements
-The EtherCAT master needs a RTL8139 (or compatible) network interface card to
-run. Drivers for other widespread devices (i. e. Intel PRO/100) will be
-implemented soon.
+The EtherCAT master needs a RTL8139 (or compatible), Intel PRO/1000 or nVidia
+nForce network interface card to run. Drivers for other widespread devices (f.
+e. Intel PRO/100) will be implemented soon.
-------------------------------------------------------------------------------
@@ -59,8 +59,8 @@
Realtime patches for the Linux kernel are supported, but not required. The
realtime processing has to be done by the calling module (see API
-documentation). The EtherCAT master code itself is completely passive (except
-for the idle mode).
+documentation). The EtherCAT master code itself is passive (except for the idle
+mode and EoE).
To avoid frame timeouts, deactivating DMA access for hard drives is
recommented (hdparm -d0 <DEV>).
--- a/README.EoE Fri Feb 01 21:22:22 2008 +0000
+++ b/README.EoE Fri Feb 01 21:34:35 2008 +0000
@@ -6,9 +6,10 @@
environment with Ethernet-over-EtherCAT devices.
A virtual network interface will appear for every EoE-capable slave. The
-interface naming scheme is eoeXsY, where X is the master index and Y is the
-slave's ring position. Please provide a network configuration file for any of
-these interfaces. On SUSE systems, these can look like the following:
+interface naming scheme is either eoeXsY, where X is the master index and Y is
+the slave's ring position, or (if the slave has an alias set) eoeXaZ, where Z
+is the (decimal) alias address. Please provide a network configuration file for
+any of these interfaces. On SUSE systems, these can look like the following:
/etc/sysconfig/network/ifcfg-eoe0s14:
IPADDRESS=10.0.0.14/8
--- a/TODO Fri Feb 01 21:22:22 2008 +0000
+++ b/TODO Fri Feb 01 21:34:35 2008 +0000
@@ -22,6 +22,7 @@
* Remove ecdb.h and let lsec output PDO information 'cut-and-pastable' for
applications.
* Update documentation.
+* Create table of supported network devices and add link inside README.
Future issues: