From: Jonathan Toppins <jtoppins@cumulusnetworks.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 3/3] net: igb: register mii_bus for SerDes w/ external phy
Date: Fri, 15 May 2015 00:08:12 -0400 [thread overview]
Message-ID: <5555712C.5090106@cumulusnetworks.com> (raw)
In-Reply-To: <CAJ+vNU1zFXTnaTi2ME7V6C_ucOukDwVTd3_Ne52DOz_0aHyn3A@mail.gmail.com>
On 5/12/15 6:37 PM, Tim Harvey wrote:
>
> agreed - I will separate this into a different patch. I think
> SIOCGMIIREG/SIOCSMIIREG are useful for debugging and various userspace
> tools like ethtool and others that allow direct mii register access. I'm
> not clear what the general consusus is but there do seem to be many
> ethernet drivers that support SIOCMIIREG including the phylib default
> ioctl handler.
I am on holiday, will get a chance to read over the thread this weekend.
Regards,
-Jon
next prev parent reply other threads:[~2015-05-15 4:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 18:19 [Intel-wired-lan] [PATCH 0/3] igb: add i210/i211 external phy support Tim Harvey
2015-04-30 18:19 ` [Intel-wired-lan] [PATCH 1/3] net: igb: add i210/i211 support for phy read/write Tim Harvey
2015-05-09 1:06 ` Alexander Duyck
2015-05-11 15:26 ` Tim Harvey
2015-05-11 15:45 ` Alexander Duyck
2015-04-30 18:19 ` [Intel-wired-lan] [PATCH 2/3] net: igb: add phy read/write functions that accept phy addr Tim Harvey
2015-05-09 1:07 ` Alexander Duyck
2015-05-11 15:27 ` Tim Harvey
2015-05-11 15:46 ` Alexander Duyck
2015-04-30 18:19 ` [Intel-wired-lan] [PATCH 3/3] net: igb: register mii_bus for SerDes w/ external phy Tim Harvey
2015-05-09 1:05 ` Alexander Duyck
2015-05-11 18:42 ` Tim Harvey
2015-05-11 20:44 ` Alexander Duyck
2015-05-12 22:37 ` Tim Harvey
2015-05-13 6:16 ` Alexander Duyck
2015-05-15 4:08 ` Jonathan Toppins [this message]
2015-05-20 15:46 ` Tim Harvey
2015-05-29 15:26 ` Jonathan Toppins
2015-06-05 15:08 ` Tim Harvey
2015-05-05 2:00 ` [Intel-wired-lan] [PATCH 0/3] igb: add i210/i211 external phy support Jeff Kirsher
2015-05-07 16:40 ` Tim Harvey
2015-05-07 16:57 ` Jeff Kirsher
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=5555712C.5090106@cumulusnetworks.com \
--to=jtoppins@cumulusnetworks.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