[PATCH] build,json: store arch_packages in profiles.json

2020-06-30 Thread Paul Spooren
The `arch_packages` contains the supported package architecture. Previously it was necessary to parse the `Packages` index for the line `Architecture:`, requiring both an additional parser and file download. Signed-off-by: Paul Spooren --- scripts/json_overview_image_info.py | 7 +-- 1

[PATCH buildbot] phase1: add JSON merge step

2020-06-30 Thread Paul Spooren
The refactored JSON info files require a final merge step which sums up all created JSON info files of a target into a single `profiles.json` files. This patch adds the extra step to run `make json_overview_image_info` just before calculating the checksums so the `profiles.json` files is signed

Re: [RFC PATCH v2] mvebu: compile the kernel in Thumb-2 mode for ARMv7 targets

2020-06-30 Thread Rui Salvaterra
Hi, Hauke, On Tue, 30 Jun 2020 at 21:32, Hauke Mehrtens wrote: > > Did you run a benchmark to test how much faster it is? I haven't done any performance testing, but I expect it to be a wash (improvements/regressions within around 2-3 % across the board). The big win here is in the

Re: [RFC PATCH v2] mvebu: compile the kernel in Thumb-2 mode for ARMv7 targets

2020-06-30 Thread Hauke Mehrtens
On 6/18/20 3:16 PM, Rui Salvaterra wrote: > (Sending as RFC due to the note below.) > > The Thumb-2 instruction set generates denser code, allowing for more efficient > use of the cache and consequently higher execution performance. Did you run a benchmark to test how much faster it is? >

Re: [OpenWrt-Devel][PATCH v2 2/2] octeontx: enable Cavium CPT and ZIP drivers

2020-06-30 Thread Hauke Mehrtens
On 6/24/20 11:06 PM, Tim Harvey wrote: > On Thu, Jun 11, 2020 at 5:22 AM Hauke Mehrtens wrote: >> >> On 6/3/20 10:16 PM, Tim Harvey wrote: >>> On Tue, Jun 2, 2020 at 3:21 PM Hauke Mehrtens wrote: On 6/2/20 7:05 PM, Tim Harvey wrote: > The CPT module requires firmware which we add

Re: [PATCH] dropbear: init: replace backticks with $()

2020-06-30 Thread Rui Salvaterra
Hi, Adrian, On Tue, 30 Jun 2020 at 18:05, wrote: > > Merged your two patches, please add a commit description next time. > Will do, thanks a lot. Cheers, Rui ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

RE: [PATCH] dropbear: init: replace backticks with $()

2020-06-30 Thread mail
> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Rui Salvaterra > Sent: Dienstag, 30. Juni 2020 18:22 > To: openwrt-devel@lists.openwrt.org > Cc: Rui Salvaterra > Subject: [PATCH] dropbear: init: replace backticks with $() Merged

[PATCH] zram-swap: init: replace backticks with $()

2020-06-30 Thread Rui Salvaterra
Signed-off-by: Rui Salvaterra --- package/system/zram-swap/files/zram.init | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/package/system/zram-swap/files/zram.init b/package/system/zram-swap/files/zram.init index d33e779850..a6126e578f 100755 ---

[PATCH] dropbear: init: replace backticks with $()

2020-06-30 Thread Rui Salvaterra
Signed-off-by: Rui Salvaterra --- package/network/services/dropbear/files/dropbear.init | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/package/network/services/dropbear/files/dropbear.init b/package/network/services/dropbear/files/dropbear.init index

PATCH libubox: arg checking and examples

2020-06-30 Thread Karl Palsson
Minor tweaks to hopefully help people avoid some sharp corners. Patches 2 and 3 are optional, and have no functional change, but IMO make the code easier to follow for subsequent developers. ___ openwrt-devel mailing list

[PATCH libubox 4/4] examples/lua: attempt to highlight some traps

2020-06-30 Thread Karl Palsson
Ran into some issues with my fd event being garbage collected. As I never wanted to call :delete, I had seen no reason to keep the returned object, as my callback and upvalues were still valid. Signed-off-by: Karl Palsson --- examples/uloop-example.lua | 8 +--- 1 file changed, 5

[PATCH libubox 1/4] lua/uloop: fd_add() better args checking

2020-06-30 Thread Karl Palsson
Actually check for flags being valid, instead of simply ignoring the call if flags was zero. Use standard lua checks for the function argument, so you can get a normal "argument #2 was invalid, expected function, got xxx" instead of the vague, "invalid arg list" Signed-off-by: Karl Palsson ---

[PATCH libubox 2/4] lua/uloop: make get_sock_fd capable of absolute addresses

2020-06-30 Thread Karl Palsson
The original code required the use of relative addresses into the lua stack. It should accept either. Signed-off-by: Karl Palsson --- lua/uloop.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lua/uloop.c b/lua/uloop.c index fcbe274..394970d 100644 --- a/lua/uloop.c +++

[PATCH libubox 3/4] lua/uloop: fd_add: use absolute indices for arguments

2020-06-30 Thread Karl Palsson
Instead of having to adjust the index repeatedly as the stack is manipulated, use absolute addressing for the function arguments, so they stay the same throughout the call. Zero functional change, just subjectively easier to follow variables. Signed-off-by: Karl Palsson --- lua/uloop.c | 11