All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Ben Hutchings <bhutchings@solarflare.com>, netdev@vger.kernel.org
Subject: Re: PHY down?
Date: Fri, 5 Aug 2011 06:13:09 +0200	[thread overview]
Message-ID: <20110805041309.GB15141@zapo> (raw)
In-Reply-To: <OFEC77B7FA.1BCB17E8-ONC12578E0.0043754B-C12578E0.00441F36@transmode.se>

On Tue, Aug 02, 2011 at 02:24:04PM +0200, Joakim Tjernlund wrote:
> Ben Hutchings <bhutchings@solarflare.com> wrote on 2011/08/02 13:01:08:
> >
> > On Tue, 2011-08-02 at 11:24 +0200, Joakim Tjernlund wrote:
> > > I must be missing something obvious but I cannot find how
> > > to bring eth0's PHY down (link down) from user space.
> > > Tried various settings with ethtool and ifconfig eth0 down but it didn't help.
> >
> > If you configure an interface down, and if the interface is not used for
> > remote management, then some drivers will turn the PHY off.  But there
> > is no general way to control this explicitly.
> 
> OK, when to stop the PHY doesn't seem standardized. Seem logical to me
> to also turn off the PHY when interface is configured down. Perhaps this could
> be agreed upon?
> What does remote management mean? How do I identify if the I/F is used for remote management?
> 
>  Jocke

I'd rather see an explicit way of turning off the PHY. Downing the interface might be
useful without killing the PHY. I've seen PoE switches that kill you when you bring
the link down or reset the PHY after once beeing up, Down/up of interface might become
impossible in some environments if we would standardize on PHY off for interface down.

Maybe an explicit ethtool option?

Cheers

      parent reply	other threads:[~2011-08-05  4:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02  9:24 PHY down? Joakim Tjernlund
2011-08-02 11:01 ` Ben Hutchings
2011-08-02 12:24   ` Joakim Tjernlund
2011-08-02 12:38     ` Ben Hutchings
2011-08-05  4:13     ` Edgar E. Iglesias [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=20110805041309.GB15141@zapo \
    --to=edgar.iglesias@gmail.com \
    --cc=bhutchings@solarflare.com \
    --cc=joakim.tjernlund@transmode.se \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.