Message ID | 20200421212207.8482-1-hauke@hauke-m.de |
---|---|
Headers | show |
Series | mac80211: Update to version 5.7-rc2 | expand |
On 21.04.20 23:22, Hauke Mehrtens wrote: > This updates mac80211 in OpenWrt to version 5.7-rc2. > This update contains ath11k and many other ieee80211ax updates. > ath11k only works on the ipq807x devices. > > I tried to start a discussion how we want to go forward with the > wireless subsystem we ship in the next OpenWrt release: > https://lists.infradead.org/pipermail/openwrt-devel/2020-March/022198.html > > I would prefer if we apply this to master and then continuously update > to match more recent kernel versions till we are at an LTS kernel > version. I assume that the kernel 5.9 or 5.10 will be the next LTS > version. Using a normal kernel release as a base will make providing > (security) updates much harder. > Hi Hauke, It seems I missed that one. +1 for option 4 I'm also in favor of avoiding non-LTS stuff as it puts pressure on timely updates. It allows bleeding edge stuff while being still (more easily) maintainable when a release moves to maintenance. Regards, Koen
On 2020-04-21 23:22, Hauke Mehrtens wrote: > This updates mac80211 in OpenWrt to version 5.7-rc2. > This update contains ath11k and many other ieee80211ax updates. > ath11k only works on the ipq807x devices. > > I tried to start a discussion how we want to go forward with the > wireless subsystem we ship in the next OpenWrt release: > https://lists.infradead.org/pipermail/openwrt-devel/2020-March/022198.html > > I would prefer if we apply this to master and then continuously update > to match more recent kernel versions till we are at an LTS kernel > version. I assume that the kernel 5.9 or 5.10 will be the next LTS > version. Using a normal kernel release as a base will make providing > (security) updates much harder. > > You can also find these patches in my staging tree: > https://git.openwrt.org/?p=openwrt/staging/hauke.git;a=shortlog;h=refs/heads/mac80211-5.6 > > Please test this and report any regressions you see compared to the > version currently shipped in OpenWrt master. I tested this and found that the debugfs phy rate control settings directory was not in the right place. It is supposed to be in /sys/kernel/debug/ieee80211/phy0/rc but it somehow ended up in /sys/kernel/debug/rc instead. - Felix
On 4/22/20 7:33 PM, Felix Fietkau wrote: > On 2020-04-21 23:22, Hauke Mehrtens wrote: >> This updates mac80211 in OpenWrt to version 5.7-rc2. >> This update contains ath11k and many other ieee80211ax updates. >> ath11k only works on the ipq807x devices. >> >> I tried to start a discussion how we want to go forward with the >> wireless subsystem we ship in the next OpenWrt release: >> https://lists.infradead.org/pipermail/openwrt-devel/2020-March/022198.html >> >> I would prefer if we apply this to master and then continuously update >> to match more recent kernel versions till we are at an LTS kernel >> version. I assume that the kernel 5.9 or 5.10 will be the next LTS >> version. Using a normal kernel release as a base will make providing >> (security) updates much harder. >> >> You can also find these patches in my staging tree: >> https://git.openwrt.org/?p=openwrt/staging/hauke.git;a=shortlog;h=refs/heads/mac80211-5.6 >> >> Please test this and report any regressions you see compared to the >> version currently shipped in OpenWrt master. > I tested this and found that the debugfs phy rate control settings > directory was not in the right place. It is supposed to be in > /sys/kernel/debug/ieee80211/phy0/rc but it somehow ended up in > /sys/kernel/debug/rc instead. Thanks for reporting Felix, This commit broke it: https://git.kernel.org/linus/52e04b4ce5d03775b6a78f3ed1097480faacc9fd You can revert it, then it works again. I reported this upstream: https://marc.info/?l=linux-wireless&m=158758952226370&w=2 Hauke