From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ajay Patel <patela@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ppc: Sungem auto-negotiation problem
Date: Thu, 28 Jul 2005 10:03:18 +0100 [thread overview]
Message-ID: <1122541399.18835.21.camel@gaston> (raw)
In-Reply-To: <90f56e4805072711341bc156d9@mail.gmail.com>
On Wed, 2005-07-27 at 11:34 -0700, Ajay Patel wrote:
> Hi,
>
> I have a PowerMac G5. (Newer Model with SMU).
> It has a Sungem ethernet with "PHY ID: 2060d2".
>
> When this ethernet is connected to
> "Tigon3 [partno(BCM95704A6) rev 2002 PHY(5704)] " or
> to the cisco switch, The PowerMac declares link up with
> 100 Mbs, while the other end declares link up with 1000Mbs.
> In this setup both end cannot ping each other.
>
> If I lower the speed of Tigon based adapter or Cisco's switch
> port to 100Mbs, both end can ping each other.
>
> Is it a bug? or Am I missing something?
I posted a patch that might fix it a while ago. What kernel version have
you tested specifically ?
Ben.
prev parent reply other threads:[~2005-07-28 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 18:34 ppc: Sungem auto-negotiation problem Ajay Patel
2005-07-28 9:03 ` Benjamin Herrenschmidt [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=1122541399.18835.21.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patela@gmail.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