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 16:20:14 +1100 [thread overview]
Message-ID: <1167801614.6165.117.camel@localhost.localdomain> (raw)
In-Reply-To: <20070102.211158.35016452.davem@davemloft.net>
> Thanks for finding these bugs, although that's really strange pause
> behavior you are seeing on your switches.
>
> By default, we advertise PAUSE but not ASYM PAUSE in the tg3 driver,
> and I get flow control on every switch I have here.
Yeah, that's strange. I still have the debug values at hand:
- I advertise 0x5e1
- I read in LPA 0xc9e1 from the switch
(and my bcm PHY tells me Rx and Tx pause disabled in a separate
register)
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).
> 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 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.
Ben.
next prev parent reply other threads:[~2007-01-03 5: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 [this message]
2007-01-03 5:26 ` David Miller
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=1167801614.6165.117.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.