From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 29 01:48:04 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 05EAA37B401; Tue, 29 Jul 2003 01:48:04 -0700 (PDT) Received: from dmlb.org (pc2-cmbg4-6-cust36.cmbg.cable.ntl.com [81.96.76.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04D7C43F75; Tue, 29 Jul 2003 01:48:03 -0700 (PDT) (envelope-from dmlb@dmlb.org) Received: from pc2-cmbg4-6-cust36.cmbg.cable.ntl.com ([81.96.76.36] helo=DJK1Comp) by dmlb.org with smtp (Exim 3.36 #1) id 19hQ8w-0000uL-00; Tue, 29 Jul 2003 09:47:39 +0100 Message-ID: <002601c355ae$100a3240$a7ac77c1@DJK1Comp> From: "Duncan Barclay" To: "Terry Lambert" , "Joe Marcus Clarke" References: <3F254CCB.8030403@aeefyu.net> <1059415694.710.31.camel@gyros> <3F262766.4DE637F4@mindspring.com> Date: Tue, 29 Jul 2003 09:47:36 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4920.2300 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 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 08:48:04 -0000 Hello Terry, From: "Terry Lambert" > 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. It shouldn't be as I set the RX coalescing timer at the same settings as the Linux drivers - and it is set to 1 packet. > 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). Nope - no wedging is going on. It's packet aligment issues - either I'm programming the RX DMA pointers wrong or not adjusting them correctly on receipt. TX is absolutly fine, it can easily max out a 100MB/s link with hardly any CPU load. > 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-). Ta - will do when the RX issues are fixed. > -- Terry > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > >