From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 29 00:52:20 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD7F837B401; Tue, 29 Jul 2003 00:52:20 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D0C543F75; Tue, 29 Jul 2003 00:52:20 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc0dr.dialup.mindspring.com ([209.86.1.187] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19hPHD-0005R0-00; Tue, 29 Jul 2003 00:52:08 -0700 Message-ID: <3F262766.4DE637F4@mindspring.com> Date: Tue, 29 Jul 2003 00:51:02 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Joe Marcus Clarke References: <3F254CCB.8030403@aeefyu.net> <1059415694.710.31.camel@gyros> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4824a24ac298a2cc2736aa44eeb21143c3ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: Aeefyu cc: freebsd-hackers@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: BCM4401 Support for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jul 2003 07:52:21 -0000 Joe Marcus Clarke wrote: > On Mon, 2003-07-28 at 12:18, Aeefyu wrote: > > i.e. Broadcom 440x NIC support for FreeBSD 4.x and 5.x (as found on > > latest Dell's Notebooks - mine is a 8500) > > > > Would anyone be so kind to enlighten me on the the current status? > > Last I heard of developments being made was end of June. > > This was forwarded to me from Greg Lehey. The dcm driver works okay for > me, but I had to hack it for some new bus dma changes. I have noticed a > few issues of slowness with it when using it in a more "normal" sense > (i.e. using it to read mail, ssh to machines, etc.). Most likely, the interactive performance is a result of the RX packet coelescing, with a timer set to too long an interval. In general, it's probably an easy adjustment to make. I notice that he also says he didn't know what to add into some of the timer and media routines, so that could be part of the issue as well (e.g. if it's getting wedged and having to unwedge itself). BTW: As a rule of thumb, if you don't know what to put in a timer or media routine, put a printf() there. It will likely annoy someone into fixing it. 8-). -- Terry