From: "Li Yang" <leoli@freescale.com>
To: "Wolfgang Grandegger" <wg@grandegger.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: UCC GETH does not work on my MPC8360EA
Date: Fri, 19 Sep 2008 14:26:57 +0800 [thread overview]
Message-ID: <2a27d3730809182326t2ee3f114hdaf844ead15acf7b@mail.gmail.com> (raw)
In-Reply-To: <48D24CFA.3040604@grandegger.com>
On Thu, Sep 18, 2008 at 8:43 PM, Wolfgang Grandegger <wg@grandegger.com> wrote:
> 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
I mean that the latest u-boot can fixup the phy-connection-type
automatically base on the chip revision.
- Leo
prev parent reply other threads:[~2008-09-19 6:26 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
2008-09-19 6:26 ` Li Yang [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=2a27d3730809182326t2ee3f114hdaf844ead15acf7b@mail.gmail.com \
--to=leoli@freescale.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=wg@grandegger.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).