Age | Commit message (Collapse) | Author |
|
According to https://reviews.freebsd.org/D12429, UDP transmit checksum
offloading doesn't work in Azure when sizeof(IP hdr + UDP hdr + payload)
is greater than 1420 and don't fragment bit isn't set in the IP header.
Instead of peeking into the packet and attempting to fix the fallout, we
restrict UDP checksum offloading to NDIS versions newer than the one used
in Azure (6.30) in an attempt to keep the feature enabled. Unfortunately,
there's no way to tell Azure apart from a standalone Hyper-V to make this
check more precise.
|
|
(I've had this diff locally for a long time on port build machines to
avoid NFS stalls.)
|
|
|
|
|
|
From FreeBSD.
|
|
|
|
|
|
|
|
|
|
D-Link DWA-182 rev D1.
ok stsp@
|
|
clone running guests and take disk-only snapshots, most of the time ending
up with a clean filesystem.
ok dlg@ deraadt@
|
|
interrupt context with assertwaitok(), which does work.
ok dlg@
|
|
usb_transfer_complete, so that if we need to allocate a new one (as in the
case of interrupt endpoints) we will always be able to do so without
allocating a new chunk. Mapping a new chunk involves allocating from the
kernel map, which is not safe to do from interrupt context.
fixes a panic reported by semarie
ok visa@ krw@ (before a last minute tweak)
|
|
Kills "iwm0: unhandled firmware response 0xff/0xb8000010 rx ring" dmesg spam.
Patch by jes@posteo via tech@, who found the corresponding change in Linux:
https://patchwork.kernel.org/patch/9869017/
|
|
linux and add back struct members.
Avoids diffs in inteldrm, libdrm and Mesa >= 17.2.
ok kettenis@
|
|
ok jsg@
|
|
Prevents a deadlock reported by aalm@
|
|
|
|
|
|
ok deraadt@, ratchov@
|
|
|
|
(Bristol Ridge, aka tweaked Carrizo) not to be confused with
Carrizo-L (16h apu).
ok jsg@, mlarkin@
|
|
|
|
|
|
|
|
|
|
|
|
Apparently this can cause a firmware crash during a TX command on 7265 devices.
Why this happens is unclear.
Problem reported and workaround tested by trondd on bugs@
I have verified that hidden SSID APs still work, though we won't be able to
seamlessly roam between them anymore. Seems like a fair trade-off for now.
|
|
The problem happened if we didn't find an AP to connect to after one scan
iteration. The net80211 stack then performs a SCAN -> SCAN transition to
kick off another scan, but the driver treated this transition as a no-op
and remained in SCAN state doing nothing.
To fix this, introduce a flag which keeps track of whether a firmware
scan command is in progress, and start another scan during a SCAN->SCAN
transition if no scan is in progress. Matches what iwm(4) does.
Note that previously (i.e. in 6.2), iwn(4) would always try to start
a new scan regardless of what the firmware was currently doing.
Problem noticed by myself and also by deraadt@
test & ok tb@
|
|
|
|
|
|
|
|
|
|
|
|
like we already do in the code that flushes the BTB.
ok jsg@
|
|
|
|
|
|
|
|
|
|
in passthrough IO requests, which makes AEN processing work on SAS2208
controllers, and since AEN processing works now, enable it again.
tested on SAS2208 (PERC H710P) and SAS3108 (PERC H730), SAS3.5 parts
should work too.
ok dlg@
|
|
never be called to convince compilers and static analysis tools a path
that uses uninitialised memory does not exist.
ok krw@ mpi@
|
|
The account flag `ASU' will no longer be set but that makes suser()
mpsafe since it no longer mess with a per-process field.
No objection from millert@, ok tedu@, bluhm@
|
|
ok krw@ mpi@
|
|
memory regions.
|
|
SDIO function. This is necessary for some SDIO cards that need to be
talked with using smaller block lengths than the maximum supported by
the host controller.
ok kettenis@
|
|
interface for "reading memory" akin to the bus_space(9) API. The
already existing multi interface is used for "reading FIFOs". The
technical difference is that one always reads from the same address
(FIFO) while the other increments the address while reading (memory).
ok kettenis@
|
|
don't fault on strict alignment architectures.
|
|
alignment can be variable, it's better to move taking care of alignment
into the BCDC receive code.
|
|
receive. Did that everywhere else but missed it here.
|
|
|