Age | Commit message (Collapse) | Author |
|
this means packets are consistently counted in one place, unlike the
many and various ways that drivers thought they should do it.
ok mpi@ deraadt@
|
|
|
|
|
|
relying on the newstate task to do so. Fixes races of driver code against
mira timeouts leading to crashes in some situations, e.g. occasionally when
changing channels while the interface is up.
ok procter@
|
|
virtio itself is not PCI, it is a paravirtual bus on top of either PCI
or MMIO (arm). This is the first step of moving the virtio files to
dev/pv. No functional change.
arm kernel changes tested by jsg@ and patrick@
no objections from sf@ mlarkin@
|
|
using it uninitialised in one path.
|
|
OK kettenis@ mlarkin@
|
|
|
|
|
|
While we don't have ACPI in vmm(4), we need a simple way to shutdown
and reboot VMs gracefully but the device also allows to add more
direct communications between host and guest later.
OK mlarkin@
|
|
|
|
OK mlarkin@
|
|
No functional change.
The previous name was chosen at a time when I could not yet anticipate
what this function would really end up doing.
The new name should make this function's purpose more obvious, especially
where it appears at strategic places in driver code.
|
|
The heavy lifting was done by damien@ years ago. I didn't even have
to figure out what the hardware expects, the code was already there.
This driver now supports MCS 0-15 in client and hostap mode.
No Tx aggregation and no 40 MHz channels yet.
tested by vgross@, bmercer@, tb@, jmc@, Vadim Vygonets, Peter Kay
ok bmercer@ tb@ phessler@
|
|
B117-M. From Martin Ziemer.
|
|
OK deraadt@ kettenis@
|
|
radeondrm, using the same scheme as efifb(4).
OK mpi@, visa@, kettenis@
|
|
|
|
ok deraadt
|
|
|
|
Fixes some clang warnings.
ok jsg@
|
|
|
|
#ifdef as the debug code itself. Prevents clang from warning about these
functions being unused.
ok stsp@, deraadt@
|
|
1cd73ff70d13a22faa95db8323382dd6d036554e by Alex Deucher, whose commit
message makes me suspect that Brad Smith mailed us a diff back in 2013
that we ignored.
ok jsg@
|
|
auvia(4). From Michael W. Bombardieri <mb at ii.net>. Thanks.
|
|
Thanks.
|
|
we're not in 11n mode. This will allow tcpdump to show the mode correctly.
ok mpi@
|
|
With help from and OK sf, OK mpi on the previous version.
|
|
Michael W. Bombardieri <mb at ii.net>
|
|
|
|
The nominal maximum Tx rate is now 144Mbit/s (MCS 15, 20MHz channel, SGI).
In practice it's more around 30Mbit/s, though. The most significant limiting
factor is probably lack of Tx aggregation support. (Due to protocol overhead,
reaching the nominal max is pretty much impossible anyway. When shopping wifi
devices, do not believe what stickers on the box are saying; full of lies!)
But APs will send us aggregates, so Rx should be faster than Tx (which was
already the case, just less pronounced).
Tested by phessler@, bmercer@, tb@
ok tb@
|
|
protection from 20MHz-only STAs on a 40MHz channel. We do not support 40MHz
channels yet so there is nothing to protect ourselves from. It is the 40MHz
users who need to start using RTS when a 20MHz-only user shows up.
|
|
The number of retried frames shrinks significantly.
ok tb@
|
|
The problem noticed, fix tested and OK procter@
|
|
it to bpf for tcpdump(8). Fix it so MCS >= 8 get passed on correctly.
ok phessler@
|
|
recording is requested on devices with no ADCs. Many thanks to
Bryan Vyhmeister <bryan at bsdjournal.net> for testing & debugging this.
|
|
Please let me know about any regressions.
Tested by myself, tb@, okan@, jca@, naddy@, mlarkin@
ok tb@ jca@
|
|
|
|
Rename 8086:15a[abce] back to X552, give 8086:15ad a proper moniker
X552/X557-AT and the yet-unreleased parts 8086:15c* are tentatively
named X553.
|
|
|
|
tested by Hrvoje Popovski, thanks!
|
|
Due to insufficient error handling X552 SFP+ card isn't configured
properly on boot when an SFP+ module is not plugged in. As a side
effect the interface becomes completely unusable afterwards.
The issue was discovered and fix tested by Hrvoje Popovski, thanks!
|
|
Should fix "panic: timeout_add: not initialized" reported by danj@
|
|
|
|
Cleanup trailing whitespaces from the previous change while here.
|
|
procter@ has noticed that flow control settings survive module change
when they should be forgotten. It became clear that we're overwriting
the selected FC mode with the requested version instead of keeping
negotiated settings. Tested by procter@.
|
|
Previously only multi-rate fiber modules would disable the TX laser, but
newer Intel driver does it for single rate modules as well. Reminded by
kettenis@, tested by procter@ and Hrvoje Popovski. Thanks!
|
|
|
|
intel use xl710 to refer to 40 gig parts (and 20 for some reason),
and x710 to refer to 10g parts. there's allegedly going to be 25g
parts called xxv710.
i havent included the xl722 parts yet.
im naming the devices by the speed and connector rather than going for
actual intel product names like XL710-QDA1 because other vendors will
use the same chips in product with other names.
intel also put the XL710-QDA1 product id on the XL710-QDA2, which is
a good argument not to use product names too.
|
|
reducing the local diff in libdrm.
We only handle a single master as xorg privdrop has already occurred at
the point where the ioctls are issued.
|