[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1169842902.24996.108.camel@localhost.localdomain>
Date: Sat, 27 Jan 2007 07:21:42 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Jens Osterkamp <jens@...ibm.com>
Cc: Ishizaki Kou <kou.ishizaki@...hiba.co.jp>, linuxppc-dev@...abs.org,
netdev@...r.kernel.org, cbe-oss-dev@...abs.org,
Linas Vepstas <linas@...tin.ibm.com>, jgarzik@...ox.com,
James K Lewis <jim@...ewis.com>
Subject: Re: spidernet: dynamic phy setup code
On Fri, 2007-01-26 at 14:09 +0100, Jens Osterkamp wrote:
> This patch modifies the patch submitted by Kou Ishizaki to make it work on the
> blade (http://marc.theaimsgroup.com/?l=linux-netdev&m=116593424505539&w=2).
> Unfortunately I dont have access to a Celleb so I cannot test it there.
>
> The basic logic behind this is simple : when the interface first comes up
> it tries to detect the phy. When the phy is detected, it is initially set up
> to use copper. A timer is set to check the link status in spidernet_link_phy
> using poll_link. If link check fails more than SPIDER_NET_ANEG_TIMEOUT
> times, it switches to fiber link with autonegotiation. If that fails more
> than SPIDER_NET_ANEG_TIMEOUT times, it switches to fiber link with no
> autonegotiation. If that also fails, it goes back to copper, and so forth.
> If the link comes up, it prints the link abilites and we are done.
>
> The name of the phy found attached to the spider chip is reported to the
> user. Hardcoded values for the timeout are moved to #defines. I put in a
> few comments to make the code more readable.
Can't we have a device-tree property indicating wether to use fiber or
copper ?
Ben.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists