netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] sungem: PHY updates & pause fixes
Date: Wed, 03 Jan 2007 17:20:05 +1100	[thread overview]
Message-ID: <1167805205.6165.141.camel@localhost.localdomain> (raw)
In-Reply-To: <1167802802.6165.129.camel@localhost.localdomain>

> The one with only asym. support is a big Cisco Catalyst 3350 (well.. big
> but not that many ports :-)

Ok, I got in the config of the switch with somebody who knows how to
speak ciscong, and it seems that it defaults to flow control "desired"
for send and "off" for receive on all ports, which means it will indeed
only advertise support for asymetrical flow control.

We've changed the setting for the port on which my sungem g5 is
connected to "desired" on both send and receive, and it now advertises
flow control on both, and sungem does pick it up properly.

So it's indeed the default setting of those cisco switches that seem to
not quite match what drivers like sungem or tg3 like.

Ben.



  reply	other threads:[~2007-01-03  6:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03  4:58 [PATCH] sungem: PHY updates & pause fixes Benjamin Herrenschmidt
2007-01-03  5:11 ` David Miller
2007-01-03  5:20   ` Benjamin Herrenschmidt
2007-01-03  5:26     ` David Miller
2007-01-03  5:40       ` Benjamin Herrenschmidt
2007-01-03  6:20         ` Benjamin Herrenschmidt [this message]
2007-01-04  2:55         ` David Miller
2007-01-04 20:06           ` Eric Lemoine
2007-01-04 20:27             ` David Miller
2007-01-04 20:57               ` Eric Lemoine
2007-01-04 21:15                 ` Benjamin Herrenschmidt

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=1167805205.6165.141.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).