From: Ben Hutchings <bhutchings@solarflare.com>
To: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
Cc: netdev@vger.kernel.org
Subject: Re: Linux support for 802.3af?
Date: Sat, 13 Mar 2010 04:40:03 +0000 [thread overview]
Message-ID: <1268455203.7439.78.camel@localhost> (raw)
In-Reply-To: <4B9AE62B.6050502@redfish-solutions.com>
On Fri, 2010-03-12 at 18:11 -0700, Philip A. Prindeville wrote:
> On 03/12/2010 05:43 PM, Ben Hutchings wrote:
> > On Fri, 2010-03-12 at 17:01 -0700, Philip A. Prindeville wrote:
> >> I was looking at this Marvell-based 4-port PCI card with PoE and
> >> thinking it would be handy for powering cameras and ip-phones, but don't
> >> remember seeing any kernel support for 802.3af...
> >>
> >> http://www.korenix.com/jetcard-PoE_Universal_PCI_Card-2215-overview.htm
> >>
> >> There's no support for 802.3af, right?
> >
> > The standard MDIO ioctls can be used to access registers 11 and 12 on
> > PHYs with integrated PSE functionality. There is no way of indicating
> > whether a PHY has such functionality, but a flag for this could be added
> > to the mdio_support field of struct ethtool_cmd.
> >
> > Ben.
>
> Well, there's more to it than that, right?
>
> There's a software state machine that's required to go through the
> handshake, there's prioritization and power budgeting, etc. Yes?
>
> What am I missing?
We seem to have contrary expectations of how a PSE would be implemented.
You assume that the CPU would be involved at quite a low level. I
assume that a PSE in a Linux system would be implemented on a peripheral
device and that it would be managed from the host via MDIO (though this
is specified as an optional feature).
Looking at the specs, that particular card is using a Marvell switch
chip which doesn't have any PoE support, so management via MDIO seems
unlikely. If you're curious I suppose you should try to get the driver
from this vendor.
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.
prev parent reply other threads:[~2010-03-13 4:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 0:01 Linux support for 802.3af? Philip A. Prindeville
2010-03-13 0:43 ` Ben Hutchings
2010-03-13 1:11 ` Philip A. Prindeville
2010-03-13 4:40 ` Ben Hutchings [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=1268455203.7439.78.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=philipp_subx@redfish-solutions.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).