The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped automatically by the mailing list software.
--- Begin Message ---Hi, Recently, a couple of MikroTik devices have been ported from the ar71xx target to the ath79 one (the ath79/generic RB wAP G-5HacT2HnD (wAP AC) <https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=6aaa5ce2c5138877e0f0504c3bd536b40e9af928> [1] and the ath79/nand RB 922UAGS-5HPacD <https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=8f93c05a591bd68e4d8eaa0a8468ce2263762004> [2]). Only after the commits were merged upstream I realised that, since some of the partitions on the SPI NOR storage are sized 4 kB, the CONFIG_MTD_SPI_NOR_USE_4K_SECTORS kernel configuration item is needed. Otherwise, the soft_config partition (it contains the bootloader's settings) can't be modified or, in the worse case, other partitions are accidentally erased when modifying it (you can see the discussion at GitHub's pull request #2791 <https://github.com/openwrt/openwrt/pull/2791> [3]). CONFIG_MTD_SPI_NOR_USE_4K_SECTORS is not enabled by default on ath79/generic or ath79/nand, but used to be in ar71xx/mikrotik and is also in ath79/tiny <http://lists.infradead.org/pipermail/openwrt-devel/2019-November/020358.html> [4] (there was discussion on the mailing list <http://lists.infradead.org/pipermail/openwrt-devel/2019-December/020864.html> also [5]). In order to allow these MikroTik devices correctly write to the partitions (reading works OK right now), as far as I know, there would be three options: 1- Adding the CONFIG_MTD_SPI_NOR_USE_4K_SECTORS to ath79/generic and ath79/nand (i.e., to the whole ath79 target) · PROS: it works · CONS: probably breaks sysupgrade for other devices (?) 2- Forcing conflicting small partitions as read-only · PROS: nothing can be broken · CONS: bootloader settings won't be modifiable (e.g., with rbcfg <https://openwrt.org/packages/pkgdata/rbcfg> [6]) 3- Creating a new ath79/mikrotik subtarget · PROS: it works, and all MikroTik-specific features and tweaks are concentrated there, no technical problems or missing features should arise · CONS: mostly looks like a manufacturer-specific subtarget... Therefore, I would like to ask for your advice, so we can together decide on how to proceed: Q1- Does adding CONFIG_MTD_SPI_NOR_USE_4K_SECTORS now to ath79/generic and ath79/nand break sysupgrade? Q2- Which option among the three ones, or any other, is the best? Thanks, Roger -- [1] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=6aaa5ce2c5138877e0f0504c3bd536b40e9af928 [2] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=8f93c05a591bd68e4d8eaa0a8468ce2263762004 [3] https://github.com/openwrt/openwrt/pull/2791 [4] http://lists.infradead.org/pipermail/openwrt-devel/2019-November/020358.html [5] http://lists.infradead.org/pipermail/openwrt-devel/2019-December/020864.html [6] https://openwrt.org/packages/pkgdata/rbcfg
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
