Virtex 4 Avnet Mini-Module Networking.

[Yoshio Kashiwagi]

Glenn-san,

The PLB TEMAC driver is supporting checksum off loading (checksum
calculation by hardware).
If the same kernel source is used, isn't the hardware checksum
of PLB TEMAC disabled by the MHS file of Mini-Module?

BEGIN plb_temac
 PARAMETER INSTANCE = plb_temac_0
 PARAMETER HW_VER = 3.00.a
 PARAMETER C_PLB_CLK_PERIOD_PS = 10000
 PARAMETER C_TXFIFO_DEPTH = 131072
 PARAMETER C_RXFIFO_DEPTH = 131072
 PARAMETER C_MAC_FIFO_DEPTH = 64
 PARAMETER C_BASEADDR = 0x80000000
 PARAMETER C_HIGHADDR = 0x8000ffff
 PARAMETER C_INCLUDE_RX_CSUM = 1    <--- H/W checksum enable
 PARAMETER C_INCLUDE_TX_CSUM = 1    <--- H/W checksum enable
 PARAMETER C_RX_DRE_TYPE = 2
 PARAMETER C_TX_DRE_TYPE = 2

Yoshio Kashiwagi - Nissin Systems

> I am having trouble using the network on the Avent Mini-Module.  I had 
the
> network working on the ML403 board with Linux 2.6.19.
> 
> The kernel comes up fine with the Mini-Module and the network seems to 
work
> until I try to use it.  I can configured the ethernet with ifconfig 
and can
> even ping another machine on the network.
> 
> The problem is with the TCP layer.  It seems almost everytime the
> Mini-Module sends TCP information the checksum is reported an wrong 
(via
> ethereal).  The only thing that comes to mind is the ML403 uses a 
Marvell
> PHY and the Mini-Module has a Broadcom PHY.  I do not know enough 
about
> low-level networking to know where the problem is.  Is the checksum
> generated in the PHY?  Could something be wrong in Linux programming 
the
> Broadcom PHY and not the Marvell PHY?  Why is it only the TCP 
information
> (the IP information has the correct checksum)?
> 
> Thanks for any information you can offer.
> 
> Glenn