Age | Commit message (Collapse) | Author |
|
remove long disabled radio devices
ok deraadt
|
|
ok dlg@
|
|
ok mikeb@
|
|
ok kettenis@
|
|
|
|
Tested by procter@ on RT2860 and by me on RT2790 and RT3090.
Ported from FreeBSD by James Hastings.
|
|
So set the appropriate scan capability flags in the ic.
ok sthen@
|
|
|
|
Part of a larger patch by James Hastings.
|
|
So set the appropriate scan capability flags in the ic.
ok sthen@
|
|
corresponding bit in the iwm(4) Tx command regardless of frame length.
ok sthen@
|
|
value.
Specs from mikeb@, ok dlg@
|
|
IWM_CMD_* values are bit flags. The same was done 2 years ago
in Linux git commit a10229271946731959b2269370d0492d88cfab23.
|
|
de is amazing(tm). it really should be cut back and simplified a bit.
|
|
drivers that fill that field in too.
quad types are going away.
|
|
Lets Bacula find the end of medium on LTO5 drive.
Reported & fix tested by Kor son of Rynar.
ok mikeb@ deraadt@
|
|
interface marked UP and scheduling the init task. Matches iwn(4) behaviour.
|
|
|
|
|
|
Repairs urtwn(4) on macppc. Problem reported by juanfra@.
ok millert@ deraadt@
|
|
ok mpi@
|
|
the stack while associated, which in turn makes it possible to keep track of
HT protection changes.
ok mpi@
|
|
Makes running monitor mode over extended periods of time much less annoying.
ok benno@
|
|
of HT protection changes while associated.
HT protection affects behaviour on Tx but is configured along with Rx settings
(because Intel likes it that way). And our previous iwn_update_htprot()
implementation had a bug where it would accidentally clear bits which enable
CCK rates for Rx. The Intel Wireless-N 2200 chip accordingly stopped receiving
some frames (most notably broadcast frames) and the link broke down.
Also, restore the power-saving level after updating the Rx config (like
Linux does), and add some DELAYs for good measure to ensure the firmware
has time to process asynchronous commands we send.
tested by myself and mlarkin@
ok mlarkin@
|
|
This should hopefully help people reporting errors with SB700.
From FreeBSD, ok kettenis@, krw@
|
|
For virtio devices, ignore the black/white-listing depending on the PCI
bridge. This enables MSI-X with qemu's old "82441FX" pci-bridge.
Suggested by kettenis@
|
|
Tx aggregation), instead of the maximum (63 frames). Tx aggregation should
already be disabled, so this change should be a no-op. It just avoids any
side effects in case the firmware happens to interpret the limit we set here.
ok mpi@
|
|
data frames above a certain length, but we were setting it for !data frames
above a certain length, which makes no sense at all. Found while comparing
our driver's Tx code to iwlwifi.
ok mpi@
|
|
frames the same number of times as Linux iwlwifi does.
|
|
This increases performance for interrupt heavy loads.
While suspend/resume support for MSI-X is missing, this is also missing for
virtio. So no new issue there.
Currently, qemu's old "82441FX" pci-bridge is still blacklisted for MSI. But
MSI-X is used if qemu is started with "-M q35".
|
|
The only way to ensure that the device does not do DMA for the timed out
request is a device reset.
Also increase the timeout to 15s
|
|
This describes more accurately what it is good for.
Also introduce a virtio_poll_intr macro.
|
|
For MSI-X (and also possibly for other transports), the interrupt
handler must do different things. Move it out of virtio.c and into
virtio_pci.
ARM part tested by patrick@
|
|
updates with some iwn chips, such as the 2200. Reported by mlarkin and krw.
|
|
early during startup, e.g. where the BSSID for the MAC context is copied from.
Pointed out by Imre Vadasz.
|
|
firmware based on information from the wireless stack. Letting the
firmware deal with these details by itself seems to work better.
Fixes association issues with 8260 hardware for me and Bryan Vyhmeister.
Also tested by jcs@.
|
|
picking a rate from the firmware RS table. This matches what other drivers do.
Also, pass the correct Tx rate to BPF (tcpdump) for 5GHz, and don't loop over
CCK rates when building the Link-Quality command's RS table for 5GHz.
tested by myself and jcs@
|
|
This means we won't sleep and wait for the firmware to send an interrupt
when it's done processing the command. For unknown reasons, sometimes the
firmware never wakes the driver after a phy db command so the driver gives
up partway through the hardware init sequence.
We already have a DELAY in place after each phy db command we send to give
the firmware some time for processing, so skipping the sleep is not expected
to cause problems. If it does, we'll have to revisit this change.
For now, this change makes iwm(4) work better in bsd.rd.
Problem reported by Remi Locherer on bugs@, and confirmed by kettenis@.
Lots of help with testing and ok tb@
|
|
ok tb@ earlier version
|
|
Patch by Imre Vadasz.
|
|
in the file sys/dev/ic/rtwn.c. This reduces kernel bloat and will make it
easier to have both drivers benefit from future enhancements.
ok mpi@
|
|
This mostly copies r88e support code to ic/rtwn.c and moves some functions
which are not trivial to merge with USB counterparts back to pci/if_rtwn.c.
ok mpi@
|
|
I hope this will fix problems due to collisions and interference.
tested by tb@ and Marcus MERIGHI
ok tb@
|
|
sending multicast filter and STA settings during association.
Makes ARP and inet6 autoconf work again.
ok kettenis@
|
|
register. Second, correctly decode the table sizefromits contents.
First issue pointed out by David Hill (with the help of clang). Second
issue spotted after seeing a diff from Christiano Hasbaert.
|
|
never did the handoff between the BIOS and the OS correctly.
Should make xhci(4) usable on machines with xHCI BIOS support like most
of the recent DELL.
Tested by Hrvoje Popovski and David Hill.
ok kettenis@, mikeb@
|
|
|
|
it NVMe.
samsung do the same.
pointed out by Evgeniy Sudyr who has a SSD 750 using the same id as the DC
parts.
|
|
ok mpi@
|
|
Patch by Imre Vadasz.
|