REDD-0.4: Lots of changes!!

Hi, all.

I've just released the 0.4 version of REDD (RTLinux Ethernet Device Drivers). 
- New features added 
- Structural changes that ease the work of developing a new driver.
- Structural changes that ease the work of developing protocols (or code over 
REDD) using REDD
Read the changelog below.

Project description:
---------------------------------------------------------------------------------------
REDD is an Open Source project consisting on a set of Ethernet card drivers 
for RTLinux-GPL. This drivers provide the standard POSIX API (open, close, 
read,  write  and  ioctl  calls)  and can be accessed by RT-tasks to send and 
receive messages through an Ethernet network.

Changelog:
---------------------------------------------------------------------------------------
The REDD-0.4 distribution differs from the 0.3 distribution in:

  - A file   gathering together  all  the  tunable  options has   been
  developed (reddopts.h).
  - The O_NONBLOCK (nonblocking) mode has been added to the drivers.
  - By default the ZERO COPY is  used when interfacing the driver with
  the read  call, but one can choose  the standard working mode of the
  read call in the reddopts.h file  (added the read's standard working
  mode).
  - An option to  decide if the driver  receives all the broadcasts in
  the network  or only those addressed  to  him has been added  in the
  reddopts.h file.
  -  The RTLinux code needed to   develop a new  REDD  driver has been
  gathered  together  in the  file src/include/drivers/rtl_posix_if.h.
  This simplifies   a lot the work   of  developing a new   driver and
  standarizes the functions and   variables that the  RTLinux  drivers
  must provide (or use).
  - A  new mechanism  that allows  you  to substitute the  open, read,
  write,  close and  ioctl (hereafter the  POSIX  calls) with your own
  calls  without modifying the driver's code  has been provided.  This
  mechanism       is        provided      in             the      file
  src/include/posix_fake/rtl_posixio_fake.h.    That file allows  your
  code to get a pointer to each  of the POSIX calls functions declared
  in  the driver and use them  (if you want)   inside your calls (that
  will  substitute  the driver's ones).   This allows you  to add code
  before and after the POSIX  calls transparently (the final user will
  call read, write,  etc..  in the   same way, but  your  code will be
  executed instead of the drivers one), being  a powerful mechanism to
  develop protocols that use  this  drivers  (for example, a real-time
  protocol over Ethernet).

REDD home page:
---------------------------------------------------------------------------------------
http://redd.sourceforge.net

Please send comments to Sergio Perez <[email protected]>

Best regards.

Sergio.
_______________________________________________
Rtl mailing list
[email protected]
http://www2.fsmlabs.com/mailman/listinfo/rtl