From: Carl Riechers <criechers@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] EMAC2 & EMAC3 operation on PPC 440GX
Date: Wed, 22 Jun 2005 05:53:38 -0700 (PDT) [thread overview]
Message-ID: <20050622125338.5577.qmail@web30302.mail.mud.yahoo.com> (raw)
In-Reply-To: <42B9593C.9050804@sandburst.com>
I'm also using the Marvel 88E1111 PHY with no
problems. Note that you must follow the reset
waveform exactly per the data sheet or the PHYs will
be in la la land. Hopefully the reset discrete is
connect to a GPIO pin. Since this PHY can not be
strapped for RGMII, you also must set register 20 to
0xce3 in your board specific initialization followed
by a soft reset.
Carl
--- "Travis B. Sawyer" <tsawyer+u-boot@sandburst.com>
wrote:
> 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
>
>
>
-------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux
> Migration Strategies
> from IBM. Find simple to follow Roadmaps,
> straightforward articles,
> informative Webcasts and more! Get everything you
> need to get up to
> speed, fast.
>
http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2005-06-22 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 13:00 [U-Boot-Users] EMAC2 & EMAC3 operation on PPC 440GX David Grab
2005-06-21 20:02 ` Ralph Siemsen
2005-06-22 12:27 ` Travis B. Sawyer
2005-06-22 12:53 ` Carl Riechers [this message]
2005-07-12 15:25 ` AW: " David Grab
2005-07-12 15:37 ` Travis B. Sawyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050622125338.5577.qmail@web30302.mail.mud.yahoo.com \
--to=criechers@yahoo.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox