Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 15 Feb 2002 10:04:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 15 Feb 2002 10:03:59 -0500 Received: from dsl-65-188-226-101.telocity.com ([65.188.226.101]:27910 "HELO fancypants.trellisinc.com") by vger.kernel.org with SMTP id ; Fri, 15 Feb 2002 10:03:46 -0500 Date: Fri, 15 Feb 2002 10:03:42 -0500 From: Jason Lunz To: Jeff Garzik Cc: linux-kernel@vger.kernel.org Subject: Re: Broadcom 5700/5701 Gigabit Ethernet Adapters Message-ID: <20020215150342.GA4347@trellisinc.com> In-Reply-To: <3C6D07B9.596AD49E@mandrakesoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C6D07B9.596AD49E@mandrakesoft.com> User-Agent: Mutt/1.3.27i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org In mlist.linux-kernel, you wrote: > Cuz the driver is a piece of crap, and BroadCom isn't interested in > working with the open source community to fix up the issues. Can you elaborate? What are the issues? I've found the broadcomm driver to be more robust than the in-kernel one for acenic cards. With acenic, I've had a null-pointer deref on SMP and other lockups where I wasn't lucky enough to get an oops. Also, broadcomm-driven cards can be put in a bridge. An acenic/bridge combination will crash the kernel hard when tcp traverses the bridge. > DaveM and I should have something eventually, which will make the > RH-shipped driver irrelevant. that would be oh-so-nice. Do you need cards to play with? I've got a couple of 3com broadcomm-chipset cards I prabably won't be needing. -- Jason Lunz Trellis Network Security j@trellisinc.com http://www.trellisinc.com/ - 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/