-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Kernel: Bump mainline from 6.8-rc7 to 6.8 stable, also bump UEFI-edge from 6.7 to 6.8 #6399
Conversation
- Kernel configs updated via ./compile.sh rewrite-kernel-config
- Using ./compile.sh rewrite-kernel-patches
https://github.com/lwfinger/rtl8723du/commits/master/ drivers/net/wireless/rtl8723du/os_dep/usb_intf.c:153:17: error: 'struct usb_driver' has no member named 'drvwrap'
cache/sources/rtl8192eu is added to the kernel before compilation |
Thanks! I found the locations where the driver repos are specified, e.g.
The repo at https://github.com/lwfinger/rtl8723du states that THIS DRIVER IS OBSOLETE AND SHOULD BE REPLACED BY THE rtw88 DRIVERS AT https://github.com/lwfinger/rtw88.git Wouldn't it make sense to skip this (rtl8723du) driver, as well as potentially other now obsolete drivers, for newer kernel versions? This would prevent having to patch them again after each kernel version. After some digging around, I found out that the
So basically, rtl8723du would only be needed in a few cases and can mostly be skipped. |
Went through the list of supported devices by
This would save hassles of potentially needing new patches with new kernel versions and also save a little bit of time on kernel building. |
Also add commit dates to make life prettier and easier The following drivers have been updated with fixes for 6.8 - driver_rtl8811CU_rtl8821C - driver_rtl88x2bu - driver_rtl8811_rtl8812_rtl8814_rtl8821 The following drivers have been updated without specific 6.8 patches: - driver_rtl8189ES (patches for 6.7, deleted two upstreamed patches) - driver_rtl8189FS (patches for 6.7, deleted four upstreamed patches)
@ColorfulRhino welcome to the delights of those ancient vendor network drivers. It's hell. It's also intricate, some boards will work better with the old/deprecated driver, there's a very complex relationship between the driver and the firmware, and general sadness since the network drivers patching is done separately from the other patches and later integrated into the Python patching. The first kernels to be bumped to a new version usually show these problems, although as you've seen some family use different stuff, etc. |
Oh no, what have I gotten myself into... 😂 I just wanted to quickly bump the kernel 🫠 |
…d RTL88x2cs in favor of mainline RTW88 for kernel >=6.8 - RTW8723DS, RTW8723DU is unsupported/deprecated/obsolete by the author since kernel 6.7 in favor of RTW88, so deprecate it for kernel >=6.8 - RTL88x2cs specifically says in its repo: "USE RTW88 NOT THIS DRIVER", so deprecate in favor of RTW88, except for meson64 family - move random RTL88x2cs hook specific for meson64 family in drivers_network.sh to their family config
Resolved all wireless network driver hassles 🥳 The build is now stuck at a later stage (at or after (Can't post to paste.armbian.com because the debug output is too large I guess
Build command used: EDIT:
stacktrace:
|
…y for better visibility and ease of use (e.g. when checking which driver commits should be updated)
Building EDIT: But I guess this will be a problem in every 6.8 kernel, or am I missing something? |
I don't think we have a good mechanism for this, so copy ... Probably it will be fixed upstream soon and patch will be gone anyway. |
It's building successfully now! Yay 🥳
True. |
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.
OK, lets's merge this.
@viraniac Some of your wireless |
sorry, i miss this thread.
Please do not touch anything else related to JetHub devices without my approval. All such changes must go through my review only.
This repository is maintained by myself and my colleagues. The comment appeared when we switched to the rtw88 driver. After we switched back to rtl88x2cs, I decided to keep the comment as motivation for development and to identify issues in rtw88. |
Description
rk3588-edge
./compile.sh rewrite-kernel-config
./compile.sh rewrite-kernel-patches
How Has This Been Tested?
./compile.sh build BOARD=nanopi-r6s BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no BUILD_ONLY="kernel" KERNEL_CONFIGURE=no RELEASE=bookworm
--> build success./compile.sh build BOARD=uefi-arm64 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no BUILD_ONLY="kernel" KERNEL_CONFIGURE=no RELEASE=bookworm
Checklist: