Beyer Philipp wrote: > Jan Kiszka wrote: >> Beyer Philipp wrote: >> >>> ... >>> kontron_xenomai:~# rtifconfig rtlo up 127.0.0.1 >>> kontron_xenomai:~# rtroute add 10.0.0.2 00:E0:4B:0E:3D:29 dev rteth1 >>> >> You could try rtroute solict as well, first from master to slave, then >> the other way around. This also indicates if there is any communication >> at all (one direction should work as we saw). Check /proc/xenomai/irq if >> something happens, and on which side. If you can resolve the conflict on >> IRQ #10 (e.g. by unloading the Linux driver for the competing device), >> you could also try rteth0. >> > The problem is I actually can't unload this other module, because it is > compiled into the kernel. > And I need it statically, because I boot from it via PXE -> kernel tftp > -> nfsrootfs. This device is the VIA RHINE I was speaking of. It is > eth0. If I try to rtifconfig rteth0 my system freezes! Thats because I > tried with rteth1 :D
/me slowly starting to understand the scenario. Again, you can instruct rt_tulip to skip the first NIC so that rteth1 becomes rteth0. > > kontron_xenomai:~# rtroute solicit 10.0.0.2 dev rteth1 > kontron_xenomai:~# rtroute > Host Routing Table > Hash Destination HW Address Device > 00 0.0.0.0 00:00:00:00:00:00 rtlo > 01 10.0.0.1 00:00:00:00:00:00 rtlo > 01 127.0.0.1 00:00:00:00:00:00 rtlo > 3F 10.255.255.255 FF:FF:FF:FF:FF:FF rteth1 > kontron_xenomai:~# cat /proc/xenomai/irq > IRQ CPU0 > 0: 82322 > 11: 2 > 34: 3 > ------------------------------------------------------------------------- > kontron_xenomai:~# rtroute solicit 10.0.0.1 dev rteth1 > kontron_xenomai:~# rtroute > Host Routing Table > Hash Destination HW Address Device > 00 0.0.0.0 00:00:00:00:00:00 rtlo > 01 127.0.0.1 00:00:00:00:00:00 rtlo > 02 10.0.0.2 00:00:00:00:00:00 rtlo > 3F 10.255.255.255 FF:FF:FF:FF:FF:FF rteth1 > kontron_xenomai:~# cat /proc/xenomai/irq > IRQ CPU0 > 0: 104582 > 11: 3 > 34: 4 irq count before and after the solicit would tell more. The should be one IRQ for packet tx and one for rx. > kontron_xenomai:~# >> BTW, does "normal" networking under Linux work with this link? >> >> > I just tested it with both tulip devices - it works without problems. Ok, then also compare the kernel output of the Linux driver in debug mode with that of rt_tulip in debug mode. Maybe the media type isn't negotiated correctly. I remember some issues - without further details unfortunately. I only remember that tulip was somehow fishy in this regard, fits to this comment [1]. Do you have a crosslink cable in between? There is the "options" module parameter of rt_tulip, playing with it may be worthwhile (see [2] for the meanings). Jan [1]http://www.rts.uni-hannover.de/rtnet/lxr/source/drivers/tulip/tulip_core.c#L1644 [2]http://www.rts.uni-hannover.de/rtnet/lxr/source/drivers/tulip/tulip_core.c#L58
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
