Hello Philip
Yeah, it's intentional. It was meant to be a sentinel for bitrot.
I was already aware that this warning was intentional.
I have expressed that incorrectly sorry.
You don't want to have an empty expansion of CPU_CLFAGS_* as these are
usually important platform-specific values
The target config require some refresh due to the just introduced
filtering of the "run-time" options, MIPS eBPF JIT backporting, and so
on.
The configuration is easily updated using make kernel_oldconfig. So
let's update it now in preparation for v5.10 support to reduce the new
kernel
Copy and refresh patches and config from 5.4 to 5.10. Most patches
require no more then automatic refresh. The only exception is the
Ethernet driver patch, which requires some more work:
* drop eth_change_mtu() usage since it was removed from the kernel,
it anyway useless for drivers that
Hello,
I finally managed to update ath25 to the 5.10 kernel. Sorry for that it
took so long time, I was a quite busy this fall. The update itself is
relatively simple: mostly copy'n'refresh plus a few Ethernet fixes.
Run-time tested with:
* Abicom FreedomCPE (AR5312 based)
* D-Link DWL-2100AP
Support for mvswich driver (Marvell 88E6060 switches) build has been
missed during the initial v5.10 kernel introduction. But it is required
for AR21xx boards, e.g. Fonera 2.0. Return the missed driver building
instructions to fix boards support with the new kernel.
Compile tested only with the
Each of
- CRYPTO_AEAD2
- CRYPTO_AEAD
- CRYPTO_GF128MUL
- CRYPTO_GHASH
- CRYPTO_HASH2
- CRYPTO_HASH
- CRYPTO_MANAGER2
- CRYPTO_MANAGER
- CRYPTO_NULL2
either directly required for mac80211 crypto support, or directly
selected by such options. Support for the mac80211 crypto was enabled in
the
Both CLANG_VERSION and LLD_VERISON are autogenerated runtime
configuration options, so add them to the kernel configuration filter
and remove from generic and per-target configs to keep configs clean.
Signed-off-by: Sergey Ryazanov
---
target/linux/armvirt/config-5.10 | 1 -
Hello,
this series intended to cleaup per-target kernel configurations. It
should reduce amount of odd options in the per-target configurations by
removing "run-time" options and moving mac80211 crypto related options
to the generic configuration.
All this odd options were discovered during the
Yeah, it's intentional. It was meant to be a sentinel for bitrot.
If you look at the line following the changes:
DEFAULT_CFLAGS=$(strip $(CPU_CFLAGS) $(CPU_CFLAGS_$(CPU_TYPE))
$(CPU_CFLAGS_$(CPU_SUBTYPE)))
You don't want to have an empty expansion of CPU_CLFAGS_* as these are usually
Hello Arvid,
On Wed, Dec 15, 2021 at 2:13 PM Arvid Picciani wrote:
> ZBT-WE1206 has an external watchdog that with stock openwrt resets the board.
What board do you mean? I am unable to locate ZBT-WE1206 neither in
the repository, nor in google.
> should this get disabled in bringup or is this
Hi
I have gathered my thoughts in my own version of uqmi.
I think I have dual-stack working.
It's available at https://github.com/mrhaav/openwrt-packages. Feel
free to take a lock and try. :)
/Henrik
Den mån 6 dec. 2021 kl 08:29 skrev Bjørn Mork :
>
> Sergey Ryazanov writes:
>
> > Can you
Hi Arnout,
On 2021-12-16 18:00, Arnout Vandecappelle wrote:
Since I want to use these features outside of OpenWrt, I'd like to upstream
the patches 300-noscan.patch and 360-ctrl_iface_reload.patch to hostap.
First of all, I'd like confirmation from you that it's OK to redistribute
those
Hi Felix,
Since I want to use these features outside of OpenWrt, I'd like to upstream
the patches 300-noscan.patch and 360-ctrl_iface_reload.patch to hostap.
First of all, I'd like confirmation from you that it's OK to redistribute
those patches under hostap's BSD-3-Clause license rather
From: Rafał Miłecki
It's very useful flag for handling various formats in sysupgrade. This
commits comes from 1.34.0 release.
Signed-off-by: Rafał Miłecki
---
.../001-dd-support-iflag-count_bytes.patch| 140 ++
1 file changed, 140 insertions(+)
create mode 100644
Hello,
If I execute the following command in the openwrt project:
./scripts/dump-target-info.pl targets
I get the this output! I don't know if this is a mistake or if it is
intentional.
The warning was added by this commit
15 matches
Mail list logo
