From: Wolfgang Grandegger <wg@grandegger.com>
To: Li Yang-R58472 <LeoLi@freescale.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: UCC GETH does not work on my MPC8360EA
Date: Thu, 18 Sep 2008 14:43:38 +0200 [thread overview]
Message-ID: <48D24CFA.3040604@grandegger.com> (raw)
In-Reply-To: <113760FDF39C3E40AAB8DE6E6C64D0A7110901@zch01exm26.fsl.freescale.net>
Li Yang-R58472 wrote:
>> -----Original Message-----
>> From: linuxppc-dev-bounces+leoli=freescale.com@ozlabs.org
>> [mailto:linuxppc-dev-bounces+leoli=freescale.com@ozlabs.org]
>> On Behalf Of Wolfgang Grandegger
>> Sent: Wednesday, September 17, 2008 5:18 PM
>> To: linuxppc-dev
>> Subject: UCC GETH does not work on my MPC8360EA
>>
>> Hello,
>>
>> I have a wired problems with my MPC8360EA using Linux
>> 2.6.27-rc6. The UCC GEHT controller works fine with 100/Full
>> but fails with 1000/Full.
>> What I see is that the TX done interrupts come (ifconfig's TX
>> packet counter goes up), but the messages does not show up on
>> the wire. RX seems to work properly, though.
>>
>> Any idea what's going wrong? Does someone got it working with
>> 1000/Full?
>
> This looks like an old problem that RGMII Tx shouldn't use internal
> delay while Rx should use. So try to use 'rgmii-rxid' as
> phy-connection-type in device tree. Also there should have been a fixup
> in u-boot for this. So update to use latest u-boot might fix your
> problem.
I do not have problems with U-Boot using 1000/full. The DTS property
phy-connection-type = "rgmii-rxid"
fixed the problem wuth Linux, indeed, but I realize slow boot over NFS
and sometimes I even get "nfs server not responding" with that setting.
Wolfgang.
next prev parent reply other threads:[~2008-09-18 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 9:17 UCC GETH does not work on my MPC8360EA Wolfgang Grandegger
2008-09-17 9:38 ` Li Yang-R58472
2008-09-18 12:43 ` Wolfgang Grandegger [this message]
2008-09-19 6:26 ` Li Yang
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=48D24CFA.3040604@grandegger.com \
--to=wg@grandegger.com \
--cc=LeoLi@freescale.com \
--cc=Linuxppc-dev@ozlabs.org \
/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.