Hallo Romain, > By comparing the RTnet driver with Linux 2.6.13.2's driver, I > have found the reason: the module name in the driver (file > rtnet-0.9.0/drivers/experimental/r8169/rt_r8169.c) contains a > slash!
thank you for this information! The RTL8169 driver for RTnet is mainly based on the original driver provided by Realtek, though it seems quite trashy at some places (module name is only one more example for this...) Some parts (eg., xmit function) are based on backporting much of the 2.6.12 kernel code. Nevertheless, the code contained in vanilla 2.6.12+ looks completely re-written; it now even supports VLANs and some other features. But for me it was easier to backport the (more compact) realtek "original" driver. I actually wasn't able to test the driver with fusion; Jan did some changes to at least let it compile. My only tests for now were done with 2.4.27 and RTAI 3.2; I'll make more tests (including fusion) in 1-2 weeks. Please let me know if you experience any problems, so I can update the driver... > I still have to find it the drivers are actually working... When you run "rtnet start", the slave should synchronize with the master, giving an output on the slave like "TDMA calibration: .... 16us" (or similar). Then it should work. You can also seamlessly interact with "normal" FastEthernet cards. Just give it a try. :-) Bye, Klaus ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
