<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Le 15 mars 2020 à 13:52, <<a href="mailto:mail@adrianschmutzler.de" class="">mail@adrianschmutzler.de</a>> <<a href="mailto:mail@adrianschmutzler.de" class="">mail@adrianschmutzler.de</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi,<br class=""><br class=""><blockquote type="cite" class="">-----Original Message-----<br class="">From: Thibaut [<a href="mailto:hacks@slashdirt.org" class="">mailto:hacks@slashdirt.org</a>]<br class="">Sent: Sonntag, 15. März 2020 13:39<br class="">To: <a href="mailto:mail@adrianschmutzler.de" class="">mail@adrianschmutzler.de</a><br class="">Cc: OpenWrt Development List <<a href="mailto:openwrt-devel@lists.openwrt.org" class="">openwrt-devel@lists.openwrt.org</a>><br class="">Subject: Re: [OpenWrt-Devel] [PATCH v2] ar71xx: add support for RB SXTsq<br class="">2nD<br class=""><br class="">Hi,<br class=""><br class=""><blockquote type="cite" class="">Le 15 mars 2020 à 13:05, <<a href="mailto:mail@adrianschmutzler.de" class="">mail@adrianschmutzler.de</a>><br class=""></blockquote><<a href="mailto:mail@adrianschmutzler.de" class="">mail@adrianschmutzler.de</a>> a écrit :<br class=""><blockquote type="cite" class=""><br class="">Hi,<br class=""><br class=""><blockquote type="cite" class="">-----Original Message-----<br class="">From: openwrt-devel [mailto:openwrt-devel-<br class=""></blockquote></blockquote><a href="mailto:bounces@lists.openwrt.org" class="">bounces@lists.openwrt.org</a>]<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">On Behalf Of Thibaut VARÈNE<br class="">Sent: Sonntag, 15. März 2020 11:35<br class="">To: <a href="mailto:openwrt-devel@lists.openwrt.org" class="">openwrt-devel@lists.openwrt.org</a><br class="">Cc: Thibaut VARÈNE <<a href="mailto:hacks@slashdirt.org" class="">hacks@slashdirt.org</a>><br class="">Subject: [OpenWrt-Devel] [PATCH v2] ar71xx: add support for RB SXTsq<br class=""></blockquote></blockquote>2nD<br class=""><blockquote type="cite" class=""><br class="">the ar71xx target will only be supported in already released 19.07 branch<br class=""></blockquote>and be removed afterwards.<br class=""><blockquote type="cite" class=""><br class="">Consequently, we do not accept any device support for this target<br class=""></blockquote>anymore.<br class=""><blockquote type="cite" class=""><br class="">Please work with the ath79 target instead, which is meant to replace ar71xx<br class=""></blockquote>and is also already included in 19.07.x (though Mikrotik devices have only<br class="">been added in master).<br class=""><br class="">I had a feeling this would be the answer.<br class=""><br class="">At least the code is there for those who need it, and it details the necessary<br class="">bits to get this hardware to work.<br class=""><br class="">Regarding moving to ath79 there are a number of issues which I’m trying to<br class="">wrap my head around.<br class=""><br class="">Specifically, right now we have a (imo very convenient) « one image fits them<br class="">all » approach for ar71xx-based mikrotik devices. This relies on load-time<br class="">detection of the hardware which is based part on the kernel command string<br class="">passed by the routerboot bootloader, and part on actual hardware detection<br class="">at kernel load time (MIPS machine name).<br class=""><br class="">I don’t know yet if it is possible to transcribe this in a DTS world: routerboot<br class="">doesn’t support DTS, so my impression is that in order to maintain this<br class="">feature an intermediary loader is needed, which is going to be non-trivial.<br class=""><br class="">Second, I don’t know if the machine name detection can also be<br class="">implemented in DTS: I was under the impression that all DTSes define a fixed<br class="">string, there doesn’t seem to be a mechanism to lift that string from the mtd<br class="">device as is currently done on ar71xx. Is this correct?<br class=""></blockquote><br class="">The way devices were detected in ar71xx also caused a lot of problem, as it was very confusing even to seasoned developers. Now, we just build a separate image for each device, so we do not need this mess of scripts for detection anymore.<br class=""></div></div></blockquote><div><br class=""></div>I believe this is a waste of resources and a very suboptimal approach. I’m not sure I’m interested in spending time on this :P</div><div><br class=""></div><div>Some devices share the exact same hardware and differ only in (marketing) name, as evidenced by:</div><div><a href="https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=5ac974f2145c770431a6eb7e006dd086b70224b1" class="">https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=5ac974f2145c770431a6eb7e006dd086b70224b1</a></div><div><br class=""></div><div>(this device uses the 911L platform)</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="">Just have a look at how the few ath79 devices are implemented, but note that they will be moved to a mikrotik subtarget soon as indicated by Roger already.<br class=""></div></div></blockquote></div><br class=""><div class="">I’ve offered in this thread a couple patches to align the ath79 implementation on the existing ramips one wrt mtd partitioning and naming.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Thibaut</div></body></html>