From owner-cvs-all Mon Jan 4 16:59:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04295 for cvs-all-outgoing; Mon, 4 Jan 1999 16:59:17 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04284; Mon, 4 Jan 1999 16:59:16 -0800 (PST) (envelope-from wpaul@FreeBSD.org) From: Bill Paul Received: (from wpaul@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id QAA27460; Mon, 4 Jan 1999 16:59:09 -0800 (PST) Date: Mon, 4 Jan 1999 16:59:09 -0800 (PST) Message-Id: <199901050059.QAA27460@freefall.freebsd.org> To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: cvs commit: src/sys/pci if_pn.c if_pnreg.h Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk wpaul 1999/01/04 16:59:09 PST Modified files: sys/pci if_pn.c if_pnreg.h Log: GRRRR! Apparently, the promiscuous mode chip bug which I thought was isolated to revision 33 PNIC chips is also present in revision 32 chips. Cards with rev. 32 chips include the LinkSys LNE100TX and the Matrox FastNIC 10/100. This accounts for all the cards that I have to test with. (I was never able to personally trip the bug on this chip rev, but today one of the guys in the lab did it with the software they're working on for their cellular IP project, which uses BPF and promiscuous mode extensively.) This commit enables the promiscuous mode software workaround code for both revison 32 and revision 33 chips. It's possible all of the PNIC chips suffer from this bug, but these are the only two revs where I know for a fact it exists. Revision Changes Path 1.6 +3 -3 src/sys/pci/if_pn.c 1.4 +2 -1 src/sys/pci/if_pnreg.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message