From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] PPC460EX with 2 Ethernet Tranceivers
Date: Tue, 11 Aug 2009 21:20:11 +0200 [thread overview]
Message-ID: <20090811192011.C0BCE833DBD2@gemini.denx.de> (raw)
In-Reply-To: <16691A8B34B5D9458EA3A1C37A11555A01351D87@tanisys-ex2.Tanisys.Local>
Dear "Judd Gilbert",
In message <16691A8B34B5D9458EA3A1C37A11555A01351D87@tanisys-ex2.Tanisys.Local> you 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:
...
> eth0: EMAC-0 /plb/opb/ethernet at ef600e00, MAC 00:13:a8:00:0d:c6
> eth0: found Generic MII PHY (0x00)
> /plb/opb/emac-rgmii at ef601500: input 1 in RGMII mode
> eth1: EMAC-1 /plb/opb/ethernet at ef600f00, MAC 00:13:a8:00:0d:c7
> eth1: found Generic MII PHY (0x02)
>
> If I don't hold the 2nd transceiver in reset I get the following message
> when linux boots:
>
> eth0: EMAC-0 /plb/opb/ethernet at ef600e00, MAC 00:13:a8:00:0d:c6
> eth0: found Generic MII PHY (0x00)
> /plb/opb/emac-rgmii at ef601500: input 1 in RGMII mode
> /plb/opb/ethernet at ef600f00: can't find PHY!
Well, this is a Linux issue. Linux should make no assumptions about a
specific state of a network device. No matter what U-Boot does, the
Linux kernel should always initialize the hardware so that it works.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A girl with a future avoids the man with a past.
-- Evan Esar, "The Humor of Humor"
next prev parent reply other threads:[~2009-08-11 19:20 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 [this message]
2009-08-12 9:08 ` Stefan Roese
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=20090811192011.C0BCE833DBD2@gemini.denx.de \
--to=wd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox