From: Matt Porter <mporter@kernel.crashing.org>
To: Gerhard Jaeger <g.jaeger@sysgo.com>, linuxppc-embedded@ozlabs.org
Subject: Re: PPC 440GX with NS DP83865 phy
Date: Thu, 10 Mar 2005 09:12:28 -0700 [thread overview]
Message-ID: <20050310091227.B27661@cox.net> (raw)
In-Reply-To: <20050310160356.GD19275@gate.ebshome.net>; from ebs@ebshome.net on Thu, Mar 10, 2005 at 08:03:56AM -0800
On Thu, Mar 10, 2005 at 08:03:56AM -0800, Eugene Surovegin wrote:
> On Thu, Mar 10, 2005 at 11:06:53AM +0100, Gerhard Jaeger wrote:
> > the patch has been posted in October last year (wow, thought it was in
> > december or so):
> > http://ozlabs.org/pipermail/linuxppc-embedded/2004-October/015811.html
> >
> > I think it needs some cleanup to apply correctly, but the issue is still
> > the same - the RGMII bridge needs to be setup again after the EMAC has
> > been reset. This problem occurs, when the speed is != 100Mbs, then
> > the clocking for the phy is not correct.
> > I have attached an updated patch, which first checks the PHY speed, then
> > according to that speed the RGMII and ZMII will be setup...
>
> [snip]
>
> OK, from quick look it seems that this is infamous problem with PHYs
> which don't generate Rx clock if there is no link.
Ok, good, I was just looking an wondering if it was the same issue.
> Current driver works sometimes probably just by luck.
>
> Gerhard, there is an experimental NAPI driver for 4xx at
> http://kernel.ebshome.net (for current 2.4 & 2.6 BK trees). I recently
> added full 440GX support. We (Matt and I) are thinking about
> scraping the current driver and using my new version sometimes in the
> future. It'd be great if you could find some time and try this new
> driver on your board. Enable "PHY Rx clock workaround" in driver
> config.
In the meantime, I'll see how this work-around works on some platforms
I have here.
Gerhard: what's the list of 4xx systems (and phys) you have tested
this against? I assume this patch is used on all 4xx platforms you
support in your distro?
next prev parent reply other threads:[~2005-03-10 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 10:06 PPC 440GX with NS DP83865 phy Gerhard Jaeger
2005-03-10 16:03 ` Eugene Surovegin
2005-03-10 16:12 ` Matt Porter [this message]
2005-03-10 16:29 ` Gerhard Jaeger
2005-03-10 16:22 ` Gerhard Jaeger
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 17:11 Sanjay Bajaj
2005-03-10 7:37 ` Gerhard Jaeger
2005-03-10 8:34 ` Eugene Surovegin
2005-03-10 16:03 ` Matt Porter
2005-03-10 16:24 ` Gerhard Jaeger
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=20050310091227.B27661@cox.net \
--to=mporter@kernel.crashing.org \
--cc=g.jaeger@sysgo.com \
--cc=linuxppc-embedded@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox