| Age | Commit message (Collapse) | Author |
|---|
|
and unused.
|
|
should shrink the kernel somewhat. For some strange reason I was unaware
of this api when I pulled in these changes.
tested by myself and Paul de Weerd, thanks!
|
|
|
|
|
|
|
|
struct and pack all other hardware structs which have been forgotten.
|
|
that ieee80211.h contains only definitions that are part of the
802.11 standard and not constants used internally by net80211.
because channels attributes are exported to userland through the
radiotap BPF interface, add the definitions to ieee80211_radiotap.h
too (which must be kept in sync with what is used in net80211).
also, do not export combinations of channel attributes to userland
so that noone get stupid ideas.
|
|
|
|
|
|
|
|
use it in drivers that leave the 802.11 FCS in frames
passed to radiotap BPF. otherwise, userland has no way
to know if FCS is included or not as it depends on drivers.
this is required by some ports (aircrack).
requested by dhill@
|
|
IEEE80211_ACK_LEN instead of IEEE80211_MIN_LEN for ZYD_MIN_RXBUFSZ
and ZYD_MIN_FRAGSZ.
silence some warnings while i'm there.
change ZYD_FILTER_BSS to use the same value as the vendor's driver
that contains some magic (undocumented) bits.
|
|
since we pass received management frames to net80211, net80211
may send replies (like deauth/disassoc), so we just call
IF_PURGE(&ic->ic_mgtq) in {ipw,iwi}_start just to be on the
safe side of things (so we don't leak mbufs).
|
|
bwi_node structure (containing the rate control state).
because bwi(4) does not support HostAP or IBSS modes there is
no need to maintain a per-node rate control state, so we could
as well store it in bwi_softc but that will allow for future
improvements.
pointed out by Taylor R Campbell (campbell AT mumble DOT net)
on tech@
|
|
remove IBSS and HostAP support from net80211 and 802.11 drivers.
it can be used to shrink RAMDISK kernels for instance (like what
was done for wi(4)).
it also has the benefit of highlighting what is specific to IBSS
and HostAP modes in the code.
the cost is that we now have two code paths to maintain.
|
|
Malicious PPPoE discovery packets could cause the kernel to
crash.
From canacar@ and inspired by the original fix from NetBSD.
ok canacar@
|
|
|
|
|
|
|
|
|
|
there reorder fields in the struct to make it shorter on 64 bit archs.
panic reported by jasper@
thanks to miod@ for helping me debug this down
|
|
1. If bus_dmamap_load_mbuf() fails because there are not enough
segments in the map, defrag the mbuf.
2. If there are not enough free (hardware ring) descriptors, set
IFF_OACTIVE and keep the packet on the queue.
3. If there is some other resource starvation that makes
bus_dmamap_load_mbuf() or defragmentation fail, drop the packet.
Don't set IFF_OACTIVE, since the Tx ring could be empty and we'd be
stuck.
4. Only pass packets that are actually handed off to the hardware to
BPF. Do so before handing them off to the hardware to make sure
the packet isn't freed behind our back.
ok dlg@
|
|
to button #5.
|
|
ok deraadt@
|
|
when mopbooting the bootblocks because one trashed the ones on disk by
accident), be sure to use the proper BDEV_SDx rpb device type value,
depending on the type of onboard controller. Crank version.
|
|
"looks sane to me" otto@, ok miod@
|
|
|
|
|
|
pf_pkt_addr_changed. atm just clears the state key pointer.
calling this is cleaner than having other parts of the stack clearing
pointers in the pf part of the mbuf packet header directly.
|
|
|
|
|
|
|
|
|
|
together with the previous commits by jsing@, OpenBSD/sgi does USB now.
ok jsing@ miod@
|
|
us to use sgivol on devices which have a sector size != DEV_BSIZE, such as
a CD drive.
ok miod@ krw@
|
|
accessors to OpenBSD/sgi.
ok miod@
|
|
ok miod@ jasper@
|
|
ok miod@
|
|
correct address to write the passed label. Don't spoof partitions
while looking for the address, as this could result in an invalid
label being written out.
"That looks right" deraadt@ "Looks good to me" miod@
|
|
changes, okay beck@, tedu@ and thib@.
|
|
|
|
o attempt to make record work (but silence for now)
from drahn@, ok maja@, drahn@
|
|
has subsystem ids set to the same as the regular ids, so the heuristic does
not work. So look for the TAD,Viper machine name. When we get our hand on
a Bullfrog (with a PCI slot) we will need to revisit this.
ok kettenis
|
|
|
|
|
|
|
|
when switching from gcc 2.95, if not forever.
|
|
|
|
|
|
Preserve it explicitely in dzmctl() and restore it after the DTR update.
(This problem was a real PITA to track down)
|
