09:32 <mrkiko> slh: thanks!

09:33 <mrkiko> slh: and maybe you also know why upstreaming board-2 blobs for ipq-wifi is no more possible?

11:51 <gch981213> Any suggestions on how we should deal with lengthy sysupgrade scripts for flashing vendor firmware? e.g.: https://github.com/openwrt/openwrt/pull/5063 https://github.com/openwrt/openwrt/pull/10873 . I also have one for ASUS RT-ACRH17. I'm not against the idea of giving users an easy option to go back, but supplying lengthy scripts for every devices

11:51 <gch981213> in all images under the same subtarget doesn't sound sustainable to me.

12:16 <rmilecki> gch981213: thanks a lot for pointing that out

12:36 <owrt-snap-builds> Build [#917](https://buildbot.openwrt.org/master/images/#builders/1/builds/917) of `ath79/generic` failed.

13:21 <oliv3r[m]> mips can run in both BE and LE configurations, right? Is there any (trivial) way to detect this in linux? I think our switchcore peripheral is BE access only so want to be able to detect this runtime

13:22 <oliv3r[m]> (or do readl() and ioread32() already detect this automatically?)

13:32 <gch981213> oliv3r[m]: Pratically nobody mix the usage of the two modes on the same system.

13:33 <oliv3r[m]> the problem is, I want to transition to GENERIC_MIPS_KERNEL, which sets CONFIG_SWAP_IO_SPACE; setting this however, 'breaks' our SoC, because (I think) one of our periphierials (actually a block of peripherials, that is 'in-house developed by realtek', doesn't support the automatic switch. The UART seems to work fine, which goes in line with (as I understood it) that MIPS can at runtime, switch access modes

13:34 <oliv3r[m]> iow https://elixir.bootlin.com/linux/latest/source/arch/mips/include/asm/mach-generic/mangle-port.h#L17

13:43 <gch981213> oliv3r[m]: My understanding is that endianess only describe how CPU treats the data from memory when combining multiple bytes into words.

13:46 <gch981213> oliv3r[m]: I don't think there are specific elements of endianess passed along the system bus outside CPU.

14:02 <mrkiko> gch981213: in my opinion, this may be documented in the wiki for a specific device, and the related scripts linked from there

14:38 <gch981213> mrkiko: The downside of that is: It's hard to keep track of scripts scattered around the wiki. If we made any breaking changes in sysupgrade core, these script may be outdated and end up bricking users devices.

14:39 <gch981213> I've put an idea here: https://github.com/openwrt/openwrt/pull/5063#issuecomment-1448296194

18:05 <nick[m]12> nbd: I have weird mesh errors. I have an 2 ax devices (mt7915e) and 1 ac device (ath10k). Everything works fine between the two ax devices until I start the mesh device on the ac device. Suddenly no communication is possible anymore.

18:28 <nick[m]12> https://github.com/openwrt/mt76/issues/755

19:02 <lmahmutov> hi 2 all. Can anyone help me ) i try to integrate to my custom openwrt build latest mt76 drivers from lede master, and get this erros. I replaced mac80211 folder and mt76 folder

19:02 <lmahmutov> https://pastebin.com/9UZSuJSR