-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
mvebu: add linux 6.1 testing kernel #12938
Conversation
To start migration to Kernel 6.1 we copy all existing patches from 5.15. Signed-off-by: Stefan Kalscheuer <stefan@stklcode.de>
Remove the following patches: 100-ARM-dts-turris-omnia-configure-LED-0-pin-function-to [1] 101-ARM-dts-turris-omnia-enable-LED-controller-node [2] 702-net-next-ethernet-marvell-mvnetaMQPrioOffload [3] 703-net-next-ethernet-marvell-mvnetaMQPrioFlag [4] 704-net-next-ethernet-marvell-mvnetaMQPrioQueue [5] 705-net-next-ethernet-marvell-mvnetaMQPrioTCOffload [6] 710-v6.2-phy-marvell-phy-mvebu-a3700-comphy-Reset-COMPHY-regi [7] Manually rebased: 902-drivers-mfd-Add-a-driver-for-IEI-WT61P803-PUZZLE-MCU All other patches automatically rebased [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=94a29bffdd59498382131fd428fed221f5c96def [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=40624346b7ae0c2b1209fc9993ea30699e512c50 [3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=75fa71e3acadbb4ab5eda18505277eb9a1f69b23 [4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e7ca75fe6662f78bfeb0112671c812e4c7b8e214 [5] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e9f7099d0730341b24c057acbf545dd019581db6 [6] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2551dc9e398c37a15e52122d385c29a8b06be45f [7] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cd1e1735aeab49abc679218a79ee764c0d394880 Signed-off-by: Stefan Kalscheuer <stefan@stklcode.de>
Start 6.1 migration with a full copy of the current stable config. Signed-off-by: Stefan Kalscheuer <stefan@stklcode.de>
With an initial set of patches and configs in place let's start testing with kernel 6.1. Run-tested on the cortexa9 subtarget (WRT1900ACS, Turris Omnia) Tested-by: Etienne Champetier <champetier.etienne@gmail.com> Signed-off-by: Stefan Kalscheuer <stefan@stklcode.de>
missing kconfig. |
Oops 🙈 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here what I did a week ago, which is pretty close to what you did (modulo the commit description): https://github.com/champtar/openwrt/tree/mvebu-6.1
I also needed CONFIG_UNUSED_BOARD_FILES=n
when building Turris Omnia.
Turris Omnia works fine (vlan_filtering=1 finally fixed, wifi 2.4 & 5) except leds are not working (maybe we need new versions of patch 100 & 101)
Interesting. I also ran a build for the Omnia (but as I don’t have a spare device on hand for testing, did not flash it yet) without this. |
I did not remove patches 103 and 104 which initialize the multi-color LEDs. Seems you removed them as upstreamed 🤔 |
Nice, i think I just went too fast and deleted all of them as a group without checking |
I'll try to redo a clean build to see if it still pop-up for me |
Built all the wrtpac targets, tested on: mamba bootlog Anyone know if the |
Thanks for testing. The patch was introduced in 2e1f6f1 (Kernel 4.4) Related to an upstream fix for the Armada 3700 platform (since 5.12) If I get it right, the patch should still affect the cortexa9 subtarget. But I am unsure, if this is still an issue to be patched... This exact patch did not make it upstream, so I kept it for 6.1 as well. |
IIRC, dtaht reported issue and ndb resolved. Tried to find the old issue but meta data seems to have gone walkabout. I do not use the patch in my personal build and have noticed no issue, but I use MQPrio so unsure as to the default fq_codel. |
That should be in Your e-mail box, unless You got rid of it. It's this issue: #5411. |
Thanks for the reference. It's the first time I stumble upon that topic, bus as I have a test device wired up, I just built 2 versions with and without the patch and ran the benchmarks: Test device: Test client: Test commands
Results with patch 700
Results without patch 700
(both results repeatable with minor deviations) Conclusion Yep, we definitely still have a minor fairness problem on cortexa9 without the patch. So I'd say, it is still relevant. |
Thanks for clearing this. If someone want's to pursue this issue on netdev mailing list (don't know if it was ever brought up there) please add @rmk92 (Russell King) to recipients, as he's most active contributor to that driver. |
36fa148
to
74ca188
Compare
|
Works good on Cobra |
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083] |
Rebased onto current main branch with |
how can I select the 6.1 kernel? I cloned this repo, enabled experimental features on make menuconfig but I cant find the use testing kernel version option. |
I was not pulling the correct branch. |
modfiy makefile KERNEL_PATCHVER:=5.15 |
if this could be rebased to master then i would test it for solidrun clearfog pro |
i changed target/linux/mvebu/Makefile to edit: dang... same error as pedrom, was on main :P |
i am unable to build:
|
Looks like the rtl8812 drivers fail to compile. At least that's not a default package for any mvebu device, so probably not the right place to discuss this issue. That particular issue is already addressed in #12746 |
i have a clearfog solidrun where i can put in different m2 wifi cards or usb cards without that driver it works |
I understand the issue, I have MT76 Wi-Fi cards, an LTE modem and some other non-standard periphery as well that, but that does not make any of them an mvebu-specific issue. It’s an out-of-tree driver after all, so it can and should be fixed separately. For the Linksys WRT-series even the standard driver (mwlwifi) is not ready for 6.1 in the main tree. 6.1 migration has just begun, so you very likely will find quite a few drivers across the tree that need additional work. If you need one of them, you could patch the driver, test and provide feedback for already present patches or wait until maybe someone will fix it.
No, that’s not true. Even if this PR will get merged, default is still 5.15. We only introduce 6.1 as testing kernel. |
ah i see, i thought 6.x is going to be default soon for mvebu. |
f1198c1
to
74f9a2b
Compare
@anomeome please build another image with PPPoE |
I've merged the PR. |
For further discussion please use #13213 |
Introduce initial 6.1 testing kernel support for the mvebu target.
Removed 7 upstreamed patches and rebased the others.
Build and run-tested on a Linksys WRT1900ACS (this specific device requires some additional fixes to compile the "mwlwifi" drivers, see #12940)
dmesg output
(some old test config with 3 VLANs, 2x3 WiFi networks, Wireguard and some other stuff)