This belong better in the drivers folder, sorry for putting it here.

Hi Alex:

	This certainly looks like a MAC problem of some sort.  All 0's
for the MAC is a bad thing...
I think that your MAC is incorrectly specified on the command line.  It
should be 001122334455.  While I don't think that this is the cause of
the problem, let's start there and see if it makes any difference.  You
can also try:

io-pkt-v4 -dxemac.so verbose

To start up the stack with the driver in verbose mode and then you can
post the output from sloginfo (assuming that you have slogger running)
and that might give us a bit more info.


	Robert.

-----Original Message-----
From: Alex Pavloff [mailto:community-noreply@qnx.com] 
Sent: Friday, November 21, 2008 2:53 PM
To: ionetmig-networking
Subject: Xilinx devn-xemac not fully functioning with shim layer

Hi all,

I'm trying to use the devn-xemac driver with io-pkt, using the shim.
This driver is present in the Xilinx Virtex II-Pro BSP, and is basically
a thin QNX layer around Xilinx's EDK-provided source function.

No problems in 6.3.2.

Here's what's happening in 6.4 (using io-pkt-v4).

# io-pkt -ptcpip
# mount -T io-net -o mac=00112233445566 devn-xemac.so # ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet 127.0.0.1 netmask 0xff000000
en0: flags=80008802<BROADCAST,SIMPLEX,MULTICAST,SHIM> mtu 1500
        address: 00:00:00:00:00:00

# ifconfig en0 192.168.230.100
# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet 127.0.0.1 netmask 0xff000000
en0: flags=80008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,SHIM> mtu
1500
        address: 00:00:00:00:00:00
        inet 192.168.230.100 netmask 0xffffff00 broadcast
192.168.230.255

Now, when I try to ping another host, I see outgoing ARP packets, I see
the response from the target host... but it looks like the packets
aren't being processed by io-pkt properly.  nicinfo report bytes
transmitted just fine, but nothing recieved.

Another issue appears to be that the shim layer isn't picking up the mac
address, as it comes in at the default.

I suspect the problem is in the xemac driver not quite agreeing with the
shim -- any suggestions on where to look?




_______________________________________________
io-net migration
http://community.qnx.com/sf/go/post17093