00:14.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I354 [8086:1f41] (rev 03)
I am not clear on the status of the document I have. Here is a link to a similar product: https://people.ucsc.edu/~warner/Bufs/AG6248.pdf -- I have the 7648c which is somewhat similar to the 6248c as far as the "out of band" ports. On Sun, Jan 14, 2018 at 8:11 PM, Lu, Wenzhuo <wenzhuo...@intel.com> wrote: > Hi Chas, > > 1, Would you like to use this CLI “lspci -nn | grep Eth” to get the device > ID of the NIC? > > 2, You mentioned “the doc of the platform”. Is it public? If so, could you > tell me the link? Just want to understand more about it. > > Thanks. > > > > > > Best regards > > Wenzhuo Lu > > > > *From:* Chas Williams [mailto:3ch...@gmail.com] > *Sent:* Friday, January 12, 2018 1:57 AM > *To:* Lu, Wenzhuo <wenzhuo...@intel.com> > *Cc:* dev@dpdk.org; skh...@vmware.com; Charles (Chas) Williams < > ciwil...@brocade.com>; Chas Williams <ch...@att.com> > *Subject:* Re: [dpdk-dev] [PATCH] net/e1000: add minimum support for > Broadcom 54616 PHY > > > > I derived that value by observing what the ixgbe finds when loading on my > platform. The docs for the platform say that the attached PHY is a > Broadcom 54616. I couldn't find any documentation on this PHY to determine > what this value is (i.e. is it really some sort of ID string for that > PHY). I almost suspect that the ixgbe is reading some registers on the > PHY that just happen to contain this value after reset. > > > > Supposedly it's similar to the 54618 but that really doesn't provide much > more information. The bnx2x has a driver for the 54618 and nothing that > looks similar to that string. >
