RELEASE_NOTES

Enea LINX for Linux

Version: 1.1.3, March 27, 2007

This is an updated release of Enea LINX for Linux open source
package, containing the LINX kernel module, the LINX library and tools
for supervising and for configuring inter-node communication. The
focus of this release is added support for SMP and 64-bit targets.

Supported Linux kernel versions

LINX for Linux version 1.1.3 supports Linux kernel 2.6.9 to 2.6.20.

This release has been tested on the following platforms:
* Linux kernel 2.6.20-1.2925.fc6 in Fedore Core FC6 x86 SMP
* Linux kernel 2.6.19-1.2911.fc6 in Fedora Core FC6 x86 SMP
* Linux kernel 2.6.18-1.2868.fc6 in Fedore Core FC6 x86 SMP
* Linux kernel 2.6.17 in the Gentoo r7 distribution for Pentium III
  and IV targets.
* Linux kernel 2.6.16 in the Gentoo r7 distribution for Pentium III
  and IV targets.
* Linux kernel 2.6.15 in the DENX for Walnut (PPC)
* Linux kernel 2.6.11 in Fedora Core FC4 on x86_64 SMP Pentium Xeon
* Linux kernel 2.6.9 in Red Hat Enterprise Linux WS on x86_64 SMP
  Pentium Xeon


LINX Development environment requirements

LINX doesn't use any unusual features and should be easy to build in
any modern self hosted or cross build environment.


LINX Known Bugs and Incomplete Features

The following are known limitations and bugs in this release:

* LINX doesn't support multiple links between two targets.

* If the LINX kernel module fails to send attach-, hunt- or supervision
  signals (the sockets sndbuf and/or rcvbuf is exhausted) the LINX kernel
  module calls kernel panic.

* Successful send on a LINX socket returns at least 64 bytes, even if fewer
  bytes were actual transmitted.

* Make system lacks proper dependencies.

* Poor performance if last packet is lost.

* LINX doesn't have a proper, reserved at IEEE, Ethernet type.

* Coalescing is experimental.

* LINX_INFO_SIGNAL_PAYLOAD is not supported from a 32-bit binary when
  running on a 64-bit Linux kernel.

* For some kernel versions and distributions LINX must be built with
  LINX_KERNEL_WORKAROUND_1, see README.

LINXDISC Limitations

* If the linxdisc daemon is killed with SIGKILL it cannot be restarted
  due to lack of cleanup, but if the user removes the lockfile and
  established LINX-connections, the daemon may be started again.

[END OF DOCUMENT]