Re: [PATCH 1/5] uqmi: support C reserved keywords in upstream JSON files
Hi Jean, On Wed, 10 Apr 2024 12:25:05 +0200 Jean Thomas wrote: > Add a dummy prefix in case a name in the upstream JSON files is a > C reserved keyword. > > This is the case with the "Register" element of the new "Configure > Profile Event List" message. > > Signed-off-by: Jean Thomas thanks. I merged your serie after rebasing them to the new paths. Regards, lynxis ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Status of snapshot builds for omap target
Hi Raylynn, I've it on my list to test it again on the beagleboard black and re-enable it if it works with the older ethernet driver which doesn't have the hardcoded VLAN tags. Best, lynxis ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: makefile debugging
Hi Tim, > I seem to recall a way to ask OpenWrt's build system to output a list > of all variable values used in the build but can't find it documented > or in my notes. Does anyone know how to do that? > > Also, is there a way to output a post-processed Makefile after all the > define foo gets done? I find it pretty difficult to work through the > build system, especially when working with images. For packages at least this works for me: TOPDIR=$(pwd) make --no-print-directory -C package/network/services/unetd/ val.PKG_CONFIG_DEPENDS Best, lynxis PS. original seen on https://github.com/ads-tec/sbom-openwrt/blob/6baf6702ffa1d3666db4aeca5084fc79569977f8/lib/utils.py#L138 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Mark lantiq and omap as source only
Hi Paul, > I haven’t seen much progress happening regarding bringing the targets lantiq > or omap to Kernel 5.15. That fact is currently the last blocker for branching > another release. > Instead of postponing another release I’d like to mark both targets as > source-only and do the 23.05 branch, starting with a RC0. If either of the > two targets are fixed within the RC phase, they should be re-added, as > discussed during the last meeting. what are the problems with lantiq 5.15? For omap: - The upstream kernel changed the ethernet default and the driver will use 2 static vlan ids (configurable via dts) to tag the traffic of port 1 and port 2. ACK for OMAP. I'll try to fix it before the release. Best, lynxis ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 22.03 expat - CVE-2022-43680/CVE-2022-40674
Hi Peter, I've updated the expat of openwrt-22.03 branch to 2.5.0. Best, lynxis ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [RFC] dropping of $(AUTORELEASE) feature
Hi, > I agree that this increases maintenance burden but I believe that a > CI side solution for those > conflicting-because-of-deviating-PKG_RELEASE situations would be the > better course of action. I would also like to drop the AUTORELEASE feature. I would like to have a specific version in the tree. AUTORELEASE makes it also harder to rebuild OpenWrt for reproducible builds when the git tree is not available. What could we do to make it easier for the package maintainers? Add a linter script to warn if a Makefile or any file under a package has been modified but not the pkgversion or pkgrelease? Best, lynxis ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
OpenWrt 21.02 branch
Hi, I've created branches for OpenWrt 21.02. Even there is still a lot of work to be done for the next release we decided to branch now. This allow us to stabilize 21.02 and make it ready for release. Further more patches has been piling up which couldn't merged into master before the branch for the next release (e.g. linux 5.10). Best, lynxis -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgpkyTrPLNH2p.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: ramips: add support for Xiaomi Mi Router 4AC (100M Edition)
Hi Sorin, do you know if the Xiaomi Mi Router 4A is the same? I've a router 4a (100m) around which boots from bc26. Most likely a EU variant. Best, lynxis > It seems that the difference is not that it's 4AC because even the > one > in OpenWrt ATM is a 4AC (defined as 4A) but what I found out is that > 4AC seem to have 2 different versions/flavors: > * 4AC CN -> It's using CPU@380MHz and the bootloader entry point > is bc16 and limits the WiFi to 20dBm for 2.4GHz and 20dBm for 5GHz > (Currently in OpenWRT) > * 4AC EU(or International) -> It's using CPU@375MHz and the > bootloader entry point is bc26 and limits the WiFi to 16dBm for > 2.4GHz and 18dBm for 5GHz -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgpiExWLAQxBN.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: SAD DNS cache poisoning attack
Hi, I'm wondering is dnsmasq also vulnerable as forwarder? Or only as recursive resolver? Did someone tested it? Is there a public poc? Best, lynxis -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgpud5IIPn7jp.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] generic: platform/mikrotik: implement multi caldata
On Fri, 25 Sep 2020 21:09:26 +0200 Thibaut wrote: > Ping? LGTM. What's in the "$wdata/data_0" file? Is it the BDF? Best, lynxis -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgpbyv_G_1yGj.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] omap: update uboot to v2020.04
On Mon, 21 Sep 2020 18:53:13 +0200 Alexander 'lynxis' Couzens wrote: > > do you mind to take a quick look? In the end this is just a tiny > > package bump! :) > > let me have a tiny look on other devices ;) the pandaboards fails, but the bbb boots. same as before. the panda is only booting the spl. i'll have a look tomorrow on the panda with jtag but it's not a blocker for your patch. it didn't worked before. i'll merge your patch within the next week. best, lynxis -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgpsBuHfrHo7V.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] omap: update uboot to v2020.04
> do you mind to take a quick look? In the end this is just a tiny > package bump! :) let me have a tiny look on other devices ;) pgpOzAIMUIUuc.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq: fritz7312: set maximum speed to 100 mbit on 5.4
> Hi, > > I don't have any clue at all about the problem itself. > > I just found the inconsistency and want to align 4.19 and 5.4, as > currently it is effectively a regression. > > If you want to address this differently, go for it, but don't ask me > anything about it ;-) i tested it before commiting the patch. it did a difference. i might have time next weekend to look over it and do additional tests. Please push the commit. Best, lynxis pgphmRAguVll_.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.infradead.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCHv3] ubox: run init script through shellcheck
Hi Rosen, do you plan to do a v4? Otherwise I would merge it. Best, lynxis -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgp0cNu8MC65G.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] tools: squashfskit4: fix build with GCC10
Hi Paul, Hi Robert, > Sorry, I did not know about that situation but after a look it seems > that squashfs-tools is more up to date that the fork. > There has been a 4.4 release and couple of patches each month to it. you're right! I would like to discontinue squashfskit. It had it's reason, but there are now 2 options: a) the upstream is more active and even made it reproducible b) there is a full rewrite squashfs-ng For now, I'll test the patch und merge it later. Maybe I'll also have the time evaluate the upstream and squashfs-ng. Best Regards, lynxis -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgpt9bcB5Enea.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] hostapd fails to link at current master
Hi Arne, > I'm getting the following liker errors trying to build hostapd-full or > wpad-full fpr x86_64 at the current master, and tag 19.07.1: > > The last error also appears at tag 18.06.7. thanks for your bug report. I've looked into it. It seems a Makefile dependency problem. I've done a quick dirty hack to fix it. It builds now. You can find in my staging tree under the branch hostapd. https://git.openwrt.org/?p=openwrt/staging/lynxis.git;a=shortlog;h=refs/heads/hostapd But it needs further work to check what's the best way to fix it. Best, lynxis -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgpqHrcCwYUCa.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ppp: activate PIE ASLR by default
On Thu, 20 Feb 2020 10:56:26 +0100 Petr Štetiar wrote: > This activates PIE ASLR support by default when the regular option is > selected. > > Size increase on imx6: > > 112681 ppp_2.4.8-2_arm_cortex-a9_neon.ipk > 121879 ppp_2.4.8-2_arm_cortex-a9_neon.ipk > = 9198 diff Acked-by: Alexander Couzens -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgp5Baj6dOUx6.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] jffs2 runs into read-only on low memory systems (5 eblocks)
Hi David, I'm currently working with low flash system (4MB flash / jffs2: 320 kb, 5 erase blocks). Some of the systems seems to run into read-only mode, while most work fine. I've around ~50 devices which is less than 5 %. My devices runs 4.14 and ar71xx devices. I would guess the garbage collector triggers to late, when the last free block has been allocated and moves itself into this situation. Are there any tools to debug this? Are there any tests tools available? I've dumps of the broken flash. Any thoughts how to debug it further? Best, lynxis -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgpRpfXRSB6lD.pgp Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
