From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ishizaki Kou <kou.ishizaki@toshiba.co.jp>
Cc: netdev@vger.kernel.org, jgarzik@pobox.com, jim@jklewis.com,
linuxppc-dev@ozlabs.org
Subject: Re: spidernet: dynamic phy setup code
Date: Mon, 05 Feb 2007 11:08:07 +1100 [thread overview]
Message-ID: <1170634087.2620.69.camel@localhost.localdomain> (raw)
In-Reply-To: <200702021020.l12AKLrS011304@toshiba.co.jp>
> We use bcm5461. There is a possibility that we don't know the appropriate
> setting which is applicable for both type of switches.
Have you tested the existing 54xx code in sungem_phy.c ? We use that
with 5462 at least in K2 and all sorts of 54xx chips and it works
fine... Just setup the right advertisement bits and call setup_aneg in
the PHY ops. You don't even need to implement the "forced" fallback code
that is in sungem. It's not necessary with most broadcom PHYs as they do
that themselves, just setup aneg and poll the link from a timer, that's
it. Once you get a link, then setup your GMACMODE based on the link
speed.
I don't have the datasheet of the 5461 at hand but I doubt it's any
different... Like other Broadcom 54xx PHYs, it might need some special
initialization code to work around firmware bugs though...
> We didn't investigate for the detail, but we met the following phenomena.
> 1. When auto-neg starts with Gbps setting and ethernet card is connected to
> a 100Mbps switch, LINK is not detected.
> 2. When auto-neg starts with 100/10Mbps setting and ethernet card is
> connected to Gbps switch, LINK is detected (poll_link() succeeds), but
> the network is not available.
That is very strange... I would need to review your code in more details
or eventually have HW access to run my own experiments, but none of this
should happen if things are setup properly. Also avoid relying on the
link interrupt, it's a known cause of trouble. Just poll.
Ben.
next prev parent reply other threads:[~2007-02-05 0:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 13:09 spidernet: dynamic phy setup code Jens Osterkamp
2007-01-26 17:58 ` Linas Vepstas
[not found] ` <200701262150.52882.jens@de.ibm.com>
2007-01-26 22:15 ` Linas Vepstas
2007-01-26 22:30 ` Jens Osterkamp
2007-01-26 20:21 ` Benjamin Herrenschmidt
2007-02-01 10:50 ` Jens Osterkamp
2007-02-01 8:05 ` [Cbe-oss-dev] " Ishizaki Kou
2007-02-01 11:04 ` Jens Osterkamp
2007-02-02 10:20 ` Ishizaki Kou
2007-02-05 0:08 ` Benjamin Herrenschmidt [this message]
2007-02-02 10:29 ` [RFC/PATCH 2.6.20-rc6 1/4] spidernet: autoneg support for Celleb Ishizaki Kou
2007-02-02 10:30 ` [RFC/PATCH 2.6.20-rc6 2/4] spidernet: load firmaware when open Ishizaki Kou
2007-02-02 10:31 ` [RFC/PATCH 2.6.20-rc6 3/4] spidernet: add support for Celleb Ishizaki Kou
2007-02-02 10:33 ` [RFC/PATCH 2.6.20-rc6 4/4] spidernet: remove txram full logging Ishizaki Kou
2007-02-04 23:44 ` [Cbe-oss-dev] spidernet: dynamic phy setup code Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2007-02-01 7:54 kou.ishizaki
2007-02-06 10:42 ` spidernet: dynamic phy setup code Ishizaki Kou
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=1170634087.2620.69.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=jim@jklewis.com \
--cc=kou.ishizaki@toshiba.co.jp \
--cc=linuxppc-dev@ozlabs.org \
--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).