00:48 <SlimeyX> found it https://lldpd.github.io/usage.html

01:46 <KGB-0> https://tests.reproducible-builds.org/openwrt/openwrt_lantiq.html has been updated. (96.2% images and 99.9% packages reproducible in our current test framework.)

02:15 <djfe> lantiq was reduced to subtarget xrx200 being set to source-only. Ansuel mentioned being positive about lantiq gswip code (switch) being fixed during the release candidate phase. so this might take some time still but it's no guarantee either. With the bug unfixed it would be irresponsible publishing 5.15 on xrx200

02:15 <djfe> Mailinglist thread on the topic: http://lists.openwrt.org/pipermail/openwrt-devel/2023-May/thread.html#40970

02:16 <slh> to be fair, in practice lantiq is effectively xrx200 only, anything older than xrx200 is hardly usable/ useful

02:19 <djfe> yeah ^^

02:24 <djfe> but we might see support for newer targets at some point (grx based stuff)

02:26 <slh> which is great, if those devices would be bundled with usable wireless cards as well (and not lantiq/intel/maxlinear wav600)

03:15 <hurricos> How would a branch to a slightly higher address cause a data abort?

03:15 <hurricos> I'm on ARM and trying to boot a zImage using `go`, since `bootm` isn't available (aruba)

03:16 <hurricos> https://forum.openwrt.org/t/adding-support-for-aruba-ap135/118032/10 -- but if I ever jump to an address higher than $PC, I get a 'data abort'.

03:16 <hurricos> I can branch lower, i.e. I can cause an infinite loop.

03:16 <hurricos> I also get 'data abort' when attempting to use `mcr` to adjust the MMU.

03:18 <hurricos> I crash on the first branch in the .start section of arch/arm/boot/compressed/head.S

03:18 <hurricos> (this branch is implied since a few .words are declared in the ... I think that's the "stack" technically)

03:18 <hurricos> > How would a branch to a slightly higher address cause a data abort?

03:19 <hurricos> I could imagine the MMU is tracking my work and making sure I don't try to jump to a random address ....

03:19 <hurricos> but if so, I'm unsure how the original code stops the MMU from doing that, as I also get data aborts from using mcr to touch the machine-specific registers to stop it

03:21 <hurricos> seem to me rock vs. hard place :|

03:22 <hurricos> perhaps I cannot branch because the addresses I'm targeting aren't marked as executable yet

03:23 <hurricos> I have not seen any resources for marking addresses as executable however

03:24 <hurricos> In particular, I definitely expected to see that type of thing under arch/arm/boot/{*,*/*,*/*/*}.S

03:26 <hurricos> At this point I am literally cycling between vbindiff and `r2 -a arm.as -b 32 zImage` and `scp -O` to try understanding which instructions here are causing the data abort

03:26 <hurricos> I am clear in understanding that the data abort message is generated by a function which resides in u-boot and whose address has been inserted into the interrupt vector, so as to be accessible by the MMU via an interrupt.

03:27 <hurricos> By truncating down carefully, I've narrowed the data-abort down to the `b 0x3c` (encoded as `05 00 00 EA`)

03:28 <hurricos> (.... at address 0x20)

07:22 <owrt-snap-builds> Build [#870](https://buildbot.openwrt.org/master/images/#builders/54/builds/870) of `ramips/mt7620` completed successfully.

07:27 <owrt-2203-builds> Build [#253](https://buildbot.openwrt.org/openwrt-22.03/images/#builders/37/builds/253) of `ramips/rt3883` completed successfully.

07:56 <KGB-2> https://tests.reproducible-builds.org/openwrt/openwrt_ath79.html has been updated. (98.6% images and 100.0% packages reproducible in our current test framework.)

13:21 <KGB-0> https://tests.reproducible-builds.org/openwrt/openwrt_x86.html has been updated. (100.0% images and 100.0% packages reproducible in our current test framework.)

16:48 <georgep56_> Hey guys. I'm running snapshot builds on two Linksys WHW03 V2 devices and for me they are dead stable. Can I do anything to propose the version for the next stable release?

16:54 <dwfreed> there's nothing special to do; if support is in snapshot, then it'll be in the next release

16:54 <dwfreed> I don't think 23.x has been forked off yet

16:56 <georgep56_> Okay thanks. I've read that (obviously) it helps to report any bugs, but - despite trying - I can't find any 😁

16:57 <Borromini> any minute now =D

16:58 <georgep56_> It's a real ball-ache having to reinstall everything just to add any extra software 🤕

16:59 <georgep56_> Borromini: 😂😂

18:14 <KGB-1> https://tests.reproducible-builds.org/openwrt/openwrt_sunxi.html has been updated. (0% images and 100.0% packages reproducible in our current test framework.)

20:14 <Znevna> is still beeing worked on? :p https://github.com/openwrt/openwrt/issues/9248

20:14 <Znevna> being*

20:16 <Borromini> :P

20:25 <Gramdalf> What's the best way to send a notice to the syslog in a /etc/init.d/ script? Would it be using `logger`?

20:25 <jakllsch> probably

20:26 <Gramdalf> Are there any examples of how the base system does it?

22:12 <swalker> updated openwrt/upstream, https://sdwalker.github.io/uscan/index.html

22:16 <owrt-snap-builds> Build [#861](https://buildbot.openwrt.org/master/images/#builders/19/builds/861) of `ramips/mt7621` failed.

23:06 <KGB-1> https://tests.reproducible-builds.org/openwrt/openwrt_tegra.html has been updated. (100.0% images and 100.0% packages reproducible in our current test framework.)