I encountered a similar problem and have found four related solutions:
1. To see how to write Linux kernel tasks that can bind/connect etc.
check out
the implementation of NFS
in the kernel. It has its own scheduler and is quite complex (i.e. I
didn't go
through the whole thing). You could probably figure out the API and use
it.
2. The RTLinux network driver for the Tulip board. This driver could
be used
as an interface, but you would have to write your own protocol stacks.
3. At http://www.realtimelinux.org/archives/networking/20001/ you will
find a
discussion of what you are looking for and someone who has ported some
of the
linux native code to the RTlinux kernel. I don't really know what this
means,
since IP and ethernet are both non-real-time sorts of things.
4. I have written a RTLinux module (but have not yet distributed it)
that
allows sockets to be created using the standard Linux socket interface,
and
then "passed" to a realtime module that can then send and receive
packets. It
only works with UDP. All management is performed by the hosting user
task.
The module actually sends the packets through the standard Linux kernel,
so the
delay from the packet generation to output is not controlled, however
all the
standard networking features such as ARP, IP forwarding, NAT, ICMP are
performed by the kernel.
Robert Kavaler
[EMAIL PROTECTED]
Re
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
