From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] PPC460EX with 2 Ethernet Tranceivers
Date: Wed, 12 Aug 2009 11:08:35 +0200 [thread overview]
Message-ID: <200908121108.35608.sr@denx.de> (raw)
In-Reply-To: <16691A8B34B5D9458EA3A1C37A11555A01351D87@tanisys-ex2.Tanisys.Local>
On Tuesday 11 August 2009 16:44:52 Judd Gilbert wrote:
> I am currently running linux 2.6.28.4 on a PPC460EX with 2 Marvell
> Alaska 88EIIII Ethernet transceivers connected to it. I've added the
> flags I believe to configure u-boot properly:
>
> #define CONFIG_IBM_EMAC4_V4 1
> #define CONFIG_HAS_ETH0
> #define CONFIG_HAS_ETH1
> /* Based on the marvell phy datasheet for obscure details */
> #define CONFIG_PHY_ADDR 1 /* PHY address, See schematics
> */
> #define CONFIG_PHY1_ADDR 2 /* 2nd PHY address. See
> schematics */
> #define CONFIG_PHY_RESET 1 /* reset phy upon startup
> */
> #define CONFIG_PHY_GIGE 1 /* Include GbE speed/duplex
> detection */
> #define CONFIG_PHY_DYNAMIC_ANEG 1
>
> If I hold one the 2nd transceiver (address 2) in reset on power up,
> (just for a second or so) the linux kernel boots, detects both PHYs, and
> eth0 and eth1 both work fine. I'm holding the chip in reset manually
> with a switch I added to the board. The linux kernel spits the following
> information out on success:
>
> eth0: EMAC-0 /plb/opb/ethernet at ef600e00, MAC 00:13:a8:00:0d:c6
> eth0: found Generic MII PHY (0x00)
Is this really PHY address 0? Above you configured the PHY for EMAC0 to
address 1.
What does "mii info" show?
Best regards,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
prev parent reply other threads:[~2009-08-12 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 14:44 [U-Boot] PPC460EX with 2 Ethernet Tranceivers Judd Gilbert
2009-08-11 19:20 ` Wolfgang Denk
2009-08-12 9:08 ` Stefan Roese [this message]
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=200908121108.35608.sr@denx.de \
--to=sr@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.