summaryrefslogtreecommitdiffstats
path: root/sys/fs/procfs/procfs_status.c
diff options
context:
space:
mode:
authorwpaul <wpaul@FreeBSD.org>1999-01-05 00:59:08 +0000
committerwpaul <wpaul@FreeBSD.org>1999-01-05 00:59:08 +0000
commit169d9aa40517d0edd12b626c3f37bd10f5caca72 (patch)
treee338b1b5a1bc9c0abde7ddfc54d56931c86f4eee /sys/fs/procfs/procfs_status.c
parent6abb5831186d3538e25c374d63ef754cedc8e2dd (diff)
downloadFreeBSD-src-169d9aa40517d0edd12b626c3f37bd10f5caca72.zip
FreeBSD-src-169d9aa40517d0edd12b626c3f37bd10f5caca72.tar.gz
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.
Diffstat (limited to 'sys/fs/procfs/procfs_status.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud