Age | Commit message (Collapse) | Author |
|
be generated by version 17 firmware. While at it, declare all known
firmware command groups and all PHY_OPS subcomand ids.
Patch by Imre Vadasz, with tweaks by me
ok patrick@
|
|
All supported firmware versions support IWM_UCODE_TLV_FLAGS_TIME_EVENT_API_V2.
Rename struct iwm_time_event_cmd_v2 to iwm_time_event_cmd, and remove helper
functions for converting from V2 API structs to V1 versions.
Patch by Imre Vadasz
ok patrick@
|
|
IWM_UCODE_TLV_FLAGS_PM_CMD_SUPPORT
IWM_UCODE_TLV_FLAGS_NEWBT_COEX
IWM_UCODE_TLV_FLAGS_BF_UPDATED
IWM_UCODE_TLV_FLAGS_D3_CONTINUITY_API
IWM_UCODE_TLV_FLAGS_STA_KEY_CMD
IWM_UCODE_TLV_FLAGS_DEVICE_PS_CMD
IWM_UCODE_TLV_FLAGS_SCHED_SCAN
All supported firmware versions have these flags set.
Patch by Imre Vadasz
ok patrick@
|
|
All supported firmware versions have this feature flag set.
Remove now unneeded iwm_calc_rssi() function.
Patch by Imre Vadasz.
ok patrick@
|
|
It is only required for devices connected via SDIO which we do not support.
Patch by Imre Vadasz
ok patrick@
|
|
Aware Regulatory (LAR) mode and LAR is disabled according to NVM.
Patch by Imre Vadasz.
ok patrick@
|
|
Patch by Imre Vadasz.
Matches Linux commit 176aa60bf148b5af4209ac323cef941dee76e390 by Sara Sharon.
ok patrick@
|
|
which had a value different from the IWL_DEFAULT_MAX_TX_POWER
constant in Linux iwlwifi.
Patch by Imre Vadasz.
ok patrick@
|
|
Patch by Imre Vadasz.
ok patrick@
|
|
ok patrick@
|
|
ok patrick@
|
|
ok guenther@, mpi@
|
|
to connect, e.g. due to a timeout, we will switch the state to SCAN.
Unfortunately this skips clearing the active channel set, which
means that on a scan on all bands only the nodes on the active
channel set, which is defined by whatever node we tried to connect
to, are allowed and all other APs are ignored. Fix this by properly
calling begin_scan(). When we fail to connect and start a scan,
make sure to let the chip know that we don't want to associate
anymore.
Another issue existed when we interrupt a scan, for instance by
setting a new nwid or wpakey. In this case we didn't abort the
scan and started a new scan while the old one as still active.
This could lead to a SCAN -> SCAN transition loop.
Remove the "set ssid" event, since this would be an event in
addition to a failed auth/assoc event, which would make us try
to handle failure twice.
Discussed with and ok stsp@
|
|
64-bit unsigned arithmetic.
|
|
window_name is evaluated early. Reported by Mikolaj Kucharski.
|
|
|
|
it's a bit shorter, and a bit more correct wrt use of bus_dma. still
a bit to go though.
|
|
PLT entries and prevent overriding
ok kettenis@ deraadt@
|
|
ok jsg@, patrick@
|
|
|
|
Using alloc.c for the history array brings no value and prevents
easy handling of memory shortage. Switch to plain reallocarray and
keep running if HISTSIZE is too big.
The allocation is still done upfront with no sanity checking, it would
probably be nicer to allocate space as needed.
Issue reported by thomas@habets.se who suggested a different approach.
|
|
The manual has it, complete the help screen.
OK millert
|
|
RTM_CHGADDRATTR messages. Be consistant and eliminate ':' after all
'name's.
ok bluhm@
|
|
ok jsg@
|
|
Either a positive count is given or -i is omitted entirely; vm.conf(5) does
not allow interface configuration that results in zero interfaces either.
Raise the minimium count value to one and tell more about invalid counts
with the usual strtonum(3) idiom.
OK reyk
|
|
|
|
if gen is toggled per packet, then it needs to be toggled before
each packet, not before the loop. also, if 0 out the right offload.
brad pointed out the if 0 bit.
|
|
Prodded by Janne Johansson - thanks!
|
|
|
|
to make mpsafetey a bit easier to figure out i disabled checksum
and vlan offload. i'll put them back in soon though.
|
|
vmx "hardware" seems to be able to use rx descriptors as soon as
theyre filled in, which means filling the ring from a timeout can
run conccurently with an isr that's pulling stuff off the ring.
this is mostly a problem with the rxr accounting, so we serialise
updates to the alive counter by running rxfill in a mutex.
most of the investigation was done by claudio@ and mathieu@
an earlier version of this diff was tested hard by mathieu@ and was
ok@ claudio
|
|
Currently we return (1000000000 / hz) from clock_getres(2) as the
resolution for every clock. This is often untrue.
For CPUTIME clocks, if we have a separate statclock interrupt the
resolution is (1000000000 / stathz). Otherwise it is as we currently
claim: (1000000000 / hz).
For the REALTIME/MONOTONIC/UPTIME/BOOTTIME clocks the resolution is
that of the active timecounter. During tc_init() we can compute the
precision of a timecounter by examining its tc_counter_mask and store
it for lookup later in a new member, tc_precision. The resolution of
a clock backed by a timecounter "tc" is then
tc.tc_precision * (2^64 / tc.tc_frequency)
fractional seconds.
While here we can clean up sys_clock_getres() a bit.
Standards input from guenther@. Lots of input, feedback from
kettenis@.
ok kettenis@
|
|
Discussed with jmc@
|
|
by the ASM stub, which is also in libc. The compiler only generates
invocations of the latter.
ok mpi@ deraadt@ kettenis@
|
|
The handling of this changed with libutil/ber.c r1.12 resulting in starttls
failing.
Found by several.
Fix suggestion by roklein <at> roklein <dot> de
OK claudio@
|
|
While here also fix some wrong definitions.
With help from jmc@
Requested by and OK deraadt@
|
|
|
|
|
|
|
|
route will now show "AUTOCONF4" in flags.
|
|
initializes the MMU into its own functions and move them to locore.S.
ok patrick@
|
|
|
|
ok tb@
|
|
|
|
ok patrick@
|
|
isn't the default already. Same change as we made on arm64 two months ago.
ok patrick@
|
|
The function argument is not checked at all and the only caller in config.c
always passes a buffer valid buffer.
Defer the error case's default value to the end to avoid rewriting in case
a node is opened.
Feedback and OK reyk
|
|
|
|
from brad@
ok bluhm@ claudio@ deraadt@
|
|
ober_add_string.3 and as it was before the ber -> ober rename.
|