Age | Commit message (Collapse) | Author |
|
ok miod@ millert@
|
|
doesn't hang.
ok millert@, dlg@
|
|
characters.
|
|
issue reported by Crystal Kolipe on tech@
|
|
New firmware versions address some security issues, as outlined here:
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00621.html
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00699.html
Firmware has been available in fw_update for some time so systems which
track -current should already have the new -77 images.
Tested:
ax200: jmc, hrvoje, stsp
ax201: Mikhail, Sven Wolf, stsp
ax210: lraab, stsp
ax211: Mikhail, dv
|
|
than assuming that it always matches our currently configured channel.
Should prevent problems on 40/80Mhz channels if there is a mismatch.
|
|
|
|
Fixes a firmware panic I encountered while working on firmware upgrades.
|
|
Undocumented and ignored by the Linux driver, too.
Apparently only used by the Windows driver.
Confirmed by Johannes Berg.
|
|
We used to provide beacon-related information only once our station was
associated. New firmware wants to see this information earlier, when are
about to send an AUTH frame. Otherwise SYSASSERT 0x2000011A is raised.
Problem diagnosed with help from Johannes Berg, thanks!
|
|
Firmware expects time in TU units.
Use 900 TU for the session protection timeout, like the linux driver does.
verified with Johannes Berg from Linux/Intel, thanks for the support!
|
|
Required for adding/removing Tx queues on new firmware versions.
Semantics have changed yet again. Good old iwm(4) required manual
removal of related Tx queues when a station is removed from firmware.
At some point iwx(4) firmware removed this requirement and demanded
that queue removal would be done implicitly by firmware instead.
And now the firmware engineers at Intel have again changed their
minds about this, and explicit queue removal is required again.
It is sad that we are being driven through such a marathon of changes
just in order to pick up some firmware security fixes...
|
|
This command is required to set up Rx aggregation on new firmware.
|
|
|
|
MAC context command fields which firmware has been ignoring since the iwm
hardware generation have been repurposed for information related to 11ax.
Just set these fields to zero. Firmware -71 and up will panic otherwise.
|
|
New firmware wants to be told about MIMO antenna configuration via
a separate command, rather than via the good old PHY context command.
|
|
As of this commit iwx will ignore 'ifconfig media' commands where the
user-specified Tx rate resolves to something other than 'autoselect'.
The existing support for forcing a Tx rate was already only partially
working in 11n and 11ac modes. I doubt anyone had a serious use case for
this. If you really need to force a specific Tx rate for data frames
sent by iwx then hack the driver instead of using 'ifconfig media'.
The firmware interface was designed for Tx rate selection in firmware.
Maintaining support for overriding the Tx rate with ifconfig in face of
complicated firmware interface changes such as this rate_n_flags change
is just not worth it. While trying to keep forced Tx rates working on top
of the new rate_n_flags format I accidentally broke the Tx rate used for
managment frames during regular operation, which caused much frustration.
|
|
also add some missing bits found in the Linux driver while here
|
|
|
|
|
|
|
|
From Stylon Wang
118ad80d27d938868299ef184f7483b21f011f0b in linux-6.1.y/6.1.15
0cf8307adbc6beb5ff3b8a76afedc6e4e0b536a9 in mainline linux
|
|
From Stylon Wang
075e2099c32cf4486b27266d2aecf61e95499ea4 in linux-6.1.y/6.1.15
ead08b95fa50f40618c72b93a849c4ae30c9cd50 in mainline linux
|
|
From Nicholas Kazlauskas
4da108082a3290804ebbd42d70ce8535c00e4637 in linux-6.1.y/6.1.15
e383b12709e32d6494c948422070c2464b637e44 in mainline linux
|
|
ok kettenis@ jmatthew@
|
|
related registers on all supported SoCs. Makes rktemp(4) work on
RK356x with U-Boot.
ok jmatthew@
|
|
than advertised in the RK3568. This value is present in the Linux
driver and implies the new register layout. So handle both values.
This makes GPIOs on the RK3566 actually work.
ok patrick@
|
|
muxings. Implement support for this.
ok patrick@
|
|
Fix year on my copyright.
|
|
ok deraadt@
|
|
ok deraadt@
|
|
this allows me to boot if acpitz is using tipmic instead of getting
stuck. tipmic would spin on tsleep, which returns immediately with
0 when cold, waiting for a value to be set by the tipmic interrupt
handler. cos the box is cold the interrupt is masked, so the tsleep
loop never ended.
patrick@ helped me find this
ok kettenis@
|
|
With this, the WAN port on the Turris Omnia works.
tested on Turris MOX by kettenis@
ok patrick@
|
|
From Lucas De Marchi
44610f4c3093bbce3061b77d37bdf1bed8e379da in linux-6.1.y/6.1.14
fff758698842fb6722be37498d8773e0fb47f000 in mainline linux
|
|
From Ankit Nautiyal
0deb50618944aed143269214daea0ba2ddf2222d in linux-6.1.y/6.1.14
18feaf6d0784dcba888859109676adf1e0260dfd in mainline linux
|
|
Without them, the kernel could be made to crash or reboot after receiving some
specially crafted terminal escape sequences.
Reported by David Leadbeater (dgl, dgl dot cx)
|
|
issue on the StarFive JH7100 SoC where packets spanning multiple mbufs
are corrupted. Makes ethernet work reliably on the StarFive VisionFive 1
board.
ok patrick@
|
|
ok patrick@
|
|
register layout where the upper 16 bits decide which of the lower 16 bits
apply when writing to a register. Handle this new variant.
ok patrick@
|
|
From Matt Roper
2fc3ff76e96f48e5e4dd705f6794b8483f7c1624 in linux-6.1.y/6.1.13
d5a1224aa68c8b124a4c5c390186e571815ed390 in mainline linux
|
|
From Leo Li
020eccac747e30a35f1fdd4dc6f18425ff1a5870 in linux-6.1.y/6.1.13
2a00299e7447395d0898e7c6214817c06a61a8e8 in mainline linux
|
|
From Jack Xiao
dbe3529e816ee77a19fb6636e762b1dadbd02d10 in linux-6.1.y/6.1.13
8f32378986218812083b127da5ba42d48297d7c4 in mainline linux
|
|
From Alex Deucher
b4e79d0c7f9bb938525716b3e05cfca6418e2bae in linux-6.1.y/6.1.13
6fc547a5a2ef5ce05b16924106663ab92f8f87a7 in mainline linux
|
|
From Yiqing Yao
fc64b04297a0674f4e5aff50622efdce46715fe1 in linux-6.1.y/6.1.13
ac7170082c0e140663f0853d3de733a5341ce7b0 in mainline linux
|
|
From Evan Quan
e9cbb2b0d9f679d7e25b9415cf9d7345441a95c5 in linux-6.1.y/6.1.13
bb25849c0fa550b26cecc9c476c519a927c66898 in mainline linux
|
|
From Nicholas Kazlauskas
488770cbddd8a873fb3bb8866e8a46211570c367 in linux-6.1.y/6.1.13
154711aa5759ef9b45903124fa813c4c29ee681c in mainline linux
|
|
From George Shen
383e32fa274a330dbf2d2db538b6bf2f9ef390aa in linux-6.1.y/6.1.13
275d8a1db261a1272a818d40ebc61b3b865b60e5 in mainline linux
|
|
From Daniel Miess
7dbd205349f1fb098057c28a9a2af244aa868f72 in linux-6.1.y/6.1.13
dd2db2dc4bd298f33dea50c80c3c11bee4e3b0a4 in mainline linux
|
|
From Daniel Miess
0c42622a573b716d79c57ff61c52fea46c0a5c94 in linux-6.1.y/6.1.13
ea062fd28f922cb118bfb33229f405b81aff7781 in mainline linux
|
|
ok jsg@ phessler@
|