From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, "Brown, Aaron F" <aaron.f.brown@intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH] igb: support BCM54616 PHY
Date: Thu, 27 Jul 2017 10:57:36 -0700 [thread overview]
Message-ID: <76c8ea56-8e4e-a85c-abe5-695b46c99308@gmail.com> (raw)
In-Reply-To: <20170727153713.GG18666@lunn.ch>
On 07/27/2017 08:37 AM, Andrew Lunn wrote:
> On Thu, Jul 27, 2017 at 12:40:01AM +0000, Brown, Aaron F wrote:
>>> From: Intel-wired-lan [mailto:intel-wired-lan-bounces@osuosl.org] On Behalf
>>> Of John W. Linville
>>> Sent: Friday, July 21, 2017 11:12 AM
>>> To: netdev@vger.kernel.org
>>> Cc: intel-wired-lan@lists.osuosl.org; John W. Linville
>>> <linville@tuxdriver.com>
>>> Subject: [Intel-wired-lan] [PATCH] igb: support BCM54616 PHY
>>>
>>> The management port on an Edgecore AS7712-32 switch uses an igb MAC,
>>> but
>>> it uses a BCM54616 PHY. Without a patch like this, loading the igb
>>> module produces dmesg output like this:
>>>
>>> [ 3.439125] igb: Copyright (c) 2007-2014 Intel Corporation.
>>> [ 3.439866] igb: probe of 0000:00:14.0 failed with error -2
>>>
>>> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>>> Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>>> ---
>>> drivers/net/ethernet/intel/igb/e1000_82575.c | 6 ++++++
>>> drivers/net/ethernet/intel/igb/e1000_defines.h | 1 +
>>> drivers/net/ethernet/intel/igb/e1000_hw.h | 1 +
>>> 3 files changed, 8 insertions(+)
>>
>> I do not have the specific hardware (Edgecore switch) but as far as regression tests go this works fine.
>> Tested-by: Aaron Brown <aaron.f.brown@intel.com>
>
> Sorry, missed the initial post, so replying to a reply.
>
> Linux has supported the BCM54616 PHY since April 2015. If the Intel
> drivers used the Linux PHY drivers, you would not of had this problem.
>
> It would be good if somebody spent the time to migrate these MAC
> drivers to use the common Linux PHY infrastructure.
I suspect there is a design pattern within the Intel drivers to share as
much low-level code as possible between OSes and only have some
Linux-ism where necessary (e.g: net_device, ethtool etc.).
PHY code is a pain in general, especially if you are serious about
testing interoperability (which is where you can spend tons of $$$ with
little reward but just say: yes it works), so it may make sense to share
it across different OSes.
I too, wish there was more sharing, but considering that this works for
the Intel driver, there is little incentive in doing this I suppose...
--
Florian
next prev parent reply other threads:[~2017-07-27 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b5d586566a1b523b9be65567b52898e33058a1cf.1500660210.git.>
2017-07-27 0:40 ` [Intel-wired-lan] [PATCH] igb: support BCM54616 PHY Brown, Aaron F
2017-07-27 15:37 ` Andrew Lunn
2017-07-27 17:41 ` Jonathan Toppins
2017-07-27 18:15 ` Andrew Lunn
2017-07-27 17:57 ` Florian Fainelli [this message]
2017-07-27 18:35 ` Wyborny, Carolyn
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=76c8ea56-8e4e-a85c-abe5-695b46c99308@gmail.com \
--to=f.fainelli@gmail.com \
--cc=aaron.f.brown@intel.com \
--cc=andrew@lunn.ch \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linville@tuxdriver.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