Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S262274AbSJARRe>; Tue, 1 Oct 2002 13:17:34 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S262271AbSJARRH>; Tue, 1 Oct 2002 13:17:07 -0400
Received: from mg03.austin.ibm.com ([192.35.232.20]:40360 "EHLO
	mg03.austin.ibm.com") by vger.kernel.org with ESMTP
	id <S262262AbSJARQM>; Tue, 1 Oct 2002 13:16:12 -0400
Date: Tue, 1 Oct 2002 12:19:19 -0500 (CDT)
From: Kent Yoder <key@austin.ibm.com>
To: Jeff Garzik <jgarzik@pobox.com>
cc: Felipe W Damasio <felipewd@elipse.com.br>, <linux-kernel@vger.kernel.org>,
       <tsbogend@alpha.franken.de>
Subject: Re: [PATCH] pcnet32 cable status check
In-Reply-To: <3D99D640.8030301@pobox.com>
Message-ID: <Pine.LNX.4.44.0210011211130.14632-100000@ennui.austin.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 710
Lines: 19


>Felipe W Damasio wrote:
>>     Also, you shouldn't need the timer stuff to keep track of link change.
>> Just the mii_check_media and netif_carrier_{on|off} and you should be fine.
>
>That depends on the hardware, specifically the presence of a reliable 
>link interrupt....

  Yeah, there's no interrupt generated by the cable being taken out on the 
card I am testing with, a PCnet/FAST III 79C975. I am looking around for 
another in the series though..

Kent

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/