RTnet uses a network driver model which is very
similar to Linux. Our
Ethernet drivers are all ported from standard Linux.
Take a look at
README.drvporting (rtnet/Documentation) to get an
impression of what
steps have to be performed.
I looked it, and it doesn't seem too difficult.
That sounds very good!
Furthermore, as FDDI would be a new media type, some
internal extensions
of RTnet would probably be required - it's a bit
difficult to say how
much work this would cause, but it should be
feasible (most parts of
RTnet are already prepared for new media types).
How can I do (what documentation must i read) to
discover what extensions must I write on RTnet? What part of the code is related to the media type??
Hey, this is getting more and more interesting! I think it might be a good time to move the further detail discussion to the RTnet list (see CC).
I don't have a detailed image yet about what has to be changed/extended. But if you are going to port FDDI to RTnet, you will get the full support of our team to create a smart integration.
So let's think a bit about it: We should start with the additional driver layer functions. Everything in ethernet/ will probably be replaced by something FDDI related. Then check what further unknown calls, structures, or defines your driver use. The first milestone should be to make the driver compile with RTnet (Marc may help with the build system if required). This step will also cover the device management (driver structure etc.).
Then we should check the packet socket support if it is able to handle unknown media. This would avoid to adapt the whole UDP/IP stuff immediately. But with packet sockets you would already have a full featured API to send and receive any FDDI payload you like to.
[just read your second mail]
I see, UDP is wanted (doesn't the other box support something like packet sockets?). This requires a bit more work (foremost routing), but when it is done, the RTnet UDP/IP output on FDDI will look like any other system's IP packet (this already applies to Ethernet).
You are right that media access control is not needed on a point-to-point link - as long as there is no prioritised traffic like real-time and non-real-time on the same line. However, media access control would probably need a deeper look first with FDDI.
Jan
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ RTnet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-users
