From: Ben Hutchings <bhutchings@solarflare.com>
To: Eilon Greenstein <eilong@broadcom.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
yanivr@broadcom.com
Subject: Re: [RFC] Add clause 45 ioctl
Date: Tue, 28 Apr 2009 14:22:11 +0100 [thread overview]
Message-ID: <1240924931.3200.3.camel@achroite> (raw)
In-Reply-To: <1240913334.8347.6.camel@lb-tlvb-eliezer>
On Tue, 2009-04-28 at 13:08 +0300, Eilon Greenstein wrote:
> Hi,
>
> This patch adds clause 45 definitions to the mii.h. This will allow
> enhancing the networking device drivers ioctl to handle clause 45
> related operations just as it can handle clause 22 commands today. Since
> clause 45 requires additional 16 bits for the bank address,
No, DEVAD is only 5 bits.
> the clause
> 22 structure cannot be used. The motivation is to allow user space
> applications to access PHY registers in clause 45.
>
> I'm sending this as RFC - if anyone has alternative suggestions on how
> user space application can access the PHY, I would appreciate it.
[...]
I was working on an alternate interface that would use the existing
structure and ioctls. There are at least two drivers (cxgb3 and sfc)
that already do this, though they currently pack PRTAD and DEVAD
differently in the phy_id field.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2009-04-28 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 10:08 [RFC] Add clause 45 ioctl Eilon Greenstein
2009-04-28 13:22 ` Ben Hutchings [this message]
2009-04-30 15:05 ` Eilon Greenstein
2009-04-30 15:49 ` Ben Hutchings
2009-04-30 16:21 ` Eilon Greenstein
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=1240924931.3200.3.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=yanivr@broadcom.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).