02:51 <KGB-2> https://tests.reproducible-builds.org/openwrt/openwrt_ath79.html has been updated. (98.7% images and 99.9% packages reproducible in our current test framework.)

08:52 <ynezz> hi, does anyone have a clue, why its not possible to install luci-app-wireguard package? https://github.com/openwrt/openwrt/issues/15620#issuecomment-2160146250

08:52 <ynezz> seems to be missing in snapshots and 23.05 as well

08:56 <ynezz> seems to be available in 22.03, interesting

08:58 <ynezz> hm, phase2 is not even attempting to build the package

09:09 <robimarko> Probably because it doesnt exist anymore

09:11 <robimarko> Its functionality seems to be merged into luci-proto-wireguard in 2022: https://github.com/openwrt/luci/commit/6e6fce3eb43ea6899eedc91bebd5713a5d4c773b

10:15 <bodksi> hi I'm interested in running openwrt on the BT homehub 2b (lantiq/danube router from UK) is there a reason it's no longer getting release builds?

10:17 <bodksi> I have 23.05 running on it after a couple of changes increase kernel partition (now 4MiB) and it seems fine

11:22 <ynezz> robimarko: ah, thanks, I was just grepping for `luci-app-wireguard` in the luci.git repo, but with checked out 22.03 branch :P

12:07 <robimarko> I am wondering, what should we do with the straggler 5.15 targets?

12:18 <wigyori> tegra has a testing kernel at 6.6, qoriq has 6.1, octeontx - well, drop?

12:20 <robimarko> Yeah, Gateworks said they are not intersted in octeonxt at all

12:20 <robimarko> But we have at91 and realtek

12:20 <robimarko> Microchip used to update at91, but the person that did it doesnt work there anymore

12:21 <robimarko> And here is the wonderful reply from Microchip: https://github.com/openwrt/openwrt/pull/11918#issuecomment-2043169345

12:21 <wigyori> at91 is on 6.1 - still behind 6.6, but at least not on 5.15

12:21 <wigyori> oh, didn't see that

12:21 <robimarko> Oh, I missed at91 being update

12:22 <robimarko> I honestly doubt anybody runtime tested that

12:22 <robimarko> That only leaves realtek

12:23 <wigyori> given how many switches the realtek target supports, putting that up for removal ("unless anyone steps up") would stir some shit up

12:23 <wigyori> which is good

12:24 <robimarko> realtek target is a mess essentially

12:24 <robimarko> Its full of hacks to get it working

12:24 <robimarko> But yeah, somebody needs to step up to push it

12:25 <wigyori> there is a wip 6.1 PR for it - unsure about its state

12:25 <robimarko> L2 forwarding was broken AFAIK

12:26 <wigyori> "nice"

12:43 <ynezz> what about starting marking such targets as source-only?

12:45 <robimarko> We still need to carry 5.15 for them

12:45 <robimarko> I dont think its worth it for a single target

12:47 <ynezz> ah, I've missed that part, good point

12:56 <ynezz> one way is to ask svanheule whats the preference/plan or go with wigyori 's proposal? :P

14:53 <owrt-images-builds> Build [#260](https://buildbot.openwrt.org/images/#/builders/188/builds/260) of `master_realtek/rtl931x` failed.

23:04 <bodski> Hi again, so I'm trying out 23.05.3 on an old lantiq-danube router (bt homehub 2 type b) and seems to work ok so far (after enlarging kernel partition)...

23:05 <bodski> except for rebooting which hangs part way through kernel hardware init, power-on boot is fine however

23:08 <bodski> I've tracked it down to what appears to be a register being incorrectly configured and can work around it by doing a memory write in uboot bootcmd before booting the kernel

23:11 <bodski> I think, according to the device tree files, that it's the RCU register, does anyone have any pointers to how this could be fixed in the kernel? i.e. avoid the need for the extra uboot

23:16 <bodski> *uboot command