From: Arun Parameswaran <aparames@broadcom.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<bcm-kernel-feedback-list@broadcom.com>, <rjui@broadcom.com>,
<aparames@broadcom.com>, <sbranden@broadcom.com>,
<jdzheng@broadcom.com>
Subject: [PATCH 0/1] Fix an issue with 'ethtool' configuring PHYs
Date: Wed, 20 May 2015 14:35:29 -0700 [thread overview]
Message-ID: <1432157730-26865-1-git-send-email-aparames@broadcom.com> (raw)
Hi,
This patch fixes an issue while using the 'ethtool' to query/set PHY's
configurations. The 'ethtool' interface in the Kernel seem to always
query settings for PHY0, irrespective of the PHY specified, while
issuing the 'ethtool' command.
For example when issueing 'ethtool -s eth0 phyad 1 speed 100' command
to set the speed of PHY1's speed, the current software would first
retrieve PHY0 settings, then apply the request settings (in this case
'speed') on top. It then uses this (PHY0's config with new speed)
settings to update the PHY1, which now ends up with partial
configurations of PHY0 and the new speed.
This patch series is based on Linux v4.1-rc4 and is available in:
https://github.com/Broadcom/cygnus-linux/tree/net-core-ethtool-fix-v1
Arun Parameswaran (1):
SWMAPYVR-4339 net: core: 'ethtool' issue with querying phy settings
net/core/ethtool.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
--
1.7.9.5
next reply other threads:[~2015-05-20 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 21:35 Arun Parameswaran [this message]
2015-05-20 21:35 ` [PATCH 1/1] net: core: 'ethtool' issue with querying phy settings Arun Parameswaran
2015-05-22 20:15 ` David Miller
2015-05-31 19:54 ` Ben Hutchings
2015-06-01 0:19 ` David Miller
2015-06-01 18:05 ` Ben Hutchings
2015-06-01 21:41 ` Arun Parameswaran
2015-06-01 21:46 ` David Miller
2015-06-01 23:53 ` Arun Parameswaran
2015-06-01 23:55 ` David Miller
2015-06-02 0:57 ` Ben Hutchings
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=1432157730-26865-1-git-send-email-aparames@broadcom.com \
--to=aparames@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=jdzheng@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/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).