[OpenWrt-Devel] RFT: Add support for kernel 5.4

[John Crispin]

On 28.02.20 21:30, Stefan Lippers-Hollmann wrote:
> Hi
> 
> On 2020-02-28, mail at adrianschmutzler.de wrote:
>> Hi,
>>
>>> On 2020-02-28, Koen Vandeputte wrote:
> [...]
>>> All supported targets have been provided with kernel 5.4 as the "Testing
>>> kernel".
>>> This means you can enable 5.4 by selecting "Global --> use the testing kernel
>>> version" within menuconfig.
>>
>> Thanks for your work.
>>
>> By moving ag71xx to files-4.19 on ath79, I suspect 4.14 is broken now on
>> this target.
>> So, we should either copy that to files-4.14 as well or remove the
>> remaining 4.14 files there as well (where I'd prefer the latter).
> 
> ath79 with kernel 4.14 has already been (mostly) broken by "ath79: add
> new ar934x spi driver" (ebf0d8dadeca443121f4f597c51bf6591e341caf), which
> does break the (shared between all kernel versions) DTS definitions for
> NAND based ath79 devices (breaking compilation with kernel 4.14).
> 
> Because of "FS#2524 - ath79-tiny: TP-Link TL-WR941ND v2.4: Marvel
> MV88E6060 regression between kernel v4.14 and v4.19"
> https://bugs.openwrt.org/index.php?do=details&task_id=2524 I still do
> regularly build ath79 with kernel 4.14, but in order to finish the build
> I do need to comment out the affected devices:
> 
> $ grep \# ath79-k414.diff
> +#TARGET_DEVICES += tplink_cpe210-v1
> +#TARGET_DEVICES += tplink_cpe220-v2
> +#TARGET_DEVICES += tplink_cpe510-v1
> +#TARGET_DEVICES += tplink_cpe510-v2
> +#TARGET_DEVICES += tplink_cpe510-v3
> +#TARGET_DEVICES += tplink_cpe610-v1
> +#TARGET_DEVICES += tplink_tl-wdr3500-v1
> +#TARGET_DEVICES += tplink_tl-wdr3600-v1
> +#TARGET_DEVICES += tplink_tl-wdr4300-v1
> +#TARGET_DEVICES += tplink_tl-wdr4300-v1-il
> +#TARGET_DEVICES += tplink_tl-wr842n-v2
> +#TARGET_DEVICES += tplink_wbs210-v2
> +#TARGET_DEVICES += tplink_wbs510-v1
> +#TARGET_DEVICES += tplink_wbs510-v2
> +#TARGET_DEVICES += ubnt_bullet-m-xw
> +#TARGET_DEVICES += ubnt_lap-120
> +#TARGET_DEVICES += ubnt_litebeam-ac-gen2
> +#TARGET_DEVICES += ubnt_nanobeam-ac
> +#TARGET_DEVICES += ubnt_nanostation-ac
> +#TARGET_DEVICES += ubnt_nanostation-ac-loco
> +#TARGET_DEVICES += ubnt_nanostation-loco-m-xw
> +#TARGET_DEVICES += ubnt_nanostation-m-xw
> +#TARGET_DEVICES += comfast_cf-e120a-v3
> +#TARGET_DEVICES += dlink_dir-825-c1
> +#TARGET_DEVICES += dlink_dir-835-a1
> +#TARGET_DEVICES += iodata_etg3-r
> +#TARGET_DEVICES += iodata_wn-ag300dgr
> +#TARGET_DEVICES += ocedo_raccoon
> +#TARGET_DEVICES += pcs_cap324
> +#TARGET_DEVICES += pcs_cr3000
> +#TARGET_DEVICES += pcs_cr5000
> +#TARGET_DEVICES += pisen_wmb001n
> +#TARGET_DEVICES += qihoo_c301
> +#TARGET_DEVICES += sitecom_wlr-7100
> +#TARGET_DEVICES += teltonika_rut955
> +#TARGET_DEVICES += wd_mynet-n750
> +#TARGET_DEVICES += wd_mynet-wifi-rangeextender
> +#TARGET_DEVICES += winchannel_wb2000
> +#TARGET_DEVICES += zbtlink_zbt-wd323
> 
> Admittedly, the affected TL-WR941ND v2 (4/32) is barely worth the effort
> anymore.
> 
> Regards
> 	Stefan Lippers-Hollmann
> 
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> 

sorry for being dense here. what are you trying to tell us ? is there a 
bug for which you propose a patch or is this a report or just a rant ? 
honestly cant figure it out
    John

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel