LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Gerhard Jaeger <g.jaeger@sysgo.com>
Cc: Sanjay Bajaj <sbajaj@tsi-telsys.com>, linuxppc-embedded@ozlabs.org
Subject: Re: PPC 440GX with NS DP83865 phy
Date: Thu, 10 Mar 2005 09:03:27 -0700	[thread overview]
Message-ID: <20050310090327.A27661@cox.net> (raw)
In-Reply-To: <200503100837.08717.g.jaeger@sysgo.com>; from g.jaeger@sysgo.com on Thu, Mar 10, 2005 at 08:37:08AM +0100

On Thu, Mar 10, 2005 at 08:37:08AM +0100, Gerhard Jaeger wrote:
> On Wednesday 09 March 2005 18:11, Sanjay Bajaj wrote:
> > Has anybody used PPC 440GX with NS DP83865 phy? If you have or have any
> > information to set it up, please share. 
> > 
> We're using this PHY on a custom 440GX board. Connected via GMII!
> After setting up the RGMII bridge correctly (see manual), you also have to
> tweak the EMAC driver. I have sent a patch (which has been rejected) a few
> weeks ago to the list which changes the setup procedure of the EMAC to work
> with a DP83865 PHY. THe current implementation will not work.

FWIW, I did go back and see the patch from 22 October in my mbox.  It's
not rejected...just missed amongst a lot of other things. If things
are quiet, it's best to ping in case somebody missed your patch.

Thanks,
Matt

  parent reply	other threads:[~2005-03-10 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 17:11 PPC 440GX with NS DP83865 phy Sanjay Bajaj
2005-03-10  7:37 ` Gerhard Jaeger
2005-03-10  8:34   ` Eugene Surovegin
2005-03-10 16:03   ` Matt Porter [this message]
2005-03-10 16:24     ` Gerhard Jaeger
  -- strict thread matches above, loose matches on Subject: below --
2005-03-10 10:06 Gerhard Jaeger
2005-03-10 16:03 ` Eugene Surovegin
2005-03-10 16:12   ` Matt Porter
2005-03-10 16:29     ` Gerhard Jaeger
2005-03-10 16:22   ` 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=20050310090327.A27661@cox.net \
    --to=mporter@kernel.crashing.org \
    --cc=g.jaeger@sysgo.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=sbajaj@tsi-telsys.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