[U-Boot-Users] EMAC2 & EMAC3 operation on PPC 440GX

[Travis B. Sawyer <tsawyer+u-boot@sandburst.com>]

David Grab wrote:
> Hello,
> 
> as mentioned before i?m using two Marvel 88E1111 PHY on my PPC440GX Board.
> They are configured as a RGMII to copper interface for use with EMAC 2 & 3.
> So now i?m in trouble with the configuration of the network. After booting i
> set with "setenv ethact ppc_440x_eth2" EMAC2 for networking. After that i
> try a "ping" to know if network is working. Reading the speed and duplex
> from PHY works, but after that i got in an endless loop. I figured out, that
> no interrupt is recognized and in 440gx_enet.c in ppc_440x_eth_init the
> default configuration of the interrupt handler is for ETH0:
> 
> 		irq_install_handler (VECNUM_EWU0 + (hw_p->devnum * 2),
> 				     (interrupt_handler_t *) enetInt, dev);
> 		irq_install_handler (VECNUM_ETH0 + (hw_p->devnum * 2),
> 				     (interrupt_handler_t *) enetInt, dev);
> 
> so i changed it as following...
> 
> 		irq_install_handler (VECNUM_EWU2 + (hw_p->devnum * 2),
> 				     (interrupt_handler_t *) enetInt, dev);
> 		irq_install_handler (VECNUM_ETH2 + (hw_p->devnum * 2),
> 				     (interrupt_handler_t *) enetInt, dev);

You shouldn't need to do this.  I have 3 different boards that work fine 
with emac2 & emac3.


> 
> and added in vecnum.h these lines:
> 
> #define VECNUM_ETH2         (64 + 0)   /* Ethernet 0 interrupt status  */
> #define VECNUM_EWU2        (64 + 1)   /* Ethernet 0 wakeup            */
> 
> But this didn?t solve the problem. Actually i also couldn?t get the TxCLK
> work on my RGMII Bridge and i don?t know why.

I saw the note yesterday about the etch length.  The hw guys didn't want
to route the 13" of extra etch so I whack a reg in our phy to tell it
to skew the clock.

-travis