public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin E <kevin360@yahoo.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Willy Tarreau <w@1wt.eu>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFT] sky2: yukon-ec-u phy power problems
Date: Wed, 22 Aug 2007 15:37:09 -0700 (PDT)	[thread overview]
Message-ID: <314260.5533.qm@web38904.mail.mud.yahoo.com> (raw)
In-Reply-To: <20070821100713.2867dce3@freepuppy.rosehill.hemminger.net>


--- Stephen Hemminger
<shemminger@linux-foundation.org> wrote:

> The sky2 driver clears some bits in the PHY control
> register, that cause
> the PHY interface to get changed.  Some of these
> deal with voltage and power
> savings as well. This may explain some of the
> failures on Gigabyte DS-3 motherboard.
> 
> The clue to possible problem was looking at why
> loading/unloading sky2 would
> break vendor sk98lin driver (ie what registers
> changed).
> 
> 
> --- a/drivers/net/sky2.c	2007-08-21
> 09:53:41.000000000 -0700
> +++ b/drivers/net/sky2.c	2007-08-21
> 09:53:43.000000000 -0700
> @@ -696,8 +696,8 @@ static void sky2_mac_init(struct
> sky2_hw
>  	int i;
>  	const u8 *addr = hw->dev[port]->dev_addr;
>  
> -	sky2_write32(hw, SK_REG(port, GPHY_CTRL),
> GPC_RST_SET);
> -	sky2_write32(hw, SK_REG(port, GPHY_CTRL),
> GPC_RST_CLR);
> +	sky2_write8(hw, SK_REG(port, GPHY_CTRL),
> GPC_RST_SET);
> +	sky2_write8(hw, SK_REG(port, GPHY_CTRL),
> GPC_RST_CLR);
>  
>  	sky2_write8(hw, SK_REG(port, GMAC_CTRL),
> GMC_RST_CLR);
>  

This appears to have fixed the problem!  I made the
change to the kernel on the broken MB and the link
stayed up.  So I went ahead and made the change to the
kernel on the working one too.   Right now I'm using
netcat to saturate the link and make sure it stays up.
 So far it's looking good, if I have any problems I'll
let you know.

Thanks,
Kevin



       
____________________________________________________________________________________
Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online.
http://smallbusiness.yahoo.com/webhosting 

  reply	other threads:[~2007-08-22 22:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 12:42 Marvell 88E8056 gigabit ethernet controller Kevin E
2007-08-18  0:03 ` Stephen Hemminger
2007-08-18  5:38   ` Willy Tarreau
2007-08-18 11:45     ` Kevin E
2007-08-18 12:17       ` Willy Tarreau
2007-08-18 13:59         ` Kevin E
2007-08-19 16:32           ` Stephen Hemminger
2007-08-19 16:42             ` Kevin E
2007-08-21 17:07               ` [RFT] sky2: yukon-ec-u phy power problems Stephen Hemminger
2007-08-22 22:37                 ` Kevin E [this message]
     [not found]             ` <2456F7EB-000C-4B71-B002-64340DD17BA8@linuxmontreal.com>
2007-08-19 18:34               ` Marvell 88E8056 gigabit ethernet controller Stephen Hemminger
2007-08-19 19:13                 ` Kevin E
2007-08-19 23:04                 ` Eric Preston
2007-08-20  1:15               ` Kevin E
2007-08-20 15:01                 ` Stephen Hemminger

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=314260.5533.qm@web38904.mail.mud.yahoo.com \
    --to=kevin360@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    --cc=w@1wt.eu \
    /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