summaryrefslogtreecommitdiffstats
path: root/sys
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2003-03-17 13:19:28 +0000
committerimp <imp@FreeBSD.org>2003-03-17 13:19:28 +0000
commitcc6a784ca96ec28686595a8e482eeeca31139bb2 (patch)
treeea203bdcf699eaf9f72678fc4aba26b189ac3b6e /sys
parent90f136c592dc7e5ed9c6ed2c80de267ef1ed74d6 (diff)
downloadFreeBSD-src-cc6a784ca96ec28686595a8e482eeeca31139bb2.zip
FreeBSD-src-cc6a784ca96ec28686595a8e482eeeca31139bb2.tar.gz
Remove bogus KASSERT. The 802.11 layer and the resume from suspend
code both seem to call wi_start (directly or via the if_start pointer) without checking to see if OACTIVE is 0. In addition, I think that with the use of 3 transmit buffers this routine can be called with OACTIVE set, but I might be mistaken about that (and it doesn't matter). Reviewed by: sam Noticed by: imp, alfred, ambrisko
Diffstat (limited to 'sys')
-rw-r--r--sys/dev/wi/if_wi.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/sys/dev/wi/if_wi.c b/sys/dev/wi/if_wi.c
index c0fc9b4..7a12be8 100644
--- a/sys/dev/wi/if_wi.c
+++ b/sys/dev/wi/if_wi.c
@@ -839,8 +839,6 @@ wi_start(struct ifnet *ifp)
WI_UNLOCK(sc);
return;
}
- KASSERT((ifp->if_flags & IFF_OACTIVE) == 0,
- ("wi_start: if_flags %x\n", ifp->if_flags));
memset(&frmhdr, 0, sizeof(frmhdr));
cur = sc->sc_txnext;
OpenPOWER on IntegriCloud