mpc8270 & Intel 82551ER on 2.6.17.14

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.  
 
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.
 
The situation is when I use the ethtool with the driver loaded and eth0
not configured with ifconfig I get this:
SCB Status Word (Lower Word)             0x0000
      RU Status:               Idle
      CU Status:               Idle
      ---- Interrupts Pending ----
      Flow Control Pause:                no
      Early Receive:                     no
      Software Generated Interrupt:      no
      MDI Done:                          no
      RU Not In Ready State:             no
      CU Not in Active State:            no
      RU Received Frame:                 no
      CU Completed Command:              no
SCB Command Word (Upper Word)            0x0100
      RU Command:              No Command
      CU Command:              No Command
      Software Generated Interrupt:      no
      ---- Interrupts Masked ----
      ALL Interrupts:                    yes
      Flow Control Pause:                no
      Early Receive:                     no
      RU Not In Ready State:             no
      CU Not in Active State:            no
      RU Received Frame:                 no
      CU Completed Command:              no
MDI/MDI-X Status:                        MDI
 

With eth0 configured using the command "ifconfig eth0 192.168.1.7
netmask 255.255.255.0 up" I get this:
SCB Status Word (Lower Word)             0x6450
      RU Status:               Ready
      CU Status:               Suspended
      ---- Interrupts Pending ----
      Flow Control Pause:                no
      Early Receive:                     no
      Software Generated Interrupt:      yes
      MDI Done:                          no
      RU Not In Ready State:             no
      CU Not in Active State:            yes
      RU Received Frame:                 yes
      CU Completed Command:              no
SCB Command Word (Upper Word)            0x0000
      RU Command:              No Command
      CU Command:              No Command
      Software Generated Interrupt:      no
      ---- Interrupts Masked ----
      ALL Interrupts:                    no
      Flow Control Pause:                no
      Early Receive:                     no
      RU Not In Ready State:             no
      CU Not in Active State:            no
      RU Received Frame:                 no
      CU Completed Command:              no
MDI/MDI-X Status:                        MDI
 
 
 
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.
 
I have no idea where to go with this.  It seems like the PCI bus is
working, but possibly not the Interrupt handler.
 
 
 

Nicholas Hickman
Applications Engineer
DTech Labs, Inc.


 

Hi Nicholas,

On 6/29/07, Nicholas Hickman [off-list ref] wrote:

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.

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.

<snip..>

I have the same, exact same problem. But there are some of the
differences with the setup though. I have an MPC5200B and the other
difference is that I have a 2.6.21-rt3. However its the same ethernet
controller.

I am trying out a few things here, some of them being complete
guesses. But if I hit something, I will let this list know. Anyone
else had similar issues ? Request you to please holler.

regards
prady
-- 
htp://prady.livejournal.com

Pradyumna,

With the help of some others I have finally figured it out.  I took a
step back and read the manual over and over along with debugging my
U-boot until it worked.  My issue there was with the SIUMCR. Since I now
had that working in U-boot I moved on to the kernel where I found that I
was redefining the SIUMCR here:

arch/ppc/syslib/m82xx_pci.c=20
approx line 248
#elif defined CONFIG_PQ2FADS || MYBOARD
        /*
         * Setting required to enable IRQ1-IRQ7 (SIUMCR [DPPC]),
         * and local bus for PCI (SIUMCR [LBPC]).
         */
        immap->im_siu_conf.siu_82xx.sc_siumcr =3D

I was entering this routine since I was basing my config off of the
PQ2FADS board.  I removed my board definition from the elif and
everything seems to be working fine.

Good luck!


-Nick


-----Original Message-----
From: Pradyumna Sampath [mailto:pradyumna.sampath@gmail.com]=20
Sent: Friday, June 29, 2007 4:12 AM
To: Nicholas Hickman
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mpc8270 & Intel 82551ER on 2.6.17.14

Hi Nicholas,

On 6/29/07, Nicholas Hickman [off-list ref] wrote:

I am having trouble getting two 82551ER Ethernet controllers running=20
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.

In the kernel I mapped the IRQ's through /arch/ppc/m82xx_pci.c.  I've=20
been using the e100 drive that comes with the 2.6.17.14 kernel and=20
have also tried the driver directly from Intel.  Both give the same=20
results.  The PCI scan shows the correct output for how the device

should be configured.
<snip..>

I have the same, exact same problem. But there are some of the
differences with the setup though. I have an MPC5200B and the other
difference is that I have a 2.6.21-rt3. However its the same ethernet
controller.

I am trying out a few things here, some of them being complete guesses.
But if I hit something, I will let this list know. Anyone else had
similar issues ? Request you to please holler.

regards
prady
--
htp://prady.livejournal.com