Hi Chas,

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

Reply via email to