From: "Aníbal Almeida Pinto" <anibal.pinto@efacec.com>
To: <netdev@vger.kernel.org>
Subject: [RFC] micrel KSZ8041 disable auto negotiation with fiber
Date: Tue, 19 Jun 2012 15:45:59 +0100 [thread overview]
Message-ID: <4FE090A7.801@efacec.com> (raw)
Hi,
I am working on a custom board based on a OMAP L138 with a KSZ8041TL-FTL
phy that have fibber and copper support.
When using with fibber the board can't connect to a switch, only after
exec :
ethtool -s eth1 speed 100 duplex full autoneg off
the phy get link and start working.
On some switches it appears that autoneg don't work well with fibber,
ethtool reports that its at 10MB/s after exec
ethtool -s eth1 autoneg on
The auto negotiation bit on phy register is disable on start when using
the fibber but Linux don't appear to look at it.
Found a thread [1] that solve the problem but don't appear to be fully
accepted.
The problem is modifying the phy code without interfere with ethtool use.
Any official/accepted solution to this problem ?
Thanks.
[1] - http://marc.info/?l=linuxppc-embedded&m=131107263711714
Aníbal
next reply other threads:[~2012-06-19 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 14:45 Aníbal Almeida Pinto [this message]
2012-06-19 17:08 ` [RFC] micrel KSZ8041 disable auto negotiation with fiber Ben Hutchings
2012-06-19 17:53 ` Aníbal Almeida Pinto
2012-06-19 18:45 ` 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=4FE090A7.801@efacec.com \
--to=anibal.pinto@efacec.com \
--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 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).