05:40 <owrt-images-builds> Build [#319](https://buildbot.openwrt.org/images/#/builders/39/builds/319) of `main_realtek/rtl839x` completed successfully.

07:35 <owrt-images-builds> Build [#312](https://buildbot.openwrt.org/images/#/builders/54/builds/312) of `main_malta/be` completed successfully.

07:40 <owrt-images-builds> Build [#314](https://buildbot.openwrt.org/images/#/builders/27/builds/314) of `main_ipq806x/chromium` completed successfully.

07:49 <owrt-images-builds> Build [#313](https://buildbot.openwrt.org/images/#/builders/59/builds/313) of `main_bmips/bcm6328` completed successfully.

07:59 <owrt-images-builds> Build [#307](https://buildbot.openwrt.org/images/#/builders/24/builds/307) of `main_mvebu/cortexa53` completed successfully.

08:31 <owrt-images-builds> Build [#315](https://buildbot.openwrt.org/images/#/builders/25/builds/315) of `main_sunxi/cortexa8` completed successfully.

08:35 <owrt-images-builds> Build [#314](https://buildbot.openwrt.org/images/#/builders/63/builds/314) of `main_imx/cortexa53` completed successfully.

08:36 <owrt-images-builds> Build [#317](https://buildbot.openwrt.org/images/#/builders/52/builds/317) of `main_omap/generic` completed successfully.

17:09 <nbd> f00b4r0: new mt76 version is pushed - it contains some additional fixes

17:09 <nbd> should also help with memleak issues

17:19 <djfe> <3

18:12 <plappermaul> Maybe someone can merge this https://github.com/openwrt/openwrt/pull/19362 from the Wunderlich team. The guys are really helping to get the Realtek target in shape.

18:18 <f00b4r0> nbd: cool thanks. I'll *try* to update the test location tomorrow but I'm really under water right now, *sigh*

20:31 <pizzaman> hello, I was wondering what the requirements are to get "new" model support added to OpenWRT. This question arises from a simple patch that I found someone else made (https://github.com/openwrt-xiaomi/openwrt/commit/81bfbed6eefb29ba35499ae09bf80d13ae2496b1) that "supports" my device ASUS RT-AX1800S (v2). I put supports in quotes b/c while network switching works, the WAN port is not functional (so

20:37 <Rondom> pizzaman: The link you posted is not a link to the OpenWrt repo

20:44 <Rondom> if you manage to fix it, maybe you can submit a PR to add it to OpenWrt ;-)

20:44 <slh> pizzaman: in general it 'just' needs someone to step up and propose a working pull request on github (or via mail to the mailing list), what working means is up to discussion, but at least the wired ports generally should work

20:45 <hauke> Ansuel: did you had a look at the EcoNet EN75xx MIPS SoC PR? https://github.com/openwrt/openwrt/pull/19021

20:50 <slh> pizzaman: obviously the PR will be reviewed, so be prepared to react to comments and do changes accordingly, some patience and persistence will be needed

20:51 <pizzaman> <Rondom>: yeah I know it's not to openwrt. The "owner" of that repo put this together, and their patch (the link I posted) results in a mostly working device.

20:52 <pizzaman> modulo the WAN port not receiving any ethernet frames... so it's not quite working I guess

20:53 <Rondom> most device support pull requests come from one person owning and using that device

20:53 <Rondom> people scratching their own itch so to say

20:53 <pizzaman> even if the code to support it comes from someone else?

20:54 <pizzaman> it's only a new dts file and a few configuration file changes, so no actual code in there. I think I should be able to "answer" questions (famous last words, I know)

20:54 <Rondom> you give credit where credit is due of course

20:54 <pizzaman> ofc

20:55 <Rondom> but sometimes one person gives up and another person picks it up a year later or so. There are some device support PRs where that is the case

20:55 <pizzaman> so, is there a way to indicate that this only works partially? (i.e., no WAN port)?

20:55 <Rondom> I have not looked at the details, but ideally we would get the WAN port working I think

20:56 <slh> the problem with that PR would be that it's not signed off by original author, so you can't just take it without that

20:56 <Rondom> true

20:56 <Rondom> contacting that author might be a good idea then

20:56 <slh> the good news, remittor is kind of active on the forum, so you might be able to talk to him

20:56 <pizzaman> ok, we'll reach out to that person and encourage them to send a PR

20:57 <pizzaman> re remittor that's exactly what I was thinking. well tbh, I was wondering why they didn't yet submit a PR for the many devices that sem to be supported by their build system

20:58 <slh> keep in mind, technical aspects can be fixed, copyright question can't (unless the original author actively cooperates), so those must be 101% correct

20:59 <pizzaman> slh: hence my question above ;-)

21:02 <pizzaman> One has to wonder whether a dts file is copyrightable. It's not that one can express the location of e.g., MMIO registers in a different ways (if we discount different representations of the same numeric value)?

21:03 <slh> DTS itself is debatable, but I don't think anyone would want to take a legal discourse about that (so it's easier to reject, than to discuss legalese)

21:04 <slh> the good part, the DTS is explicitly declared as // SPDX-License-Identifier: (GPL-2.0 OR MIT), but it still needs to be signed off

21:05 <pizzaman> yeah, IANAL so I would not know anyways. I registerd for a forum account and will try to bug remittor

21:05 <pizzaman> thanks for your patient help, I'd love to get this model supported by openwrt

21:05 <slh> I just approved your account

21:14 <pizzaman> thanks, let's see what remittor says