From: Wen-Ping Ying (wying@nextcomminc.com)
Date: Thu Jan 18 2001 - 20:12:33 EST
Hi Greg & Alistair, You are both right in that the ether chip addr is different from the hard coded addr in the driver. I guess the eventual solution to this would be to figure out how one can read the addr from the hardware. Further experiment of the network performance using continuous udp transfer caused some hiccups on the driver. The following screen capture is the result of dev->tbusy in fec_enet_start_xmit() of fec.c: (Regular ping with one second interval did cause this problem.) ----- eth0: transmit timed out. Ring data dump: cur_tx 3f4060 (full) cur_rx 3f4008. 1c01 022a 00362812 1c01 022a 00362812 1c01 022a 00362812 1c01 022a 00362812 1c01 022a 00362812 1c01 022a 00362812 1c01 022a 00362812 1c01 022a 00362812 8840 0040 003f3000 8840 0040 003f3000 8840 0040 003f3000 8840 0040 003f3000 8840 0040 003f3000 8840 0040 003f3000 8840 0040 003f3000 8840 0040 003f3000 ----------------------------------- Wen-Ping Ying NextComm, Inc. This message resent by the uclinux-dev@uclinux.org list server http://www.uClinux.org/
This archive was generated by hypermail 2.1.4 : Thu Sep 19 2002 - 13:19:26 EDT