netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Andy Fleming <afleming@freescale.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH] phylib: fix forced mode misbehaviour for aneg off case
Date: Thu, 3 Jul 2008 22:11:18 +0400	[thread overview]
Message-ID: <20080703181118.GA30139@polina.dev.rtsoft.ru> (raw)
In-Reply-To: <20080703104143.6620e99f@extreme>

On Thu, Jul 03, 2008 at 10:41:43AM -0700, Stephen Hemminger wrote:
> On Thu, 3 Jul 2008 21:16:14 +0400
> Anton Vorontsov <avorontsov@ru.mvista.com> wrote:
> 
> > With disabled autonegotiation and link absence, phylib will place phy
> > into the forcing mode, thus will start calling phy_force_reduction().
> > That means that for the drivers that are using phylib we can't actually
> > set fixed speed for the link.
> > 
> > For example:
> > 
> > # ethtool -s eth0 autoneg off speed 1000
> 
> FYI autonegotiation is required in gigabit mode per 802 spec.

Thanks for the information. FWIW, that behaviour observed for
speed 100 or speed 10, too.

As for gbit, this is interesting indeed. If we're not permitted to
disable aneg, how could we force the PHY to use gigabit, so that it
will not try to downgrade? I mean ethtool option.

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

  reply	other threads:[~2008-07-03 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 17:16 [PATCH] phylib: fix forced mode misbehaviour for aneg off case Anton Vorontsov
2008-07-03 17:41 ` Stephen Hemminger
2008-07-03 18:11   ` Anton Vorontsov [this message]
2008-07-03 19:18     ` Ben Hutchings

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=20080703181118.GA30139@polina.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.com \
    --cc=afleming@freescale.com \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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).