> hi all,
>
> there were a few small threads about rt-networking with
> rtlinux in this mailing list in the past. nevertheless,
> i would be happy if s/o could clarify things a little or
> give some insightful comments:
>
> 1. as far as i understand, it is not possible to use
> the standard linux network drivers (loaded e.g. as
> a kernel module ne2000.o) by a thread running in
> rtlinux.
> it is thus necessary to port the rsp. driver into
> rtlinux.
>
> 2. the linux driver code is certainly available. if
> 1. is true, which changes do i presumably have to
> make in order to use it in rtlinux ?
> will i have standard socket communication with
> the device ?
> (the normal
> if (-1!=(foo=socket(AF_INET,SOCK_DGRAM,0))) {...} calls?)
>
I hope that we all will agree that there is really no such thing as
hard realtime ethernet networking. Once you realize that, you can
back up and look at the design of the system and re-partition it to
work with a soft real-time networking scheme, which then leads to the
happy result that the standard system works just fine, perhaps running
with the user task at a high priority class to minimise latency...
Cramming a bunch of stuff into the rt section just makes the whole
thing non-rt, in my opinion.
FWIW
--
John Ford
National Radio Astronomy Observatory
Green Bank, WV 24944-0002
[EMAIL PROTECTED]
--- [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/
