From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: Chas Williams <3chas3@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"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, 18 Jan 2018 00:39:55 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B712A4A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CAG2-GkmBU7_cfTpnshFPNDc5w+c6FgrvFWDKG5sK7WwM_FqJhw@mail.gmail.com>
Hi Chas,
Thanks for your info and the patch. I think we should have it.
Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com<mailto:wenzhuo.lu@intel.com>>
Best regards
Wenzhuo Lu
From: Chas Williams [mailto:3chas3@gmail.com]
Sent: Friday, January 12, 2018 1:57 AM
To: Lu, Wenzhuo <wenzhuo.lu@intel.com>
Cc: dev@dpdk.org; 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
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.
next prev parent reply other threads:[~2018-01-18 0:41 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
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 [this message]
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=6A0DE07E22DDAD4C9103DF62FEBC09093B712A4A@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).