Allen,
The 8260 Ethernet controller needs to know about the duplex mode in which
the PHY operates. The driver sets it to half duplex by default, and needs
the feed back of the PHY to set it to full duplex.
As you may know, the hub always operates in half duplex, while the switch
usually operates in full duplex, if it is directly connected to your unit,
and your PHY accepts to negociate to full duplex.
Both the Ethernet controller and the PHY should be set to the same mode, or
your likely to run into communication problems (as you see ;-).
Regards,
--------------------------------------------
Jean-Denis Boyer, B.Eng., System Architect
Mediatrix Telecom Inc.
4229 Garlock Street
Sherbrooke (Québec)
J1L 2C8 CANADA
(819)829-8749 x241
--------------------------------------------
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
The 8260 Ethernet controller needs to know about the duplex mode in which
the PHY operates. The driver sets it to half duplex by default, and needs
the feed back of the PHY to set it to full duplex.
As you may know, the hub always operates in half duplex, while the switch
usually operates in full duplex, if it is directly connected to your unit,
and your PHY accepts to negociate to full duplex.
Yes, the source code has been modified to force full-duplex.
(fcc_restart(dev,1) if I remember correctly :) In fact, before this change
was made Ethernet communications did not work at all. (At least it would not
get past bootp) I searched for something that looked like it was speed
related but found nothing. (Other than the MII reporting)
Other ideas?
BTW: We are using a BCM switch for our PHY. The interface to the processor
is always full-duplex, 100BT regardless of the external connections. Hence
the no MII PHY option.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Allen Curtis wrote:
quoted
The 8260 Ethernet controller needs to know about the duplex mode in which
the PHY operates. The driver sets it to half duplex by default, and needs
the feed back of the PHY to set it to full duplex.
As you may know, the hub always operates in half duplex, while the switch
usually operates in full duplex, if it is directly connected to your unit,
and your PHY accepts to negociate to full duplex.
Yes, the source code has been modified to force full-duplex.
(fcc_restart(dev,1) if I remember correctly :) In fact, before this change
was made Ethernet communications did not work at all. (At least it would not
get past bootp) I searched for something that looked like it was speed
related but found nothing. (Other than the MII reporting)
Other ideas?
Could it be an analog problem? Have you looked at the signals comming in on
a scope?
BTW: We are using a BCM switch for our PHY. The interface to the processor
is always full-duplex, 100BT regardless of the external connections. Hence
the no MII PHY option.
Let me get this straight, You have no PHY, no magnet, no connector? If this
is the case are you sure your voltages on the I/O compatible?
I have thought about building a Beowolf cluster in this manner out of 8260s
just to impress my geek friends and colleages. Of course I don't have the
time or money to do it, but its fun to think about.
Good Luck
Conn
--
*****************************************************************
If you live at home long enough, your parents will move out.
*****************************************************************
Conn Clark
Engineering Stooge clark@esteem.com
Electronic Systems Technology Inc. www.esteem.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Could it be an analog problem? Have you looked at the signals
comming in on
a scope?
Looking at the signal with a scope is probably a good idea. Here is an
update from today's fun.
1. These is an error in the fcc_enet.c file which causes NO and CRC errors
when running in full-duplex mode. fcc_restart() should be updated to include
FCC_PSMR_LPB when configuring full-duplex mode. (cleared when not)
2. Some relative performance measurements (HHL 2.4.2 vs. 2.4.19pre9)
10T Hub | 100BT switch
-------------------------------------|
2.4.2 | 410KBps | 750KBps |
-------------------------------------|
2.4.19 | 440KBps | 190KBps |
--------------------------------------
RedHat 2.4.18-3 (x86) 3900KBps
3. TOP shows as much as 48% system utilization during a single FTP transfer.
With the fix mentioned in #1, there are 0 errors reported by ifconfig.
I may be missing something but I believe that these numbers are going the
wrong way. There is still the question of performance decrease when using a
100BT switch. Signal intregety can not be the only suspect considering the
performance did increase using an older version of the kernel. (although
nothing like the Workstation performance)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/