From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S932143AbVH3Wdy@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932143AbVH3Wdy (ORCPT <rfc822;willy@w.ods.org>);
	Tue, 30 Aug 2005 18:33:54 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751409AbVH3Wdy
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 30 Aug 2005 18:33:54 -0400
Received: from smtp.osdl.org ([65.172.181.4]:56228 "EHLO smtp.osdl.org")
	by vger.kernel.org with ESMTP id S1751373AbVH3Wdx (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 30 Aug 2005 18:33:53 -0400
Date: Tue, 30 Aug 2005 15:29:08 -0700
From: Stephen Hemminger <shemminger@osdl.org>
To: Steve Kieu <haiquy@yahoo.com>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
       Daniel Drake <dsd@gentoo.org>, Steve Kieu <haiquy@yahoo.com>,
       linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems
Message-ID: <20050830152908.1dc24339@dxpl.pdx.osdl.net>
In-Reply-To: <20050830214937.22956.qmail@web53604.mail.yahoo.com>
References: <20050830140516.316e9695@dxpl.pdx.osdl.net>
	<20050830214937.22956.qmail@web53604.mail.yahoo.com>
X-Mailer: Sylpheed-Claws 1.9.13 (GTK+ 2.6.7; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 31 Aug 2005 07:49:37 +1000 (EST)
Steve Kieu <haiquy@yahoo.com> wrote:

> 
> --- Stephen Hemminger <shemminger@osdl.org> wrote:
> 
> > You have a version of the Marvell Yukon that was
> > affected
> > by a fix in 2.6.13.
> > 	skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
> > 
> > Both the skge and sk98lin driver were fixed to check
> > for this.
> > Without the fix, the chip will be in the wrong power
> > mode.
> > 
> > The version of sk98lin driver from SysKonnect
> > already had the
> > fix, so if your distro used that one, it would have
> > the reset
> > the power mode as needed.
> 
> I am afraid not. The last time, I reproduced the
> problem using the latest sk98lin driver from
> SysKonnect  (run create patch and patch the kernel
> 2.6.13). Problem still there. The file I got from
> sysconnect is:
> 
> install-8_23.tar.bz2

Just look for references to CHIP_REV_YU_LITE_A3 in the driver
	sk98lin/skgeinit.c and sk98lin/skxmac2.c
The comparison should always be:
	pAC->GIni.GIChipRev >= CHIP_REV_YU_LITE_A3
otherwise it will not correctly take chip out of powerdown (coma) mode.