There are many changes in this file and its impossible to cover this with a patch for now current and all kernels back
We are using same hack in UWE drivers.
Upstream code has trickled down into 6.5.y, so adjust patching
accordingly.
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
Co-authored-by: Patrick Yavitz <pyavitz@xxxxx.com>
This is just a cosmetic change. Patches have been consolidated
into one patch within each corresponding linux version directory.
Added: linux-6.6 (RC-1)
Removed: linux-6.2/6.3
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
Co-authored-by: Patrick Yavitz <pyavitz@xxxxx.com>
Also added some cleanup fixes to silence some of the compiler warnings,
fixes for issues during inserting and removing xradio module and fixes
for possible data corruption on vmmaped stack.
All of these fixes were taken from https://github.com/fifteenhex/xradio
* patch: misc: rtw88: wireless-next: 2023-08-25
Updated: 6.1 / 6.4
Added: 6.5
For doc sake, this update makes 6.1 slightly differrent than 6.4 and
6.5 in one particular area of main.c.
As shown here:
7746e2fa87
6.1 requires we use del_timer_sync, where the above releases use
timer_delete_sync.
Tested-on: ODROID-C4 X96-AIR BPI-CM4 (linux 6.x.y)
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
* driver_rtw88: `linux-version compare "${version}" ge 6.1`
Suggested-by: @viraniac
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
---------
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
Co-authored-by: Patrick Yavitz <pyavitz@xxxxx.com>
Cope with the fix in stable 6.3.13 bf353116d1bf and 6.5-rc1 e8c2af660ba0
"wifi: cfg80211: fix regulatory disconnect with OCB/NAN".
That is the removal of REGULATORY_IGNORE_STALE_KICKOFF
from the wireless regulator internal API to fix any driver
that allowed OCB/NAN.
Note this code will need to be expanded once and if 6.4 include the
above fixup.
Signed-off-by: Alban Browaeys <alban.browaeys@gmail.com>
Use multiple consecutive reads in rtw_sdio_read_port() to limit the number of bytes which are copied by the host from the card in one MMC/SDIO transfer. This allows receiving a buffer that's larger than the hosts max_req_size (number of bytes which can be transferred in one MMC/SDIO transfer). As a result of this the skb_over_panic error is gone as the rtw88 driver is now able to receive more than 1536 bytes from the card (either because the incoming packet is larger than that or because multiple packets have been aggregated).
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
This brings the patch set up to 2023-06-22 wireless-next
Drivers tested;
8822CS. 8821CU and 8723DS
Notables;
Not seeing random dmesg spam `rtw_8822cs failed to get tx report from firmware` which I would see on both the CS and CU from time to time.
Signed-off-by: Patrick Yavitz <pyavitz@gmail.com>
For combo chips, antennas were controlled by bluetooth only during power on. If WiFi wish to do transmission, notification to the coexistence module are required. Previously we only do this before authentication. To allow transmission before auth, such as management TX, now we start the initiation of coexistence earlier so antennas are shared between WiFi and bluetooth after set_channel(), and frames could then be sent.
Signed-off-by: Patrick Yavitz <pyavitz@gmail.com>
Linux 6.1.34 / 6.3.8
Bits of code from upstream creeped down into LTS and Stable, creating fails and false skips. The offending code has been removed from the patch set.
Signed-off-by: Patrick Yavitz <pyavitz@gmail.com>
Patch set includes a complete backport of RTW88 as it currently stands, along with extras
Extra:
Patch: RTL8723DS (SDIO)
Patch: _rtw_download_firmware() warn: missing unwind goto?
Hack: SDIO RX Aggregation Limiting
I only have two units available to me with an 8822CS module and in my testing this is only required on the BPI-CM4IO. With out LIMITING the unit will either kernel panic or not be able to send or receive.
This is currently being looked into:
https://lore.kernel.org/linux-wireless/CAFBinCBaXtebixKbjkWKW_WXc5k=NdGNaGUjVE8NCPNxOhsb2g@mail.gmail.com/T/#u
It may be possible to just set LIMITING across all builds, but that to me seems like a poor choice. This requires testing.
Signed-off-by: Patrick Yavitz <pyavitz@gmail.com>
* sunxi: remove rtl8723cs patches from sunxi-edge (6.2)
* adjust minor pinephone patch
* media: remove rtl8723cs patches from media-edge
* media: remove rtl8723cs patches from media-current (6.1)
* sunxi: reinstate rtl8723cs patches for sunxi-6.1 and disable them
* sunxi: reinstate rtl8723cs patches for 6.2 and disable them
* main source for driver and patches are sunxi64 megous patches
* move into patch/misc/wireless-rtl8723cs directory
* integrate with minor patches from rk322x/rockchip64 families
* update drivers_network.sh to apply patches in same order as before
* remove references from patches.megous and series.conf in sunxi64
* remove patches from rk322x and rockchip64 family patches
* do not touch kernel archives older than 6.1
* Add some Wireless modules to RK3588 legacy kernel
* Add some Wireless modules to RK3588 legacy kernel
* Add some Wireless modules to RK3588 legacy kernel
* Solve compatibility issues for some of wifi patches, disable those that needs more work
* Fix 8812au
* Update to re-enable RTL88x2CS driver for 5.19.2+
* Add 8723ds and rename others
* Following naming convention
* Name
* Adjust UWE5622 for 5.19.2
* Update UWE5622 patch for sunxi
* Enable last one
* Fixes for 8723DU
Co-authored-by: Vyacheslav Bocharov <adeep@lexina.in>
* Update kernel configs
* Switch sunxi edge to 5.18.y
* Move sunxi to 5.18.y and re-enable AUFS
* Change version - temporally to make a build from here
* Update config
* 88xx was fixed in the mean time.
* Put version back
* Fix sunxi legacy, disable aufs on 5.10.y since its broken
* Upstream changed in the mean time
* Add a patch to enable 8821cu compilation at 5.18
https://github.com/armbian/build/pull/3814
* Re-enable CONFIG_RTL8822BU in edge
* Update CONFIG_RTL8XXXU
* Bump imx6
* Bump uefi kernels to 5.18.y
* Bump mvebu64 and switch odroid xu4 to 5.18
fix: add the KDEB_COMPRESS variable to the debuild script of the kernel build version 5.3+
This partially fixes#3762 if DEB_COMPRESS=xz is used.
Jira reference number AR-1194
* Switched rockchip64-current to linux 5.15
* Backported and adjusted patches from rockchip64-current
* Switched rockchip64 edge to 5.16.y (#3499)
* Initial rockchip64-edge at 5.16.y
* Bunch of fixes for rockchip64-edge at 5.16.y
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
* Prepare xu4 edge for 5.16.y, move current of imx6 to 5.15.y and edge to 5.16.y
- fix bootsplash on 5.16.y
* rk322x: advance current to 5.15 and edge to 5.16
* rockchip: advance current kernel to 5.15, edge to 5.16
* - adjust configs
- fix bootsplash patches
- adjust aufs
* Switch sunxi / sunxi64 current to 5.15.y, edge to 5.16.y
- cleanup bootsplash patches
- adjust configs
* Update mvebu64
Co-authored-by: Paolo Sabatino <paolo.sabatino@gmail.com>
* Sync kernel config with radxa and remove packaging patch
* Merge the rockchip64 legacy config as well
* Lower priority of EFI partitioning against DOS partitioning which is used by Armbian
Co-authored-by: Catalin Toda <catalinii@yahoo.com>
* introduce DEB_COMPRESS for dpkg-deb+kernel's KDEB_COMPRESS
- Avoids zstd which is now default in Ubuntu Impish, but can't be read by Debian dpkg
- Allows for xz, gzip, or none; defaults to xz; use gzip for faster, and none for much faster.
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* use KDEB_COMPRESS in packages/armbian/builddep for 5.12+ kernels too
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
