Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sync 16/09 #156

Merged
Merged

Conversation

rmandrad
Copy link
Owner

Thanks for your contribution to OpenWrt!

To help keep the codebase consistent and readable,
and to help people review your contribution,
we ask you to follow the rules you find in the wiki at this link
https://openwrt.org/submitting-patches

Please remove this message before posting the pull request.

dangowrt and others added 30 commits September 11, 2024 00:17
Add missing 'model' string to DT, so /tmp/sysinfo/model gets populated.

Fixes: 64dae10 ("ramips: mt76x8: add support for Yuncore CPE200")
Signed-off-by: Daniel Golle <[email protected]>
Add missing 'model' string to DT, so /tmp/sysinfo/model gets populated.

Fixes: e497c97 ("ramips: mt76x8: add support for Yuncore M300")
Signed-off-by: Daniel Golle <[email protected]>
Change contact information of comitter as requested.

Reviewed-by: Sarah Mädel <[email protected]>
Signed-off-by: David Bauer <[email protected]>
The path for linking libucode.so was not specified for the ucode binary.
This breaks execution of ucode in the host context.

Signed-off-by: David Bauer <[email protected]>
Aruba boards now ship with multiple DTS and image-configurations per
image. Newer apboot revs expect a configuration for their hardware to be
present.

Signed-off-by: David Bauer <[email protected]>
Adds compatibility for APK.

Signed-off-by: Rosen Penev <[email protected]>
Link: openwrt#16355
Signed-off-by: Robert Marko <[email protected]>
 02aa43d Revert "system-linux: re-apply ethtool on phy attachment"

Signed-off-by: Daniel Golle <[email protected]>
Apply changes suggested by SkyLake Huang for pending series improving
MediaTek Ethernet PHY drivers.

Signed-off-by: Daniel Golle <[email protected]>
- specify CC target explicitly
- define KBUILD_SYM32=n to select "native" build format (if building with 64-bit arch)
- rewrap lines (for good)

Signed-off-by: Konstantin Demin <[email protected]>
Link: openwrt#15702
Signed-off-by: Robert Marko <[email protected]>
e5b7fb1c606d ipq8074: add Linksys MX8500 BDF

Link: openwrt#16382
Signed-off-by: Robert Marko <[email protected]>
2ca41d755d93 qcn9074: add Linksys MX8500 BDF

Link: openwrt#16387
Signed-off-by: Robert Marko <[email protected]>
Development of fortify-headers has been moved to GitHub.
Gentoo [1] and Alpine Linux [2] already uses it.

Since updating fortify-headers to new version causes a lot of
compile errors, this commit does not bump version.

This commit also refresh patch.

[1]: https://packages.gentoo.org/packages/sys-libs/fortify-headers
[2]: https://git.alpinelinux.org/aports/log/main/fortify-headers

Signed-off-by: Yanase Yuki <[email protected]>
Link: openwrt#16374
Signed-off-by: Robert Marko <[email protected]>
There is no need to keep a version specific dts directory.
Rename the folder to its standard location.

Signed-off-by: Markus Stockhausen <[email protected]>
With commit b53202a ("realtek: switch to use generic MDIO accessor functions")
the phy access logic was enhanced. A quite big kernel patch was introduced that
allowed to make use of hardware-assisted page access like we have in the realtek
target. Basically it works the following way

- The enhanced bus intercepts page write accesses
- Currently selected pages are stored in internal vars.
- Finally only all-in-one-consistent bus/register accesses are issued
- It intercepted page changes and ensured that only a complete bus call

For the details see openwrt#16172

Switching over to newer kernels this patch is really hard to maintain. Its heavy
modifcations exist only in the realtek target. So it does not matter if we keep
it as an kernel modification or directly include it in our driver. To make it the
future brighter we drop this patch and take over its logic. Thus the kernel will
stay totally modification-free. What do we do?

1. Up to now the bus->priv structure directly pointed to ethernet->priv. Create an
explicit private structure rtl838x_bus_priv that not only holds the ethernet->priv
pointer but also space for some bus status tracking vars as well.

2. Wherever we use a reference to ethernet->priv directly replace that by an
additional indirection over the new rtl838x_bus_priv structure.

3. Up to now the phy flag PHY_HAS_REALTEK_PAGES identified that we can use the
alternative paged access from the patch. As this will be no longer available
remove it and provide read_page/write_page functions for each possible PHY.
These functions will be pretty standard as for other Realtek PHYs.

4. The existing mdio bus read/write function rely on the classic MII_ADDR_C45
flag - one interface for two access types. This mixup will be removed on the way
to kernel 6.6. In the future there will be two pairs of access functions. One for
classic access one for c45 style access. Rewrite our functions into 3 parts:

- a classic read/write function: ready for kernel 6.6
- a new c45 read/write function: ready for kernel 6.6
- a legacy read/write wrapper: for current 5.15 for the time being

When we switch to 6.6 we only need to remove the legacy wrappers and link the
new functions. Life can be so easy.

5. The classic read/write functions will incorporate the interception logic that
was originally in the patch.

6. The package convenience functions that were embedded in the patch get lost as
well. Rewrite them inside our phy driver.

Signed-off-by: Markus Stockhausen <[email protected]>
[Minor checkpatch.pl cleanups]
Signed-off-by: Sander Vanheule <[email protected]>
Copy files and config from 5.15 kernel version. Because of the big version jump
leave out the patches for now so we can treat them individually later on.

Signed-off-by: Markus Stockhausen <[email protected]>
The CONFIG_CLOCKSOURCE_WATCHDOG_MAX_SKEW_US is missing. Avoid
complaints and add it with its default 125.

Signed-off-by: Markus Stockhausen <[email protected]>
Copy the patch file to 6.6

Signed-off-by: Markus Stockhausen <[email protected]>
No content changes. Only take over the new patch locations.

Signed-off-by: Markus Stockhausen <[email protected]>
Copy the patch file to 6.6

Signed-off-by: Markus Stockhausen <[email protected]>
No content changes. Only take over the new patch locations.

Signed-off-by: Markus Stockhausen <[email protected]>
Copy the patch file to 6.6

Signed-off-by: Markus Stockhausen <[email protected]>
No content changes. Only take over the new patch locations.

Signed-off-by: Markus Stockhausen <[email protected]>
…k-otto

Copy the patch file to 6.6

Signed-off-by: Markus Stockhausen <[email protected]>
…tek-otto

No content changes. Only take over the new patch locations.

Signed-off-by: Markus Stockhausen <[email protected]>
Copy the patch file to 6.6

Signed-off-by: Markus Stockhausen <[email protected]>
…-rtl

No content changes. Only take over the new patch locations.

Signed-off-by: Markus Stockhausen <[email protected]>
…k-rtl

Copy the patch file to 6.6

Signed-off-by: Markus Stockhausen <[email protected]>
…ltek-rtl

No content changes. Only take over the new patch locations.

Signed-off-by: Markus Stockhausen <[email protected]>
Copy the patch file to 6.6

Signed-off-by: Markus Stockhausen <[email protected]>
qosmio and others added 16 commits September 15, 2024 15:33
Rather mess with target 'config-*' files, introduce a custom menu item
that consolidates all IPQ related kernel settings in one menu.

Most of these can be left as default since the options are derived from the
initial NSS fork for 'config-6.6'.

Options include:
1) enable or disable building `skbuff_recycle`
2) enable or disable preemption
3) select IPQ memory profile

Signed-off-by: Sean Khan <[email protected]>
There are instances where `skbuff_recycle` messes up skb headers causing
various issues in network related activities. This was initially meant
to resolve issues with memory usage issues on 6.1.

Introduce a proc option to enable or disable skbuff_recycle. The default
is to have it enabled. Users on 512M platforms should test if memory
leaks still occur with this option disabled.

echo 0 > /proc/net/skb_recycler/skb_recycler_enable

echo 1 > /proc/net/skb_recycler/skb_recycler_enable

NOTE: There is a new script in `qca-nss-drv` that will automatically
manage this as an UCI configurable option.

commit 217a4fa43ba2ad0a02e8080dfde11ad23534aa8c (HEAD -> NSS-12.5-K6.x)
Author:     Sean Khan <[email protected]>
AuthorDate: Sat Jul 13 18:43:52 2024 -0400
Commit:     Sean Khan <[email protected]>
CommitDate: Sat Jul 13 18:43:52 2024 -0400

    nss-drv: add skb_recycler init script

Signed-off-by: Sean Khan <[email protected]>
Also set SKB_FIXED_SIZE_2K if IPQ memory profile is < 512M

Signed-off-by: Sean Khan <[email protected]>
There was logic that was initially included in the coconut branch of
QSDK for older mac80211 NSS implementation. It was brought over to
address an issue with ath10k where during heavy traffic, AP would trigger
`failed to increase tx pending count: -16, dropping`.

The issue was actually caused by `skb_recyler` malforming some packets.
Disabling `skb_recyler` fixed the error, and therefore the logic
regarding `skb_queue_len(&local->pending[q]) >= 1000` can be reverted to
match what is currently upstream with QSDK.

Alsi refreshed remaning patches after rebase.

Signed-off-by: Sean Khan <[email protected]>
There is an issue when enabling thermal support on newer ath11k firmware.
TX/RX rates are being limited, often times 50% of client's HE
capabilities.

The issue stems from a mismatch in WMI API structure. The range to
throttle is currently "-100°C" to "150°C", this essentially means
"always" throttle.

Integrate patch from dd-wrt which adds missing WMI structures and
proper thermal ranges for IPQ5018, IPQ807x, and QCN9000.

Patch-by: Sebastian Gottschall <[email protected]>
Signed-off-by: Sean Khan <[email protected]>
Every 100 milliseconds, the station sends an "association request" and
the AP adds the peer and the AP responds to the station with an
"association response".

But "association response" takes time to reach the station. Because of
this, the station sends another "association request" to the AP.

In the second associate request, the AP removes the peer and re-adds
the station. Meanwhile, "association response" is reached to station
and station sends "QoS NULL" frame to AP.

The moment the station sends a QoS NULL frame to the ap, the peer on
the AP is deleted and the AP sends a de-authentication to the station.

To fix this issue, increased the assoc timeout period from 100 milli-
seconds to 500 milli seconds.

Signed-off-by: Sean Khan <[email protected]>
fixes: ath11k: fix peer addition/deletion error on sta band migration: d673cb6fe6c03b2be157cc6c5db40481828d282d

the fix for sta band migration raises a new bug which causes the wifi
firmware to crash if you switch between 2 bssid's on the same band. this is
usually caused since the firmware observes 2 stations with the same
bss

Signed-off-by: Sebastian Gottschall <[email protected]>

Update 999-900-bss-transition-handling.patch

Signed-off-by: qosmio <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.