On 13.03.2021 17:54, Bjørn Mork wrote:
From: John Crispin
This package implements the microcontroller protocol used to
talk Broadcom PSE controllers on a number of realtek switches.
It is required to enable PoE ouput on supported hardware.
The implemented ABI allows individial control and moni
Refresh patches.
Tested on a dual-core MT7621 device (Ubiquiti ER-X) and a single-core
MT7621 device (Netgear R6220).
This change will make future kernel upgrades easier (avoids conflicts
with upstream).
Link:
https://lore.kernel.org/lkml/20210407200738.149207-1-ilya.lipnits...@gmail.com/
Signe
The pkgconfig file currently post to host paths.
Signed-off-by: Rosen Penev
---
package/libs/libsemanage/Makefile | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/package/libs/libsemanage/Makefile
b/package/libs/libsemanage/Makefile
index ff1519f14e..2fde14c06c 100644
---
On Tue, Apr 13, 2021 at 3:53 PM Hauke Mehrtens wrote:
>
> On 4/13/21 6:03 AM, Rosen Penev wrote:
> > For some reason, fortified mempcpy does not work with GCC 10.3. It
> > worked with GCC 10.2.
> >
> > Some output with tvheadend:
> >
> > error: 'mempcpy' undeclared here (not in a function);
> > di
On 4/13/21 6:03 AM, Rosen Penev wrote:
For some reason, fortified mempcpy does not work with GCC 10.3. It
worked with GCC 10.2.
Some output with tvheadend:
error: 'mempcpy' undeclared here (not in a function);
did you mean 'memccpy'?
144 | _FORTIFY_FN(mempcpy) void *mempcpy(void *__d,
const voi
On 4/13/21 10:02 AM, Linus Walleij wrote:
On Mon, Apr 12, 2021 at 8:32 PM Christian Lamparter wrote:
Hmm, when building this with the BUILDBOT config (CONFIG_BUILDBOT)
and throw in the CONFIG_ALL_* for userspace + kernel modules for
good measure. It fails with the default world build (without
Hi Rafał,
thanks for picking this up soo quickly.
Am Dienstag, 13. April 2021, 14:02:10 CEST schrieb Rafał Miłecki:
> > The original code comes from Florian from the 2007 commit 7b564bfdcbef
> > ("Fix potential unligned access with MyLoader based devices, thanks
> > Juhos")
> >
> > https://git.o
Philip,
I already read about deprecating ipsec tool someyears ago and started to use
swanctl. I hacked some scripts together on one of my nodes to not use ipsec-
cli. (Sadly I stopped at some point, without making it useable outside of my
"lab" to pubish / share.)
By the time I became a fan of s
Hi all,
Word is that strongswan-6.0 will remove the ipsec interface. No idea how many
5.9.x releases will come out before that happens. Doing some prediction based
on the past roadmap:
The cadence in the past has been every 3 months, and typically x.y.3 or x.y.4
is the maximum release until
On Tue, Apr 13, 2021 at 03:09:24PM +0200, Felix Fietkau wrote:
>
> On 2021-04-13 14:22, Sebastian Kemper wrote:
> > This fixes a regression introduced with commit
> > 5ed1e5140a80558ab47fd70410ae3242bed5becf ("build: build kernel image
> > before building modules/packages").
> >
> > Before this com
On 2021-04-13 14:22, Sebastian Kemper wrote:
> This fixes a regression introduced with commit
> 5ed1e5140a80558ab47fd70410ae3242bed5becf ("build: build kernel image
> before building modules/packages").
>
> Before this commit the make target would always include "modules",
> resulting in a MODPO
This fixes a regression introduced with commit
5ed1e5140a80558ab47fd70410ae3242bed5becf ("build: build kernel image
before building modules/packages").
Before this commit the make target would always include "modules",
resulting in a MODPOST and a complete Module.symvers file. Since this
commit a
On 2021-04-13 08:39, Rafał Miłecki wrote:
On 13.04.2021 00:46, Sven Roederer wrote:
since some days my master builds failing for ath79-generic. I was able
to
narrow it to running "mkmylofw for compex_wpj344-16m".
The tool runs till the drive is full, currently my "compex_wpj344-16m-
squashfs-cp
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 ---
> Op 13 apr. 2021, om 06:03 heef
From: Rafał Miłecki
CRYPTO_DEV_CCP depends on X86 or ARM64
CRYPTO_DEV_CCP_DD depends on CPU_SUP_AMD or ARM64
Compiling this driver makes sense for x86 mainly. If one day support for
ARM64 board with AMD Secure Processor gets added this package may be
updated.
Trying to build this package on bcm
On 2021-04-13 12:02, Felix Fietkau wrote:
On 2021-04-13 11:46, Rafał Miłecki wrote:
From: Rafał Miłecki
CONFIG_CRYPTO_DEV_SP_CCP depends on DMA_ENGINE which depends on
DMADEVICES=y which bcm4908 doesn't need and doesn't use at this point.
Trying to build this package on bcm4908 was causing:
E
On 2021-04-13 11:46, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> CONFIG_CRYPTO_DEV_SP_CCP depends on DMA_ENGINE which depends on
> DMADEVICES=y which bcm4908 doesn't need and doesn't use at this point.
>
> Trying to build this package on bcm4908 was causing:
> ERROR: module
> 'build_dir/tar
From: Rafał Miłecki
CONFIG_CRYPTO_DEV_SP_CCP depends on DMA_ENGINE which depends on
DMADEVICES=y which bcm4908 doesn't need and doesn't use at this point.
Trying to build this package on bcm4908 was causing:
ERROR: module
'build_dir/target-aarch64_cortex-a53_musl/linux-bcm4908_generic/linux-5.4
On 13/04/2021 11:30, Florian Eckert wrote:
With the old ubus dsl API, the numbers for the individual line_states and
power_states were also returned. These were not ported to the new DSL
C-API. This commit adds the missing information.
For this the internal values are mapped to numbers.
* addit
With the old ubus dsl API, the numbers for the individual line_states and
power_states were also returned. These were not ported to the new DSL
C-API. This commit adds the missing information.
For this the internal values are mapped to numbers.
* additional JSON output for state_num:
"state_num":
Adrian Schmutzler [2021-04-10 18:55:10]:
Hi,
> > Currently it's not possible to flash factory images on devices shipped with
> > vendor firmware versions 1.1.0 Build 20201120 rel. 50406 (published
> > 2020-12-22):
>
> Will this prevent flashing back vendor firmware via TFTP or is a different
>
On Mon, Apr 12, 2021 at 8:32 PM Christian Lamparter wrote:
> Hmm, when building this with the BUILDBOT config (CONFIG_BUILDBOT)
> and throw in the CONFIG_ALL_* for userspace + kernel modules for
> good measure. It fails with the default world build (without the
> V=s option) because the following
22 matches
Mail list logo
