From: Stefan Roese <sr@denx.de>
To: linuxppc-embedded@ozlabs.org
Cc: vb <vb@vsbe.com>
Subject: Re: EMAC2 in ibm_newemac driver
Date: Thu, 2 Oct 2008 07:51:42 +0200 [thread overview]
Message-ID: <200810020751.42821.sr@denx.de> (raw)
In-Reply-To: <f608b67d0810012138w64ba5ecbg1f88fff505c820b7@mail.gmail.com>
On Thursday 02 October 2008, vb wrote:
> I have a 460GT based system with three ethernet interfaces, and I
> don't seem to be able to bring up EMAC2 in RGMII mode. The PHY works
> just fine, the counterpart on the other side of the serdes link
> autonegotiates successfully, etc. When I attempt to send something
> from the interface though, nothing shows up on the RGMII lines (I use
> a scope to probe it). The received traffic is passed from the PHY to
> the MAC, but again, nothing is reported by the rx driver.
>
> I am using the latest released code from 2.6.26.5 (I started with
> 2.6.25 release, and in that case just EMAC0 worked, updgrading to to
> 2.6.26.5 made the second interface work, but the third one seems to be
> stuck. I see that the Denx tree has a lot of changes in the driver,
> but it is not as cleanly portable, so advancing there is not an
> option.
The ibm_newemac driver in the DENX repository has absolutely no changes to the
kernel.org version.
> I am trying to debug it, but am wondering if anyone had more than two
> interfaces going on this architecture and if so - what are the
> gotchas.
The AMCC Glacier 460GT eval board uses all 4 EMAC's with RGMII. IIRC, then you
need to configure the GPIO multiplexing differently (compared to Canyonlands
460EX) to fully support all 4 EMAC's on 460GT. This is done in U-Boot. I
suggest that you check this configuration first.
Best regards,
Stefan
next prev parent reply other threads:[~2008-10-02 5:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 4:38 EMAC2 in ibm_newemac driver vb
2008-10-02 5:51 ` Stefan Roese [this message]
2008-10-03 4:57 ` vb
2008-10-03 14:37 ` 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=200810020751.42821.sr@denx.de \
--to=sr@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vb@vsbe.com \
/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;
as well as URLs for NNTP newsgroup(s).