Re: [PATCH] iperf3: move over to packages.git

2021-01-17 Thread Florian Eckert
That package is not required for building OpenWrt so the maintenance should happen over at packages.git. Sounds about right. I think most people prefer to use iperf anyway... But then I would also move the iperf package to the package feed. CC: Felix Fietkau Signed-off-by: Paul

Re: [PATCH 2/2] bcm4908: build flashable & bootable firmware images

2021-01-17 Thread Rafał Miłecki
On 15.01.2021 16:18, Adrian Schmutzler wrote: -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Rafal Milecki Sent: Freitag, 15. Januar 2021 10:44 To: openwrt-devel@lists.openwrt.org Cc: Rafał Miłecki Subject: [PATCH 2/2] bcm4908: build

Re: [PATCH] iperf3: move over to packages.git

2021-01-17 Thread Rosen Penev
On Fri, Jan 15, 2021 at 12:08 PM Paul Spooren wrote: > > That package is not required for building OpenWrt so the maintenance > should happen over at packages.git. Sounds about right. I think most people prefer to use iperf anyway... > > CC: Felix Fietkau > > Signed-off-by: Paul Spooren

[PATCH] autoconf: update to 2.70

2021-01-17 Thread Rosen Penev
Refreshed patches. Removed emacs patch as upstream removed emacs completely. Removed musl host patch. Upstream seems to have fixed it differently. Signed-off-by: Rosen Penev --- tools/autoconf/Makefile | 4 +- tools/autoconf/patches/000-relocatable.patch | 107

[PATCHv2] tools/zstd: update to 1.4.8

2021-01-17 Thread Rosen Penev
Switch to the normal tarball instead of the codeload generated one. The latter has the potential to change hashes based on changes in the repo. Signed-off-by: Rosen Penev --- v2: forgot to remove upstreamed patch tools/zstd/Makefile | 7 +--

[PATCH] tools/zstd: update to 1.4.8

2021-01-17 Thread Rosen Penev
Switch to the normal tarball instead of the codeload generated one. The latter has the potential to change hashes based on changes in the repo. Signed-off-by: Rosen Penev --- tools/zstd/Makefile | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/tools/zstd/Makefile

[no subject]

2021-01-17 Thread Stephen Walker via openwrt-devel
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 --- Branch: refs/heads/master

Re:

2021-01-17 Thread Daniel Golle
On Thu, Jan 14, 2021 at 02:29:31PM +0100, Etan Kissling via openwrt-devel wrote: > 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 >

Re: [PATCH v2 3/4] image-commands: support Chromium OS image-type creation

2021-01-17 Thread Paul Spooren
On So, Jan 17, 2021 at 09:20, Brian Norris wrote: Hi Paul, On Sun, Jan 17, 2021 at 2:43 AM Paul Spooren wrote: On Sat Jan 16, 2021 at 5:07 PM HST, Brian Norris wrote: > See the previous patches, which implemented the cros-vbutil > verified-boot payload-packing tool, and extended ptgen

Re: [PATCH v2 3/4] image-commands: support Chromium OS image-type creation

2021-01-17 Thread Brian Norris
Hi Paul, On Sun, Jan 17, 2021 at 2:43 AM Paul Spooren wrote: > On Sat Jan 16, 2021 at 5:07 PM HST, Brian Norris wrote: > > See the previous patches, which implemented the cros-vbutil > > verified-boot payload-packing tool, and extended ptgen for the CrOS > > kernel partition type. With these,

[RFC PATCH 1/2] Workaround recursive error

2021-01-17 Thread Hauke Mehrtens
It looks like there is a bug in our configuration system when we add the additional dependencies in PKG_DEFAULT_DEPENDS we get these recursive errors: tmp/.config-package.in:19514:error: recursive dependency detected! tmp/.config-package.in:19514: symbol

[RFC PATCH 0/2] toolchain: build all user space with sanitizer on glibc

2021-01-17 Thread Hauke Mehrtens
This patch allows to build most the OpenWrt user space with address and undefined behavior sanitizer activated by default. This only works with glibc and gcc 10 and I only tested this on x86 64 so far. It is not intended to activate this by default ever, but this is helpful to detect (security)

[RFC PATCH 2/2] toolchain: Allow building with ASAN and UBSAN

2021-01-17 Thread Hauke Mehrtens
This allows to build all user space with Address sanitizer and undefined behavior sanitizer. It will automatically add this to the TRAGET_CFLAGS and TARGET_LDFLAGS of every user space component. This is only working with gcc 10.X, because the system init process will mount /proc after it was

[no subject]

2021-01-17 Thread Gagan Sidhu via openwrt-devel
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, using your dts

Re: [PATCH v2 0/4] Add support for Chromium OS and Google WiFi

2021-01-17 Thread Paul Spooren
On Sat Jan 16, 2021 at 5:07 PM HST, Brian Norris wrote: > Hi, > > This series adds support for both Chromium OS (or particularly, its > kernel-payload signing and disk layout) and for a device using it (the > first generation Google WiFi). > > Google WiFi (code-named "Gale") is an IPQ4019-based

Re: [PATCH v2 3/4] image-commands: support Chromium OS image-type creation

2021-01-17 Thread Paul Spooren
On Sat Jan 16, 2021 at 5:07 PM HST, Brian Norris wrote: > See the previous patches, which implemented the cros-vbutil > verified-boot payload-packing tool, and extended ptgen for the CrOS > kernel partition type. With these, it's now possible to package kernel + > rootfs to make disk images that

RE: [PATCH] rockchip: use stable MAC-address for NanoPi R2S

2021-01-17 Thread Karl Palsson
"Adrian Schmutzler" wrote: > > + local mac_base=$(macaddr_canonicalize "$(echo "${sd_hash}" | dd > > bs=1 count=12 2>/dev/null)") > > bs=12 count=1 ? Why? unless you're passing other flags to try and magically avoid the block layer, you're only operating on a 1k block read out anyway. This