netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] sungem: PHY updates & pause fixes
Date: Tue, 02 Jan 2007 21:26:05 -0800 (PST)	[thread overview]
Message-ID: <20070102.212605.15263907.davem@davemloft.net> (raw)
In-Reply-To: <1167801614.6165.117.camel@localhost.localdomain>

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Wed, 03 Jan 2007 16:20:14 +1100

> Now, I cross-over with a TG3 and I get:
> 
>  - I advertise 0x5e1 (hopefully same value)
>  - I read in LPA 0xc5e1 from the TG3
> (and that other register tells me Rx and Tx pause can be enabled).

Does flow control get enabled with the TG3 on these
switches?  Just curious.

> > You should try to use flow control, even slower than 1000Mbit links.
> 
> Sorry, not sure I parse ;-) You mean allowing pause on 10 and 100 as
> well ? I sure can, it's easy to fix.

That's correct.

> > That's the only problem I can see, would you mind fixing that and
> > I'll put your change into my net-2.6 tree and perhaps play around
> > with PAUSE on my switches here?
> 
> Sure will do.

Thanks a lot.

  reply	other threads:[~2007-01-03  5:26 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 [this message]
2007-01-03  5:40       ` Benjamin Herrenschmidt
2007-01-03  6:20         ` Benjamin Herrenschmidt
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=20070102.212605.15263907.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=benh@kernel.crashing.org \
    --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).