M. Koehrer wrote: > Hi everybody, > > after using the very old 0.6.0 version for a long time (it works!), I want to > switch over > to the latest RTAI, 2.6 kernel and - of course - RTNET version. > I loaded the latest 2.6.15.4 kernel and the RTAI 3.3 this works fine. > The latest rtnet did not build (configure) error, thus I loaded the latest > SVN snapshot. > Building and compilation is fine now.
Will role out a new version as soon as we updated to the latest RTDM
revision (few changes to NIC IRQ handlers).
>
> As I have a point-to-point connection from the EEPRO100 board to a propietary
> network device
> I do not want (need) to use TDMA.
> However the nice script "rtnet" (that interprets rtnet.conf) seems not to be
> able
> to handle this. TDMA seems to be always required.
Correct. Anyone willing to create a TDMA-less script (or a generic
version of the existing one) is welcome. But most of the work of "rtnet"
is managing the TDMA and RTcfg subsystems.
>
> Another issued with rtnet.conf:
> Is it possible to specify multiple rteth devices in there?
Nope. Was requested before, just takes someone to design and implement this.
>
> Currently, it seems to be that I cannot use the rtnet script and thus I have
> to load and configure everything manually.
> Doing this, I detected that now not only rtnet but also rtipv4 and rtpacket
> has to be loaded to get
> everything running. Perhaps this information should be written in a README
> file (like
> README.noTDMA users...)
>
Just hacked this into the latest README:
- Starting the RTnet core manually (without RTmac):
1. Load required componentes of the real-time Linux extension (see above)
2. Load RTnet modules: rtnet (core), rtipv4 (IPv4 protocol + API),
rtpacket
(packet protocol + API), rt_loopback (rtlo loopback driver), rt_XXX
(real-time NIC driver)
3. Configure real-time NICs: rtifconfig rtethX up <IP>,
rtifconfig rtlo up 127.0.0.1
4. Add host routes to target nodes, either explicitly:
rtroute add <target IP> <target hw-address> dev <local NIC>
Or trigger an ARP handshake:
rtroute solicit <target IP> dev <local NIC>
5. Don't forget that on RTAI and on Xenomai 2.0.x the system timer has
to be
started by someone (in typical RTnet setups this is done by loading
RTcfg).
Any improvements from users' point of view are highly welcome!
Jan
signature.asc
Description: OpenPGP digital signature
