All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jesse Huang <jesse@icplus.com.tw>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 4/6] IP100A Change search phy addr start form 0
Date: Fri, 18 Aug 2006 07:20:22 -0400	[thread overview]
Message-ID: <44E5A276.3050708@pobox.com> (raw)
In-Reply-To: <1155841636.4532.16.camel@localhost.localdomain>

Jesse Huang wrote:
> From: Jesse Huang <jesse@icplus.com.tw>
> 
> Change search phy addr start form 0
> 
> Change Logs:
>     Change search phy addr start form 0
> 
> ---
> 
>  drivers/net/sundance.c |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> 212cd4ffa21a57300eae4254bf02e5b33b96f544
> diff --git a/drivers/net/sundance.c b/drivers/net/sundance.c
> index 2bde1b3..f63871a 100755
> --- a/drivers/net/sundance.c
> +++ b/drivers/net/sundance.c
> @@ -21,7 +21,7 @@
>  */
>  
>  #define DRV_NAME	"sundance"
> -#define DRV_VERSION	"1.01+LK1.13"
> +#define DRV_VERSION	"1.01+LK1.14"
>  #define DRV_RELDATE	"04-Aug-2006"
>  
>  
> @@ -559,8 +559,9 @@ #endif
>  	/*
>  	 * It seems some phys doesn't deal well with address 0 being accessed
>  	 * first, so leave address zero to the end of the loop (32 & 31).
> +	 * for IP100A the phy should start from 0
>  	 */
> -	for (phy = 1; phy <= 32 && phy_idx < MII_CNT; phy++) {
> +	for (phy = 0; phy <= 32 && phy_idx < MII_CNT; phy++) {
>  		int phyx = phy & 0x1f;
>  		int mii_status = mdio_read(dev, phyx, MII_BMSR);
>  		if (mii_status != 0xffff  &&  mii_status != 0x0000) {

For IP100A, is the phy built into the chip?

For a standard DP83840[A] phy, phy #0 is a "ghost" which mirrors another 
phy.  For this reason, we scan phy #0 last.

Does the above code not work?

	Jeff



  reply	other threads:[~2006-08-18 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 19:07 [PATCH 4/6] IP100A Change search phy addr start form 0 Jesse Huang
2006-08-18 11:20 ` Jeff Garzik [this message]
2006-08-21  5:40   ` Jesse Huang

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=44E5A276.3050708@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=jesse@icplus.com.tw \
    --cc=linux-kernel@vger.kernel.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 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.