<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3132" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2>I am having trouble getting two 82551ER Ethernet
controllers running in Linux. I am able to scan the PCI bus and see the
devices and I was even able to program the EEPROM from U-boot.
</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>In the kernel I mapped the IRQ's through
/arch/ppc/m82xx_pci.c. I've been using the e100 drive that comes with the
2.6.17.14 kernel and have also tried the driver directly from Intel. Both
give the same results. The PCI scan shows the correct output for how the
device should be configured.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>The situation is when I use the ethtool with the
driver loaded and eth0 not configured with ifconfig I get this:<BR>SCB Status
Word (Lower
Word)
0x0000<BR> RU
Status:
Idle<BR> CU
Status:
Idle<BR> ---- Interrupts Pending
----<BR> Flow Control
Pause:
no<BR> Early
Receive:
no<BR> Software Generated
Interrupt: no<BR>
MDI
Done:
no<BR> RU Not In Ready
State:
no<BR> CU Not in Active
State:
no<BR> RU Received
Frame:
no<BR> CU Completed
Command:
no<BR>SCB Command Word (Upper
Word)
0x0100<BR> RU
Command:
No Command<BR> CU
Command:
No Command<BR> Software Generated
Interrupt: no<BR>
---- Interrupts Masked ----<BR> ALL
Interrupts:
yes<BR> Flow Control
Pause:
no<BR> Early
Receive:
no<BR> RU Not In Ready
State:
no<BR> CU Not in Active
State:
no<BR> RU Received
Frame:
no<BR> CU Completed
Command:
no<BR>MDI/MDI-X
Status:
MDI</FONT></DIV>
<DIV> </DIV><FONT face=Arial size=2>
<DIV><BR>With eth0 configured using the command "ifconfig eth0 192.168.1.7
netmask 255.255.255.0 up" I get this:<BR>SCB Status Word (Lower
Word)
0x6450<BR> RU
Status:
Ready<BR> CU
Status:
Suspended<BR> ---- Interrupts Pending
----<BR> Flow Control
Pause:
no<BR> Early
Receive:
no<BR> Software Generated
Interrupt: yes<BR>
MDI
Done:
no<BR> RU Not In Ready
State:
no<BR> CU Not in Active
State:
yes<BR> RU Received
Frame:
yes<BR> CU Completed
Command:
no<BR>SCB Command Word (Upper
Word)
0x0000<BR> RU
Command:
No Command<BR> CU
Command:
No Command<BR> Software Generated
Interrupt: no<BR>
---- Interrupts Masked ----<BR> ALL
Interrupts:
no<BR> Flow Control
Pause:
no<BR> Early
Receive:
no<BR> RU Not In Ready
State:
no<BR> CU Not in Active
State:
no<BR> RU Received
Frame:
no<BR> CU Completed
Command:
no<BR>MDI/MDI-X
Status:
MDI</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>If I issue a PING out of the port and sniff the traffic on the destination
PC I see the ARP requests and I send the reply, but the embedded machine sees
nothing. If I use ethtool or even ifconfig to view the statistics on the
port they both show that there are no packets in or out.</DIV>
<DIV> </DIV>
<DIV>I have no idea where to go with this. It seems like the PCI bus is
working, but possibly not the Interrupt handler.</DIV>
<DIV> </DIV>
<DIV></FONT> </DIV>
<DIV> </DIV>
<DIV align=left>
<P class=MsoNormal><STRONG><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Calibri','sans-serif'">Nicholas
Hickman<BR></SPAN></STRONG><SPAN style="FONT-SIZE: 8pt">Applications
Engineer<BR></SPAN><STRONG><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Calibri','sans-serif'">DTech Labs,
Inc</SPAN></STRONG><SPAN style="FONT-SIZE: 8pt">.<BR></SPAN></P></DIV>
<DIV> </DIV></BODY></HTML>