Wolfgang Grandegger wrote:
Don't remember when this driver last transfered some packets
successfully. It was a contribution that we were never able to test and
maintain here. And then there are those documented RT issues due to
potential long delays in IRQ or xmit context.
OK, I'm a beat tester for this card... When I have my MPC 52xx driver
working I will have a closer look.
Great!
...
No, I have two RT ethernet interfaces connected with a cross over cable.
And the I just do rtping on the local (or remote) side:
# insmod rtnet.o
# insmod rt_mpc52xx_fec.o
# rtifconfig rteth0 up 10.0.0.2
# rtroute solicit 10.0.0.1 dev rteth0
# rtping 10.0.0.1
Real-time PING 10.0.0.1 56(84) bytes of data.
mpc5xxx_fec_hard_start_xmit:
dev c34b4800, priv c34b4900, skb c340c040
Outgoing data @c340c0a0, length 00000062:
00000000: 0001027a 37c90002 b3cb5bf8 08004500
00000010: 00540000 4000ff01 67a60a00 00020a00
00000020: 00010800 f81cd59f 00010000 00000000
00000030: 00000001 02030405 06070809 0a0b0c0d
00000040: 0e0f1011 12131415 16171819 1a1b1c1d
00000050: 1e1f2021 22232425 26272829 2a2b2c2d
00000060: 2e2f2e2f c340c162 c340c150 c340c140
mpc5xxx_sdma_transmit_interrupt:
dev c34b4800, priv c34b4900
mpc5xxx_sdma_receive_interrupt:
status 08000066, skb c3413480, rbuf c34134e0
Incoming rbuf, length: 00000066
00000000: 0002b3cb 5bf80001 027a37c9 08004500
00000010: 0054007e 4000ff01 67280a00 00010a00
00000020: 00020000 001dd59f 00010000 00000000
00000030: 00000001 02030405 06070809 0a0b0c0d
00000040: 0e0f1011 12131415 16171819 1a1b1c1d
00000050: 1e1f2021 22232425 26272829 2a2b2c2d
00000060: 2e2f4965 b86eb86e 00000000 00000000
RTnet: unknown layer-3 protocol
64 bytes from 10.0.0.1: icmp_seq=1 time=0.0 us
...
Do you see an obvious problem with the received data (with your RTnet
sensitive eyes)?
No, I don't. The layer-3 protocol ID is 0x0800 - IPv4. And if this were
unknown to the stack, you would not see the ping reply. Strange.
And you are definitely using latest SVN? Have a look at do_stacktask()
in stack/stack_mgr.c: in case pt_entry->handler() was called (i.e. the
ping reply was received), you should not get to the line where that
infamous message is generated.
I'm also puzzled why the time is 0.0.
RTAI timer is not running. Insert rtcfg.ko e.g. to get it started (even
if you don't use RTcfg).
Jan
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users
