[dpdk-dev] [PATCH] net/e1000: add minimum support for Broadcom 54616 PHY

Lu, Wenzhuo wenzhuo.lu at intel.com
Thu Jan 11 09:30:16 CET 2018


Hi Chas,

> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Chas Williams
> Sent: Thursday, December 7, 2017 7:55 AM
> To: dev at dpdk.org
> Cc: skhare at vmware.com; Charles (Chas) Williams <ciwillia at brocade.com>;
> Chas Williams <chas3 at att.com>
> Subject: [dpdk-dev] [PATCH] net/e1000: add minimum support for Broadcom
> 54616 PHY
> 
> From: "Charles (Chas) Williams" <ciwillia at 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 at 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.



More information about the dev mailing list