Signed-off-by: NHauke Mehrtens <hauke@hauke-m.de>

This updates mac80211 to version 5.15.58-1 which is based on kernel
5.15.58.
The removed patches were applied upstream.
Signed-off-by: NHauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit 3aa18f71)

Apply upstream patch[1] to fix breakage around math libraries.
This can likely be removed when 5.5.0-stable is tagged and released.

Build system: x86_64
Build-tested: bcm2711/RPi4B
Run-tested: bcm2711/RPi4B

1. https://github.com/wolfSSL/wolfssl/pull/5390Signed-off-by: NJohn Audia <therealgraysky@proton.me>
(cherry picked from commit c2aa816f)

9212bfc odhcp6c: fix IA discard when T1 > 0 and T2 = 0
Signed-off-by: NDávid Benko <davidbenko@davidbenko.dev>
(cherry picked from commit f9209086)

the hash and timestamp of the remote copy of the archive
has changed since last bump
meaning the remote archive copy was recreated
Signed-off-by: NMichael Pratt <mcpratt@pm.me>
(cherry picked from commit ba7da736)

Buidbots are throwing the following compile error:

In file included from tools/aisimage.c:9:
include/image.h:1133:12: fatal error: openssl/evp.h: No such file or directory
            ^~~~~~~~~~~~~~~
compilation terminated.

Fix it by passing `UBOOT_MAKE_FLAGS` variable to make.
Suggested-by: NPetr Štetiar <ynezz@true.cz>
Fixes: 6d5611af ("uboot-at91: update to linux4sam-2022.04")
Signed-off-by: NClaudiu Beznea <claudiu.beznea@microchip.com>
(cherry picked from commit 95a24b54)

Update uboot-at91 to linux4sam-2022.04. As linux4sam-2022.04 is based on
U-Boot v2022.01 which contains commit
93b196532254 ("Makefile: Only build dtc if needed") removed also the DTC
variable passed to MAKE to force the compilation of DTC.
Signed-off-by: NClaudiu Beznea <claudiu.beznea@microchip.com>
(cherry picked from commit 6d5611af)

Update AT91Bootstrap v4 capable targets to v4.0.3.
Signed-off-by: NClaudiu Beznea <claudiu.beznea@microchip.com>
(cherry picked from commit 859f5f9a)

Disable the usage of target specific CPU crypto instructions by default
to allow the package being shared again. Since WolfSSL does not offer
a stable ABI or a long term support version suitable for OpenWrt release
timeframes, we're forced to frequently update it which is greatly
complicated by the package being nonshared.

People who want or need CPU crypto instruction support can enable it in
menuconfig while building custom images for the few platforms that support
them.
Signed-off-by: NJo-Philipp Wich <jo@mein.io>
(cherry picked from commit 0063e342)

All patches automatically rebased.
Signed-off-by: NJohn Audia <therealgraysky@proton.me>
(cherry picked from commit 7be62b11)

Add some new/missing symbols relating to speculative execution mitigations[1].

1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/arch/x86/Kconfig?id=v5.10.133&id2=v5.10.132Signed-off-by: NJohn Audia <therealgraysky@proton.me>
(cherry picked from commit 56760c0b)

All patches automatically rebased.

Build system: x86_64
Build-tested: ipq806x/R7800
Signed-off-by: NJohn Audia <therealgraysky@proton.me>
(cherry picked from commit 913f160a)

All patches automatically rebased.

The following patch was replaced by a similar version upstream:
 bcm27xx/patches-5.10/950-0036-tty-amba-pl011-Add-un-throttle-support.patch
Signed-off-by: NJohn Audia <therealgraysky@proton.me>
(cherry picked from commit 7d3c0928)

Using the BOARD_NAME variable results for both er and erlite devices to
identify themselfs as `er` and `erlite` (via `ubus call system board`).

This is problematic when devices search for firmware upgrades since the
OpenWrt profile is actually called `ubnt_edgerouter` and
`ubnt_edgerouter-lite`.

By adding the `SUPPORTED_DEVICE` a mapping is created to point devices
called `er` or `erlite` to the corresponding profile.

FIXES: https://github.com/openwrt/asu/issues/348Signed-off-by: NPaul Spooren <mail@aparcar.org>
(cherry picked from commit 2a072701)

This fixes problem of overwriting BCM4908 U-Boot and DTB files by
BCM4912 ones. That bug didn't allow booting BCM4908 devices.

Fixes: f4c2dab5 ("uboot-bcm4908: add BCM4912 build")
Signed-off-by: NRafał Miłecki <rafal@milecki.pl>
(cherry picked from commit a8e1e305)

In theory we could have just 1 bootfs image for all devices as each
device has its own entry in the "configurations" node. It doesn't work
well with default configuration though.

If something goes wrong U-Boot SPL can be interrupted (by pressing A) to
enter its minimalistic menu. It allows ignoring boardid. In such case
bootfs default configuration is used.

For above reason each SoC family (BCM4908, BCM4912) should have its own
bootfs built. It allows each of them to have working default
configuration.
Signed-off-by: NRafał Miłecki <rafal@milecki.pl>
(cherry picked from commit 6ae2f7ff)

There are forum reports that 2 LAN ports are not working, the
GPIO settings are adjusted to fix the problem.
Signed-off-by: NDaniel Kestrel <kestrel1974@t-online.de>
(cherry picked from commit 0f301b0b)

The order of LAN ports shown in Luci is reversed compared to what is
written on the case of the device.  Fix the order so that they match.

Fixes: #10275
Signed-off-by: NChristian Lamparter <chunkeey@gmail.com>
(cherry picked from commit 69ea6713)

The change of the PKG_VERSION caused the hash of the package to
change. This is because the PKG_VERSION is present in the
internal directory structure of the archive.

Fixes: 038d5bda ("layerscape: use semantic versions for LSDK")
Signed-off-by: NChristian Lamparter <chunkeey@gmail.com>
(cherry picked from commit e879ccca)
(cherry picked from commit d4391ef0)

moves and extends the current facilities, which have been
added some time ago for the the usbip utility, to support
more utilites that are shipped with the Linux kernel tree
to the SDK.

this allows to drop all the hand-waving and code for
failed previous attempts to mitigate the SDK build failures.

Fixes: bdaaf66e ("utils/spidev_test: build package directly from Linux")
Signed-off-by: NChristian Lamparter <chunkeey@gmail.com>
(cherry picked from commit b479db90)

Destination switch ports for outgoing frame can range from 0 to
CPU_PORT-1.

Refactor the code to only generate egress frame CPU headers when a valid
destination port number is available, and make the code a bit more
consistent between different switch generations. Change the dest_port
argument's type to 'unsigned int', since only positive values are valid.

This fixes the issue where egress frames on switch port 0 did not
receive a VLAN tag, because they are sent out without a CPU header.
Also fixes a potential issue with invalid (negative) egress port numbers
on RTL93xx switches.
Reported-by: NArınç ÜNAL <arinc.unal@xeront.com>
Suggested-by: NBirger Koblitz <mail@birger-koblitz.de>
Tested-by: NLuiz Angelo Daros de Luca <luizluca@gmail.com>
Signed-off-by: NSander Vanheule <sander@svanheule.net>
(cherry picked from commit 1773264a)

Priority values passed to the egress (TX) frame header initialiser are
invalid when smaller than 0, and should not be assigned to the frame.
Queue assignment is then left to the switch core logic.

Current code for RTL83xx forces the passed priority value to be
positive, by always masking it to the lower bits, resulting in the
priority always being set and enabled. RTL93xx code doesn't even check
the value and unconditionally assigns the (32 bit) value to the (5 bit)
QID field without masking.

Fix priority assignment by only setting the AS_QID/AS_PRI flag when a
valid value is passed, and properly mask the value to not overflow the
QID/PRI field.

For RTL839x, also assign the priority to the right part of the frame
header. Counting from the leftmost bit, AS_PRI and PRI are in bits 36
and 37-39. The means they should be assigned to the third 16 bit value,
containing bits 32-47.
Tested-by: NLuiz Angelo Daros de Luca <luizluca@gmail.com>
Signed-off-by: NSander Vanheule <sander@svanheule.net>
(cherry picked from commit 0b35a08a)

The flag to enable L2 address learning on egress frames is in CPU header
bit 40, with bit 0 being the leftmost bit of the header. This
corresponds to BIT(7) in the third 16-bit value of the header.

Correctly set L2LEARNING by fixing the off-by-one error.

Fixes: 9eab76c8 ("realtek: Improve TX CPU-Tag usage")
Tested-by: NLuiz Angelo Daros de Luca <luizluca@gmail.com>
Signed-off-by: NSander Vanheule <sander@svanheule.net>
(cherry picked from commit d6165ea7)

The flag to enable the outgoing port mask is in CPU header bit 43, with
bit 0 being the leftmost bit of the header. This corresponds to BIT(4)
in the third 16-bit value of the header.

Correctly set AS_DPM by fixing the off-by-one error.

Fixes: 9eab76c8 ("realtek: Improve TX CPU-Tag usage")
Tested-by: NLuiz Angelo Daros de Luca <luizluca@gmail.com>
Signed-off-by: NSander Vanheule <sander@svanheule.net>
(cherry picked from commit d9516cac)

Netgear WAX202 is an 802.11ax (Wi-Fi 6) router.

Specifications:
* SoC: MT7621A
* RAM: 512 MiB NT5CC256M16ER-EK
* Flash: NAND 128 MiB F59L1G81MB-25T
* Wi-Fi:
  * MT7915D: 2.4/5 GHz (DBDC)
* Ethernet: 4x 1GbE
  * Switch: SoC built-in
* USB: None
* UART: 115200 baud (labeled on board)

Load addresses (same as ipTIME AX2004M):
* stock
  * 0x80010000: FIT image
  * 0x81001000: kernel image -> entry
* OpenWrt
  * 0x80010000: FIT image
  * 0x82000000: uncompressed kernel+relocate image
  * 0x80001000: relocated kernel image -> entry

Installation:
* Flash the factory image through the stock web interface, or TFTP to
  the bootloader. NMRP can be used to TFTP without opening the case.
* Note that the bootloader accepts both encrypted and unencrypted
  images, while the stock web interface only accepts encrypted ones.

Revert to stock firmware:
* Flash the stock firmware to the bootloader using TFTP/NMRP.

References in WAX202 GPL source:
https://www.downloads.netgear.com/files/GPL/WAX202_V1.0.5.1_Source.rar

* openwrt/target/linux/ramips/dts/mt7621-ax-nand-wax202.dts
  DTS file for this device.
Signed-off-by: NWenli Looi <wlooi@ucalgary.ca>
(cherry picked from commit 0f068e7c)

Netgear encrypted image is used in various devices including WAX202,
WAX206, and EX6400v3. This image format also requires a dummy squashfs4
image which is added here as well.

References in WAX202 GPL source:
https://www.downloads.netgear.com/files/GPL/WAX202_V1.0.5.1_Source.rar

* openwrt/bootloader/u-boot-mt7621-2018.09-gitb178829-20200526/board/ralink/common/dual_image.c
  Bootloader code that verifies the presence of a squashfs4 image, thus
  a dummy image is added here.

* openwrt/tools/imgencoder/src/gj_enc.c
  Contains code that generates the encrypted image. There is support for
  adding an RSA signature, but it does not look like the signature is
  verified by the stock firmware or bootloader.

* openwrt/tools/imgencoder/src/imagekey.h
  Contains the encryption key and IV. It appears the same key/IV is used
  for other Netgear devices including WAX206 and EX6400v3.
Signed-off-by: NWenli Looi <wlooi@ucalgary.ca>
(cherry picked from commit efca76ff)

The armvirt target is also used to run OpenWrt in lxc on other targets
like a Raspberry Pi. If we set WOLFSSL_HAS_CPU_CRYPTO by default the
wolfssl binray is only working when the CPU supports the hardware crypto
extension.

Some targets like the Raspberry Pi do not support the ARM CPU crypto
extension, compile wolfssl without it by default. It is still possible
to activate it in custom builds.
Signed-off-by: NHauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit d1b5d17d)

This fix allows trigger a rerun of Build/Configure when
rpcapd was selected.
Signed-off-by: NJianhui Zhao <zhaojh329@gmail.com>
(cherry picked from commit 6902af4f)

Without this, WOLFSSL_HAS_DH can be disabled even if WOLFSSL_HAS_WPAS is
enabled, resulting in an "Anonymous suite requires DH" error when trying
to compile wolfssl.
Signed-off-by: NPascal Ernster <git@hardfalcon.net>
Reviewed-by: NEneas U de Queiroz <cotequeiroz@gmail.com>
(cherry picked from commit 21825af2)

No manual changes needed.
Signed-off-by: NHauke Mehrtens <hauke@hauke-m.de>

All patches automatically rebased.
Signed-off-by: NJohn Audia <therealgraysky@proton.me>

All patches automatically rebased.

Build system: x86_64
Build-tested: ipq806x/R7800
Signed-off-by: NJohn Audia <therealgraysky@proton.me>

All patches automatically rebased.

Build system: x86_64
Build-tested: ipq806x/R7800
Signed-off-by: NJohn Audia <therealgraysky@proton.me>

No patches needed to be rebased, just updated checksums
Signed-off-by: NJohn Audia <therealgraysky@proton.me>

4cd7d4f Revert "firewall3: support table load on access on Linux 5.15+"
50979cc firewall3: remove unnecessary fw3_has_table
Signed-off-by: NRui Salvaterra <rsalvaterra@gmail.com>
(cherry-picked from commit 435d7a05)
Signed-off-by: NWenli Looi <wlooi@ucalgary.ca>

Due to the bug described here[1], remove the 300 MHz clock to avoid a low
voltage condition that can cause a hang when rebooting the RT3200/E8450.

This solution is probably better than the script-based work-around[2].

1. https://forum.openwrt.org/t/belkin-rt3200-linksys-e8450-wifi-ax-discussion/94302/1490
2. https://github.com/openwrt/openwrt/pull/5025Signed-off-by: NJohn Audia <therealgraysky@proton.me>
Tested-by: NRui Salvaterra <rsalvaterra@gmail.com>
Tested-by: NJohn Audia <therealgraysky@proton.me>
(cherry picked from commit d0d6b8e1)
[ fix the conflict by apply the patch to kernel 5.10 ]
Signed-off-by: NChristian Marangi <ansuelsmth@gmail.com>

Signed-off-by: NRafał Miłecki <rafal@milecki.pl>
(cherry picked from commit 864fdf2b)

Signed-off-by: NRafał Miłecki <rafal@milecki.pl>
(cherry picked from commit 001856fa)

Signed-off-by: NRafał Miłecki <rafal@milecki.pl>
(cherry picked from commit bb2a2b1d)

This includes BCM63xx and BCM4908 families.
Signed-off-by: NRafał Miłecki <rafal@milecki.pl>
(cherry picked from commit d9ab1e56)