01:10 <KGB-2> https://tests.reproducible-builds.org/openwrt/openwrt_kirkwood.html has been updated. (89.3% images and 100.0% packages reproducible in our current test framework.)

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

07:29 <nbd> f00b4r0: ping

07:29 <nbd> i may have a possible workaround for the mt7621 + mt7915 stability issue

07:29 <nbd> f00b4r0: https://nbd.name/p/9d1c040b

07:30 <nbd> based on my tests, the reset issue seems to be related to using the second pcie link for the 5 ghz band

07:30 <nbd> the patch disables that and forces 5 ghz onto the primary pcie link

08:27 <owrt-images-builds> Build [#127](https://buildbot.openwrt.org/images/#/builders/197/builds/127) of `openwrt-23.05_mvebu/cortexa53` completed successfully.

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

15:02 <\x> https://www.acwifi.net/28865.html mtk wifi 7

15:03 <\x> 3c a73

15:04 <\x> https://corp.mediatek.com/news-events/press-releases/mediatek-expands-wi-fi-7-portfolio-with-new-chipsets-for-mainstream-devices

15:04 <jakllsch> fun

15:05 <\x> uooohhh a73 builds on ipq60xx robimarko

15:06 <\x> but yeah more and more gonna have a73 at the very least next gen, ipq95xx is real a73, 53xx is likely another kryo silver which is a73 compatible

15:09 <\x> these triple core chips seems downbins to me

15:10 <\x> downbins from 4c, not a dedicated chip

15:10 <\x> either way seems good if this is their next gen lower-end stuff

15:32 <hauke> MT7988D is interesting, it looks like it has 3 a73 cores, 1 x 2.5G PHY and 4 x 1G PHYs. Maybe a SiP with existing dies like normal MT7988 with fussed off a73 core and extra die for the PHY and the switch, but maybe also a new SoC

15:33 <\x> if its a new soc and its their lower end (compared to 7986/7981 era) having 3 cores on lower end is welcome :D

15:35 <\x> seems a downbin to me though

15:35 <\x> not a dedicated chip

15:39 <hauke> yes probably a SiP with existing chips.

17:27 <cmonroe> 7988D is so similar to the 7988A that we could use the same device tree as 7988A.. just turn off the extra CPU core. it has 1 less PCIe bus and USXGMII I think. https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=d0a2b3f824c5e283caf31ceea49abf3022e7dc51

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

22:27 <n3ph> I see wierd network behavior on current snapshot on a Archer C50 v6. It seems no IPv4 is entering nor leaving the device - in failsafe and normal mode. no DHCP network replies(!), but ARP requests for a possible lease never recieved by client. WAN port only works on IPv6, IPv6 link local connectivity only given in failsafe boot. It seems vlan config related, I suspect

22:28 <n3ph> https://github.com/openwrt/openwrt/commit/e8084a3c3b94adcff6c9f62554cf8d9d1871fe25, unsure if worth to bisect...

22:29 <n3ph> No other changes (https://github.com/openwrt/openwrt/commits/main/target/linux/ramips/dts/mt7628an_tplink_archer-c50-v6.dts) since support (https://github.com/openwrt/openwrt/commit/e9ac1b19e0f3d383ab83373c261bfb5527a29521)

22:32 <n3ph> IPv4 access given via Wifi after enabling through failsafe mode!

23:00 <owrt-images-builds> Build [#396](https://buildbot.openwrt.org/images/#/builders/51/builds/396) of `master_ramips/rt3883` completed successfully.

23:27 <schmars[m]> nbd: i'll give the pcie patch a try next weekend, back from holiday on friday