Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 16 Feb 2001 04:32:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 16 Feb 2001 04:32:49 -0500 Received: from orange.csi.cam.ac.uk ([131.111.8.77]:16043 "EHLO orange.csi.cam.ac.uk") by vger.kernel.org with ESMTP id ; Fri, 16 Feb 2001 04:32:41 -0500 Date: Fri, 16 Feb 2001 09:32:34 +0000 (GMT) From: James Sutherland To: Rogier Wolff cc: linux-kernel@vger.kernel.org Subject: Re: 8139 full duplex? In-Reply-To: <200102160858.JAA02472@cave.bitwizard.nl> Message-ID: 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 On Fri, 16 Feb 2001, Rogier Wolff wrote: > > Hi All, > > I have a bunch of computers with 8139 cards. When I moved the cables > over from my hub to my new switch all the "full duplex" lights came on > immediately. That's what you would expect: they will auto-negotiate full duplex, in the same way they would negotiate 10 or 100 Mbit/sec. > Would this mean that the driver/card already were in full-duplex? No, that's not possible. They just automatically configured for the best performance available - in this case, full duplex. > That would explain me seeing way too many collisions on that old hub > (which obviously doesn't support full-duplex). No, it would just prevent your card working. Large numbers of collisions are normal during fast transfers across a hub. James. - 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/