From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Decotigny <decot@googlers.com>
Cc: e1000-devel@lists.sourceforge.net,
Linux NICS <linux.nics@intel.com>,
Bruce Allan <bruce.w.allan@intel.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v1] e1000e: honor pause autoneg flag
Date: Wed, 16 Jul 2014 02:23:46 -0700 [thread overview]
Message-ID: <1405502626.18280.1.camel@jtkirshe-mobl> (raw)
In-Reply-To: <98ea4a6a8e42ffa454d5d42749262e8df02c0167.1405462125.git.decot@googlers.com>
[-- Attachment #1.1: Type: text/plain, Size: 1669 bytes --]
On Tue, 2014-07-15 at 15:09 -0700, David Decotigny wrote:
> Before:
> ifup eth0
> ethtool -A eth0 autoneg off rx on
> ethtool -a eth0 # rx on, as expected
> ifconfig eth0 up
> sleep 5
> ethtool -a eth0 # rx off, not expected
>
> After:
> rx on with iface up, as expected
>
> Signed-off-by: David Decotigny <decot@googlers.com>
> ---
> drivers/net/ethernet/intel/e1000e/mac.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Thanks David, I will add your patch to my queue.
>
> diff --git a/drivers/net/ethernet/intel/e1000e/mac.c b/drivers/net/ethernet/intel/e1000e/mac.c
> index 8c386f3a..ef014ae 100644
> --- a/drivers/net/ethernet/intel/e1000e/mac.c
> +++ b/drivers/net/ethernet/intel/e1000e/mac.c
> @@ -1048,7 +1048,8 @@ s32 e1000e_config_fc_after_link_up(struct e1000_hw *hw)
> * has completed, and if so, how the PHY and link partner has
> * flow control configured.
> */
> - if ((hw->phy.media_type == e1000_media_type_copper) && mac->autoneg) {
> + if ((hw->phy.media_type == e1000_media_type_copper) && mac->autoneg &&
> + hw->adapter->fc_autoneg) {
> /* Read the MII Status Register and check to see if AutoNeg
> * has completed. We read this twice because this reg has
> * some "sticky" (latched) bits.
> @@ -1191,7 +1192,7 @@ s32 e1000e_config_fc_after_link_up(struct e1000_hw *hw)
> * flow control configured.
> */
> if ((hw->phy.media_type == e1000_media_type_internal_serdes) &&
> - mac->autoneg) {
> + mac->autoneg && hw->adapter->fc_autoneg) {
> /* Read the PCS_LSTS and check to see if AutoNeg
> * has completed.
> */
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 362 bytes --]
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
[-- Attachment #3: Type: text/plain, Size: 257 bytes --]
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
prev parent reply other threads:[~2014-07-16 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1405462125.git.decot@googlers.com>
2014-07-15 22:09 ` [PATCH v1] e1000e: honor pause autoneg flag David Decotigny
2014-07-16 9:23 ` Jeff Kirsher [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=1405502626.18280.1.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=decot@googlers.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.com \
--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).