The final version of the 0.8-series of RTnet has just been released. It
comes with some updates to keep up with the development of the kernel
and RTAI/fusion. Here is the full list of changes:
* added support for fusion 0.8.0..0.8.3
* added experimental MPC 52xxx FEC driver
* enabled kernel 2.6.12 compilation
* revised locking in critical sections of rt_8139too and rt_via-rhine
* implemented hash chains for layer 2 protocol management
(avoids protocol handler rejection on hashkey collision)
* extended RTmac to let discipline switch off VNIC support or override
xmit handler
* fixed handling of zero-sized stage 2 files in RTcfg
* fixed cleanup bug in RTcfg
* fixed rtnet.conf to let rt-driver grab only one NIC by default
(again)
We are now able to head for 0.9. That version will bring some
significant internal changes which will be visible on the surface as
well. First of all, the core will be ported over the new Real-Time
Driver Model which is now official part of RTAI/fusion (will show up in
fusion 0.9). This step will break the built-in RTDM layer which also
worked with RTAI/classic. The consequences are:
1. We need some volunteer(s) willing to port RTDM over the classic
series and maintain RTnet in this respect. Otherwise, support for
RTAI 3.x in RTnet (including kernel 2.4 support) will remain broken
from 0.9 upward!
Porting RTDM should definitely be feasible, especially as more than
half of the work is already there: the old RTDM layer and the RTOS
abstraction layer in RTnet. Both parts "only" requires updating
according to the changes made in RTDM while being merged into fusion.
An even better solution would be a native RTDM layer in RTAI/classic,
but this depends even more on the RTAI community. The RTnet core
team, especially here at the RTS, has to concentrate its limited
resources on RTAI/fusion these days and cannot provide full support
for RTAI/classic without additional help anymore.
2. Support for RTAI-24.1.x will definitely be cancelled with the next
RTnet release - ok, as long as no one else takes over the required
work. But I'm convinced that this is no productive labour anymore.
Besides the RTDM port, 0.9 will undergo a lot of internal cleanup to
remove old TDMA-V1 and to make it even more modular. The 0.9 series is
then intended to finally drive RTnet to its 1.0 release - the ultimate
goal of every "younger" Open Source project! ;)
Jan
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users
