From owner-freebsd-mobile@FreeBSD.ORG Fri Oct 10 06:59:34 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E083916A4B3 for ; Fri, 10 Oct 2003 06:59:34 -0700 (PDT) Received: from mx3.absolight.com (mx3.absolight.net [212.43.217.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA62243F3F for ; Fri, 10 Oct 2003 06:59:31 -0700 (PDT) (envelope-from mat@FreeBSD.org) Received: by mx3.absolight.com (Postfix, from userid 1007) id DB17D2A26; Fri, 10 Oct 2003 15:59:30 +0200 (CEST) X-Original-To: freebsd-mobile@freebsd.org Received: from andromede.reaumur.absolight.net (andromede.reaumur.absolight.net [212.43.217.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx3.absolight.com (Postfix) with ESMTP id 26A3C29F3; Fri, 10 Oct 2003 15:59:30 +0200 (CEST) Date: Fri, 10 Oct 2003 15:59:24 +0200 From: Mathieu Arnold To: freebsd-mobile@freebsd.org Message-ID: <278796428.1065801563@andromede.reaumur.absolight.net> In-Reply-To: 101020031349.2735.1cfb@comcast.net References: 101020031349.2735.1cfb@comcast.net X-Mailer: Mulberry/3.1.0b8 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========6CD9E18E50C44B983914==========" cc: jphurl@comcast.net Subject: Re: Broadcom 4401 driver X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Oct 2003 13:59:35 -0000 --==========6CD9E18E50C44B983914========== Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline +-le 10/10/2003 13:49 +0000, jphurl@comcast.net =E9crivait : | Hi, |=20 | I was wondering if anybody had tried the Broadcom 4401 driver on | a Dell 2400 Desktop machine? It has a 2.4 Mhz P4,=20 |=20 | If I enable the SMP & APIC_IO options the driver never receives any | interrupts. Note that the Broadcom chip is functional in that I can | send packets out, bu unfortunately I never receive any interrupts. |=20 | If I turn off those options (they are tied together essentially) the=20 | driver works.=20 |=20 | Note that on a Dell 2350, which also has a P4, the driver works as well | (with those options). |=20 | Turning off the APIC_IO option essentially makes the interrupt scheme = look | like a traditional 8259A PIC. With APIC_IO enabled, interrupts get | delivered from the APIC IO device to the Local APIC when an interrupt | occurs. |=20 | Any ideas would be most appreciated. |=20 | Thanks. |=20 | -- Jim |=20 | P.S. The driver works great on the 2350. I ftp to/from it all the time | and the performance is great. I won't be of any help, I'm using it in a few asus pundit boxes, and they're only celeron 1.8G (but they work great though). --=20 Mathieu Arnold --==========6CD9E18E50C44B983914========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (MingW32) iD8DBQE/hrs/qYYpzGz/vmcRAjOoAJ0Sq8gl0S5xsr6Q/BWOTsrl+5V9/QCfau1l lezujTGGfs/j0GAjsELjwGk= =wT5z -----END PGP SIGNATURE----- --==========6CD9E18E50C44B983914==========--