From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: Chas Williams <3chas3@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "skhare@vmware.com" <skhare@vmware.com>,
"Charles (Chas) Williams" <ciwillia@brocade.com>,
Chas Williams <chas3@att.com>
Subject: Re: [dpdk-dev] [PATCH] net/e1000: add minimum support for Broadcom 54616 PHY
Date: Thu, 11 Jan 2018 08:30:16 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B70E3FC@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20171206235528.29746-1-3chas3@gmail.com>
Hi Chas,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Chas Williams
> Sent: Thursday, December 7, 2017 7:55 AM
> To: dev@dpdk.org
> Cc: skhare@vmware.com; Charles (Chas) Williams <ciwillia@brocade.com>;
> Chas Williams <chas3@att.com>
> Subject: [dpdk-dev] [PATCH] net/e1000: add minimum support for Broadcom
> 54616 PHY
>
> From: "Charles (Chas) Williams" <ciwillia@brocade.com>
>
> If we find a Broadcom 54616, handle as a e1000_phy_none assuming that
> the NIC reset has initialized the PHY to a sane state.
>
> Signed-off-by: Chas Williams <chas3@att.com>
> b/drivers/net/e1000/base/e1000_defines.h
> index dbc2bbb..e2101c1 100644
> --- a/drivers/net/e1000/base/e1000_defines.h
> +++ b/drivers/net/e1000/base/e1000_defines.h
> @@ -1274,6 +1274,7 @@ POSSIBILITY OF SUCH DAMAGE.
> #define I350_I_PHY_ID 0x015403B0
> #define I210_I_PHY_ID 0x01410C00
> #define IGP04E1000_E_PHY_ID 0x02A80391
> +#define BCM54616_E_PHY_ID 0x03625D10
TBH, normally we don't change the base code. I checked the kernel driver and don't find this PHY either. May I ask if it's an Intel NIC and what's the device ID? Thanks.
next prev parent reply other threads:[~2018-01-11 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 23:55 Chas Williams
2017-12-07 0:00 ` Chas Williams
2018-01-11 8:30 ` Lu, Wenzhuo [this message]
2018-01-11 17:57 ` Chas Williams
2018-01-15 1:11 ` Lu, Wenzhuo
2018-01-15 13:01 ` Chas Williams
2018-01-18 0:39 ` Lu, Wenzhuo
2018-05-08 1:48 ` Zhang, Helin
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=6A0DE07E22DDAD4C9103DF62FEBC09093B70E3FC@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=ciwillia@brocade.com \
--cc=dev@dpdk.org \
--cc=skhare@vmware.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).