From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] patch for Intel igb driver to support broadcom phys
Date: Wed, 30 Dec 2015 23:47:21 -0800 [thread overview]
Message-ID: <1451548041.3348.129.camel@intel.com> (raw)
In-Reply-To: <1831EC2B04379B47B6D129255B9BF2212D34A8D1@SRV-EXMBX2.accton.com.tw>
On Thu, 2015-12-31 at 05:46 +0000, David Yang wrote:
>
> We are bare metal network switch developers who contribute codes
> for OCP ONIE (https://github.com/opencomputeproject/onie).
>
> Up to now, many switches have Intel CPU module with Ethernet?
> controller (i354) which connects to external Broadcom PHY
> (bcm54616s).
> We revised linux igb driver for making the PHY work.
>
> The patch is for linux-4.1.12.??Please help to review the?
> patch for upstream to the igb driver.
Well, first off, this was suggested by guys at Cumulus Networks back in
April of 2015. ?In short, we would support the idea of using the PHYLib
approach. ?I believe i210 and i211 currently uses the PHYLib approach,
so it probably would not take much to extend that approach to the other
devices.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20151230/8dfbdb98/attachment.asc>
prev parent reply other threads:[~2015-12-31 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 5:46 [Intel-wired-lan] [PATCH] patch for Intel igb driver to support broadcom phys David Yang
2015-12-31 7:47 ` Jeff Kirsher [this message]
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=1451548041.3348.129.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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