All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	netdev@vger.kernel.org
Subject: Re: genphy_read_status() vs. 1000bT Pause capability
Date: Tue, 28 Mar 2017 22:11:24 +1100	[thread overview]
Message-ID: <1490699484.3177.120.camel@kernel.crashing.org> (raw)
In-Reply-To: <20170328094252.GV7909@n2100.armlinux.org.uk>

On Tue, 2017-03-28 at 10:42 +0100, Russell King - ARM Linux wrote:
> The 1000X definitions are for 1000BaseX (fiber), not for 1000BaseT
> (copper).
> 
> I have a working setup here with gigabit pause.  The pause bits come
> from bits 11 and 10, just like for older copper PHYs.  Your link
> parter is indicating that it has no pause capability.  That means
> you can't use pause.

Interesting. I tried and it worked :-) Could be something funny in
the config of our switches.

Thanks for the explanation.

Cheers,
Ben.

  reply	other threads:[~2017-03-28 11:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  0:49 genphy_read_status() vs. 1000bT Pause capability Benjamin Herrenschmidt
2017-03-28  1:09 ` Andrew Lunn
2017-03-28  2:28   ` Benjamin Herrenschmidt
2017-03-28  2:55     ` Benjamin Herrenschmidt
2017-03-28  4:14       ` Florian Fainelli
     [not found]       ` <20170328041405.045FEB206B@b01ledav03.gho.pok.ibm.com>
2017-03-28  5:17         ` Benjamin Herrenschmidt
2017-03-28  5:19           ` Benjamin Herrenschmidt
2017-03-28  9:42           ` Russell King - ARM Linux
2017-03-28 11:11             ` Benjamin Herrenschmidt [this message]
2017-03-28 11:31               ` Russell King - ARM Linux
2017-03-28 20:32                 ` 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=1490699484.3177.120.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=linux@armlinux.org.uk \
    --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.