and x86_64.
Stijn Tintel (10):
kernel/modules: remove superfluous backslash
kernel/modules: add kmod-crypto-aead
kernel/modules: kmod-crypto-manager: depend on kmod-crypto-aead
kernel/modules: remove CRYPTOMGR_MODULES
kernel/modules: add kmod-crypto-seqiv
kernel/modules: add kmod-crypto
Signed-off-by: Stijn Tintel
---
package/kernel/linux/modules/crypto.mk | 13 +
1 file changed, 13 insertions(+)
diff --git a/package/kernel/linux/modules/crypto.mk
b/package/kernel/linux/modules/crypto.mk
index de3d851..ad1fe4e 100644
--- a/package/kernel/linux/modules/crypto.mk
Signed-off-by: Stijn Tintel
---
package/kernel/linux/modules/crypto.mk | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/package/kernel/linux/modules/crypto.mk
b/package/kernel/linux/modules/crypto.mk
index d17f1e1..04903c3 100644
--- a/package/kernel/linux/modules
Signed-off-by: Stijn Tintel
---
package/kernel/linux/modules/crypto.mk | 11 +++
1 file changed, 11 insertions(+)
diff --git a/package/kernel/linux/modules/crypto.mk
b/package/kernel/linux/modules/crypto.mk
index 3193fb0..1fd10d9 100644
--- a/package/kernel/linux/modules/crypto.mk
Signed-off-by: Stijn Tintel
---
package/kernel/linux/modules/crypto.mk | 11 +++
1 file changed, 11 insertions(+)
diff --git a/package/kernel/linux/modules/crypto.mk
b/package/kernel/linux/modules/crypto.mk
index 04903c3..3193fb0 100644
--- a/package/kernel/linux/modules/crypto.mk
Signed-off-by: Stijn Tintel
---
package/kernel/linux/modules/crypto.mk | 11 +++
1 file changed, 11 insertions(+)
diff --git a/package/kernel/linux/modules/crypto.mk
b/package/kernel/linux/modules/crypto.mk
index 1fd10d9..5d49160 100644
--- a/package/kernel/linux/modules/crypto.mk
Signed-off-by: Stijn Tintel
---
package/kernel/linux/modules/crypto.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/kernel/linux/modules/crypto.mk
b/package/kernel/linux/modules/crypto.mk
index d9d673c..de3d851 100644
--- a/package/kernel/linux/modules/crypto.mk
Signed-off-by: Stijn Tintel
---
package/kernel/linux/modules/crypto.mk | 15 ---
1 file changed, 4 insertions(+), 11 deletions(-)
diff --git a/package/kernel/linux/modules/crypto.mk
b/package/kernel/linux/modules/crypto.mk
index 5d49160..eec7934 100644
--- a/package/kernel/linux
Signed-off-by: Stijn Tintel
---
package/kernel/linux/modules/crypto.mk | 12
1 file changed, 12 insertions(+)
diff --git a/package/kernel/linux/modules/crypto.mk
b/package/kernel/linux/modules/crypto.mk
index eec7934..9d69cce 100644
--- a/package/kernel/linux/modules/crypto.mk
Signed-off-by: Stijn Tintel
---
package/kernel/linux/modules/crypto.mk | 12
1 file changed, 12 insertions(+)
diff --git a/package/kernel/linux/modules/crypto.mk
b/package/kernel/linux/modules/crypto.mk
index 9d69cce..73f36be 100644
--- a/package/kernel/linux/modules/crypto.mk
On 23-12-14 22:59, Stijn Tintel wrote:
> On 23-12-14 20:11, Andre Valentin wrote:
>> Hi!
>>
>> I just recompiled the module and loaded it on the router. But it seems that
>> this does not fix the error. 5 minutes later I got several alerts (ping
>> checks).
>
This patch series adds support for fast BSS transition (802.11r) to hostapd.
Only tested association with ath9k client on ath9k AP with netifd. Changes to
hostapd.sh are untested.
https://dev.openwrt.org/ticket/13187
Stijn Tintel (3):
hostapd: append nasid to config for all WPA types
hostapd
To enable 802.11r, wpa_key_mgmt should contain FT-EAP or FT-PSK. Allow
multiple key management algorithms to make this possible.
Signed-off-by: Stijn Tintel
---
package/network/services/hostapd/files/hostapd.sh | 6 --
package/network/services/hostapd/files/netifd.sh | 6 --
2 files
The 802.11r implementation in hostapd uses nas_identifier as PMK-R0 Key
Holder identifier. As 802.11r can also be used with WPA Personal, nasid
should be appended to the hostapd config for all WPA types.
Signed-off-by: Stijn Tintel
---
package/network/services/hostapd/files/hostapd.sh | 8
Signed-off-by: Stijn Tintel
---
package/network/services/hostapd/files/hostapd.sh | 29 ++
package/network/services/hostapd/files/netifd.sh | 37 ++-
2 files changed, 65 insertions(+), 1 deletion(-)
diff --git a/package/network/services/hostapd/files
On 11-02-15 15:09, Ulrich Weber wrote:
> Signed-off-by: Ulrich Weber
> ---
> package/kernel/linux/modules/crypto.mk | 13 ++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/package/kernel/linux/modules/crypto.mk
> b/package/kernel/linux/modules/crypto.mk
> index 4d
On 11-02-15 15:09, Ulrich Weber wrote:
> Signed-off-by: Ulrich Weber
> ---
> package/kernel/linux/modules/crypto.mk | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/package/kernel/linux/modules/crypto.mk
> b/package/kernel/linux/modules/crypto.mk
> index 7fea3bf..3d76ef3 10
both in OpenWrt
core and in the package repository, it might make sense to add this
optional dependency to all non-kernel packages, instead of polluting
lots of package dependency lines with it.
Signed-off-by: Stijn Tintel
---
include/package-defaults.mk | 2 +-
1 file changed, 1 insertion(+), 1
On 23-03-15 12:31, Alexandru Ardelean wrote:
> Helpful to disable when debugging lldpd crashes (when working on it).
> When priviledge separation is on, some crashes are stack-traced to
> some priviledge separation code.
Nitpicking, but the correct spelling is "privilege".
> Signed-off-by: Alexandr
On 04-04-15 14:45, shengkai wrote:
> hi Maintainer and All,
>
> We are an open source hardware team come from china, and we developed
> an open source route board using MT7620A soc. In order to support this
> new board officially, we plan to sumbit the special code for our
> prodcut to openwrt bran
r compiler/linker flags.
Tested-by: Stijn Tintel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 29/10/2019 06:37, John Crispin wrote:
Hi,
should we use v5.4 as our next kernel ?
As 5.4 is planned to be the next longterm kernel, with projected EOL
12/2021 [0], this seems like a good idea. ACK from me.
Stijn
[0] https://www.kernel.org/category/releases.html
_
Hi,
As the server that is hosting the OpenWrt.org wiki is running out of
disk space, we will take it down to resize it.
Stijn
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 6/11/2019 12:51, Stijn Tintel wrote:
Hi,
As the server that is hosting the OpenWrt.org wiki is running out of
disk space, we will take it down to resize it.
And it's back.
Stijn
___
openwrt-devel mailing list
openwrt-devel@lists.openwr
On 26/11/2019 00:34, Hauke Mehrtens wrote:
> It looks like there is a throughput problem with ath10k-ct on QCA9984,
> https://bugs.openwrt.org/index.php?do=details&task_id=2593
> there are multiple reports in the Forum.
>
> For me QCA9880 on a BTHH5A with ath10k-ct on 5GHz works in openwrt 19.07
>
On 30/11/2019 22:44, Tom Psyborg wrote:
> On 26/11/2019, Stijn Tintel wrote:
>> On 26/11/2019 00:34, Hauke Mehrtens wrote:
>>> It looks like there is a throughput problem with ath10k-ct on QCA9984,
>>> https://bugs.openwrt.org/index.php?do=details&task_id=2593
&g
On 2/12/2019 16:12, Petr Štetiar wrote:
> I've added this patch into my staging tree[4] with some warning and
> will merge it unless someone NAK it in the next 14 days.
NAK!
Pushing commits that are known to result in systems no longer booting is
simply not acceptable, imo. Not everybody reads g
/tmp/openwrt-ath79-generic-ubnt_litebeam-ac-gen2-squashfs-sysupgrade.bin
Signed-off-by: Stijn Tintel
---
Notes:
Instructions can be found to install OpenWrt via AirOS at [0]. Unfortunately
they require an AirOS image, which can only be downloaded by accepting
the EULA. As I do not
On 3/12/2019 01:39, m...@adrianschmutzler.de wrote:
> Hi Stijn,
>
> does the device have a MAC address label or imprint on the box?
It does.
>
> [...]
>
>> +define Device/ubnt_litebeam-ac-gen2
>> + $(Device/ubnt-wa)
>> + DEVICE_TITLE := Ubiquiti LiteBeam AC Gen2
> DEVICE_TITLE has been replaced b
On 3/12/2019 02:05, m...@adrianschmutzler.de wrote:
>> -Original Message-
>> From: Stijn Tintel [mailto:st...@linux-ipv6.be]
>> Sent: Dienstag, 3. Dezember 2019 00:58
>> To: m...@adrianschmutzler.de; openwrt-devel@lists.openwrt.org
>> Cc: pozega.tomis...@gmai
On 3/12/2019 13:54, Adrian Schmutzler wrote:
+ IMAGE/factory.bin := $$(IMAGE/sysupgrade.bin) | mkubntimage-split
>>> Can we reuse the IMAGE/factory.bin from Device/ubnt here? The only thing
>> missing compared to your line is append-metadata ...
>>
>> I used the same as with other ubnt-wa dev
On 3/12/2019 14:31, Petr Štetiar wrote:
> Adrian Schmutzler [2019-12-03 13:17:04]:
>
>> Other ubnt-wa do this, too, they just do not define it in parent node:
> Ok, I've checked only the parent node.
>
>> So, the question is whether it would make sense to remove the line for all
>> the other ubnt
On 4/12/2019 15:37, Tom Psyborg wrote:
> Current changes from Stijn's branch look fine, I've applied them to
> the master clone from Dec 2nd, built and flashed; mac addresses are
> correct, ethernet is working as well as both wifi interfaces.
>
Can I get some [Ack|Review|Test]ed-by from you guys?
On 2/06/2021 01:10, Alexey Dobrovolskiy wrote:
> Hi,
>
>>> service_triggers() {
>>> - local script name use_dhcp
>>> + local enable_server interface name script use_dhcp
>>
>> I'd rather leave the existing variables in their original order.
>>
>>
> OpenWrt Submission Guidelines [0] says tha
The xfrm_interface module will not be built if IPv6 is not enabled in
the kernel. Add this dependency in the kmod package to avoid people
wondering why it doesn't build when they disabled IPv6.
Signed-off-by: Stijn Tintel
---
package/kernel/linux/modules/netsupport.mk | 2 +-
1 file chang
kernel configs of 64bit targets, unless the
target config has disabled CONFIG_RCU_EXPERT.
Signed-off-by: Stijn Tintel
---
target/linux/armvirt/64/config-5.10 | 1 +
target/linux/armvirt/64/config-5.4 | 1 +
target/linux/bcm27xx/bcm2710/config-5.4 | 1 +
target/linux/bcm27xx/bcm2711
On 30/07/2021 20:56, Stijn Tintel wrote:
The generic config has CONFIG_RCU_EXPERT=y, which exposes
CONFIG_RCU_FANOUT. This is set to 32 in the generic config, but the
default for 64bit kernels is 64. This causes a warning during boot:
[0.00] rcu: CONFIG_RCU_FANOUT set to non-default
ff by
default, to maintain the current behaviour.
Signed-off-by: Stijn Tintel
---
config/Config-images.in | 6 ++
package/base-files/Makefile | 5 +
2 files changed, 11 insertions(+)
diff --git a/config/Config-images.in b/config/Config-images.in
index 4a7f08824b..dc68fade3c 100644
--- a/c
On 7/08/2021 02:56, Alberto Bursi wrote:
>
>
> On 06/08/21 21:27, Stijn Tintel wrote:
>> In OpenWrt, /var is symlinked to /tmp by default. This is done to reduce
>> the amount of writes to the flash chip, which often don't have the
>> greatest durability. As a
On 7/08/2021 10:05, Alberto Bursi wrote:
On 07/08/21 02:46, Stijn Tintel wrote:
On 7/08/2021 02:56, Alberto Bursi wrote:
On 06/08/21 21:27, Stijn Tintel wrote:
In OpenWrt, /var is symlinked to /tmp by default. This is done to
reduce
the amount of writes to the flash chip, which often
Runtime-tested on:
* ath79
* bcm27xx/bcm2708
* bcm27xx/bcm2709
* bcm27xx/bcm2711
* mvebu/cortexa53
* octeon
* realtek
* x86/64
Signed-off-by: Stijn Tintel
---
toolchain/binutils/Config.in | 2 +-
toolchain/binutils/Config.version | 2 +-
2 files changed, 2 insertions(+), 2 deletions
added to the CFLAGS and LDFLAGS.
Signed-off-by: Stijn Tintel
---
package/utils/busybox/Makefile | 3 ---
1 file changed, 3 deletions(-)
diff --git a/package/utils/busybox/Makefile b/package/utils/busybox/Makefile
index 32f0d2c755..76a1de33b7 100644
--- a/package/utils/busybox/Makefile
+++ b/pa
ng random breakage in the packages feed, many of
which not even caused by the GCC bump, I gave up and decided to just
send out this patch series.
Stijn Tintel (6):
busybox: fix compilation with GCC 10
umbim: fix compilation with GCC 10
toolchain/binutils: switch to version 2.36.1 by default
Since we switched to GCC 10 by default, with the previous default being
GCC 8, it doesn't make much sense to keep GCC 9 around, so drop it.
Signed-off-by: Stijn Tintel
---
toolchain/gcc/Config.in | 3 ---
toolchain/gcc/Config.version | 5 -
2 files changed, 8 deletions(-)
diff --
Runtime-tested on:
* ath79
* bcm27xx/bcm2708
* bcm27xx/bcm2709
* bcm27xx/bcm2711
* mvebu/cortexa53
* octeon
* realtek
* x86/64
Signed-off-by: Stijn Tintel
---
toolchain/gcc/Config.in | 2 +-
toolchain/gcc/Config.version | 12 ++--
2 files changed, 7 insertions(+), 7 deletions
being acked.
Signed-off-by: Stijn Tintel
---
package/network/utils/umbim/patches/999-gcc10.patch | 13 +
1 file changed, 13 insertions(+)
create mode 100644 package/network/utils/umbim/patches/999-gcc10.patch
diff --git a/package/network/utils/umbim/patches/999-gcc10.patch
b/package/netw
Since we switched to binutils 2.36.1 by default, with the previous
default being binutils 2.34, it doesn't make much sense to keep binutils
2.35.1 around, so drop it.
Signed-off-by: Stijn Tintel
---
toolchain/binutils/Config.in | 4
toolchain/binutils/Config.version | 4
2
On 15/08/2021 14:53, Hauke Mehrtens wrote:
> Thank you Stijn for taking care of this toolchain upgrade and Rosen
> for preparing it.
Thanks for reviewing!
>
> On 8/15/21 12:51 PM, Stijn Tintel wrote:
>> Since 21.02 has been branched, it's a good time to switch master to a
&
unusable.
Signed-off-by: Stijn Tintel
---
package/network/services/uhttpd/Makefile | 2 +-
package/network/services/uhttpd/files/uhttpd.init | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/package/network/services/uhttpd/Makefile
b/package/network/services/uhttpd
ELFv2 ABI.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93157 for more info.
Signed-off-by: Stijn Tintel
---
toolchain/gcc/common.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/toolchain/gcc/common.mk b/toolchain/gcc/common.mk
index 76c5fc114a..2167127916 100644
--- a/toolchain/gcc
DTS, so any suggestions on how to do this welcome.
Looking forward to feedback.
Thanks,
Stijn
[1]
https://community.nxp.com/t5/CodeWarrior-for-QorIQ/What-causes-quot-cpu1-fsl-dpa-ethernet-30-dpaa-eth-c-828-dpa-rx/m-p/266154
[2] https://source.codeaurora.org/external/qoriq/qoriq-components/fmc/
St
This is the main CPU type used in NXP's PPC based QorIQ processors, and
will be used by the upcoming new qoriq target.
Signed-off-by: Stijn Tintel
---
include/target.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/target.mk b/include/target.mk
index 7526224972..86a398d652 1
As of version 3.7, Nettle added PowerPC64 assembly for several
algorithms. Unfortunately, they cause build to fail due to ABI mismatch:
gcm-hash.o: ABI version 1 is not compatible with ABI version 2 output
Disable assembler when ppc64 and musl are used for now.
Signed-off-by: Stijn Tintel
perlasm scheme. This will probably break the combination
ppc64 with glibc, but as we really only want to support musl, this
shouldn't be a problem.
Signed-off-by: Stijn Tintel
---
...m-ppc-xlate.pl-add-linux64v2-flavour.patch | 63 +++
.../openssl/patches/110-openwrt_targets.patch
--git a/target/linux/qoriq/Makefile b/target/linux/qoriq/Makefile
new file mode 100644
index 00..d9a9f4d226
--- /dev/null
+++ b/target/linux/qoriq/Makefile
@@ -0,0 +1,21 @@
+# SPDX-License-Identifier: GPL-2.0-only
+#
+# Copyright (C) 2021 Stijn Tintel
+
+include $(TOPDIR)/rules.mk
+
+ARCH:=pow
2
console=$consoledev,$baudrate fsl_dpaa_fman.fsl_fm_max_frm=1522; ext2load mmc
0:1 $fdtaddr image-m300.dtb; ext2load mmc 0:1 $loadaddr
firebox_m300-kernel.bin; bootm $loadaddr - $fdtaddr"
saveenv
reset
The default U-Boot boot entry will now boot OpenWrt from the SD card.
Signed-off-by: Stijn Tintel
On 22/08/2021 03:06, Alberto Bursi wrote:
>
>
> On 22/08/21 01:15, Stijn Tintel wrote:
>> This device is based on NXP's QorIQ T2081QDS board, with a quad-core
>> dual-threaded 1.5 GHz ppc64 CPU and 4GB ECC RAM. The board has 5
>
> A few questions about this device
On 22/08/2021 14:35, Adrian Schmutzler wrote:
> Hi,
>
>> -Original Message-
>> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
>> On Behalf Of Stijn Tintel
>> Sent: Sonntag, 22. August 2021 01:15
>> To: openwrt-devel@lists.openwrt.or
On 22/08/2021 16:07, Hauke Mehrtens wrote:
> On 8/22/21 1:15 AM, Stijn Tintel wrote:
>> Add a new target named "qoriq", that will support boards using PowerPC
>> processors from NXP's QorIQ brand.
>>
>> This doesn't actually add support for any boar
On 22/08/2021 17:35, Stijn Tintel wrote:
> On 22/08/2021 16:07, Hauke Mehrtens wrote:
>> On 8/22/21 1:15 AM, Stijn Tintel wrote:
>>> Add a new target named "qoriq", that will support boards using PowerPC
>>> processors from NXP's QorIQ brand.
>>>
On 23/08/2021 10:22, e9hack wrote:
> Hi,
>
> I didn't select 'make /var persistent' but /var is generated
> persistent. I think in the Makefile the test for
> CONFIG_TARGET_ROOTFS_PERSIST_VAR = n must be changed to y (or empty).
>
> --- a/package/base-files/Makefile
> +++ b/package/base-files/Makef
On 24/08/2021 15:41, Adrian Schmutzler wrote:
> Hi,
>
+ reg = <0x00 0x1>;
+ label = "NOR (RW) LANNER RCW Code";
>>> Labels here might need some refactoring, too.
>> Since we're not really touching anything on the NOR (yet), I prefer to
>> keep the OE
On 25/08/2021 21:01, Stijn Tintel wrote:
> On 24/08/2021 15:41, Adrian Schmutzler wrote:
>> Hi,
>>
>>>>> + reg = <0x00 0x1>;
>>>>> + label = "NOR (RW) LANNER RCW Code";
>>>> Labels h
t was enabled. It was most likely required to build at that
time, but as it now builds fine without it, just remove the fixup.
Signed-off-by: Stijn Tintel
---
package/devel/strace/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/package/devel/strace/Makefile b/package/devel/strace/Mak
ble config combinations that do exhibit this
problem, it is best to solve it by adding the missing symbol to the
subtarget kernel configs. By doing this we can remove it from the
kmod-sound-soc-bcm2835-i2s package.
Signed-off-by: Stijn Tintel
---
target/linux/bcm27xx/bcm2708/config-5.10 | 1 +
target/lin
them from the
kmod-sound-soc-bcm2835-i2s package.
Signed-off-by: Stijn Tintel
---
target/linux/bcm27xx/bcm2708/config-5.10 | 2 ++
target/linux/bcm27xx/bcm2708/config-5.4 | 2 ++
target/linux/bcm27xx/bcm2709/config-5.10 | 2 ++
target/linux/bcm27xx/bcm2709/config-5.4 | 2 ++
target/linux/bcm27
On 30/09/2021 19:58, Stijn Tintel wrote:
> When building an image for the bcm27xx target, some combinations of
> config options will fail to build due the SND_SOC_AD193X_SPI kernel
> config symbol being missing.
>
> The problem only occurs on bcm27xx as the target contains a patch
When KERNEL_PERF_EVENTS is enabled in OpenWrt, or PERF_EVENTS in the
kernel config, the RPI_AXIPERF is exposed. Add it to the subtarget
kernel configs to avoid build failures.
Signed-off-by: Stijn Tintel
---
target/linux/bcm27xx/bcm2708/config-5.10 | 1 +
target/linux/bcm27xx/bcm2708/config-5.4
On 30/09/2021 01:19, Nick wrote:
> On 9/29/21 22:28, Hauke Mehrtens wrote:
>
>> kernel 5.10:
>> We should get all targets to kernel 5.10. All targets which are not
>> on kernel 5.10 when we branch off should get removed.
> Kernel 5.15 could be also a LTS Kernel that should be released in the
> end
This introduces support for hardware flow offloading, which was added in
in nftables 0.9.9.
Signed-off-by: Stijn Tintel
---
package/network/utils/nftables/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/network/utils/nftables/Makefile
b/package
This introduces support for hardware flow offloading, which was added in
in nftables 0.9.9.
Signed-off-by: Stijn Tintel
---
package/network/utils/nftables/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/network/utils/nftables/Makefile
b/package
default value in 5.10 instead of adding a build option for it.
Fixes build failures with KERNEL_UBSAN enabled.
Signed-off-by: Stijn Tintel
---
config/Config-kernel.in | 23 +++
target/linux/generic/config-5.10 | 2 ++
target/linux/generic/config-5.4 | 1 +
3 files
5.10 config.
Fixes build failures with KERNEL_KASAN enabled.
Signed-off-by: Stijn Tintel
---
config/Config-kernel.in | 7 +++
target/linux/generic/config-5.10 | 1 +
2 files changed, 8 insertions(+)
diff --git a/config/Config-kernel.in b/config/Config-kernel.in
index 6758d
Cypress was acquired by Infineon and the URL is no longer valid.
Signed-off-by: Stijn Tintel
---
package/firmware/cypress-firmware/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/firmware/cypress-firmware/Makefile
b/package/firmware/cypress-firmware
This chip is used in the Raspberry Pi Zero 2.
Signed-off-by: Stijn Tintel
---
...ac-BCM43436-needs-dedicated-firmware.patch | 29 +++
1 file changed, 29 insertions(+)
create mode 100644
package/kernel/mac80211/patches/brcm/865-brcmfmac-BCM43436-needs-dedicated-firmware.patch
This package contains the firmware for the Wi-Fi chip used in the
Raspberry Pi Zero 2. This firmware is not available in
linux-firmware.git, nor in the latest Cypress Linux Wi-Fi archive.
Signed-off-by: Stijn Tintel
---
package/firmware/bcm43436-firmware/Makefile | 36 +
1
Signed-off-by: Stijn Tintel
---
package/kernel/bcm27xx-gpu-fw/Makefile | 30 +-
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/package/kernel/bcm27xx-gpu-fw/Makefile
b/package/kernel/bcm27xx-gpu-fw/Makefile
index b99912542b..faca1777fa 100644
--- a
This series adds support for the new Raspberry Pi Zero 2. I've been
running it on mine for 10 days.
Stijn Tintel (5):
cypress-firmware: update URL
mac80211: add patch for BCM43436 firmware
bcm43436-firmware: new package
bcm27xx-gpu-fw: bump to git HEAD
bcm27xx: add support for Rasp
prefix so that it's clear the patch is not in the upstream order.
Signed-off-by: Stijn Tintel
---
.../bcm27xx/base-files/etc/board.d/02_network | 1 +
target/linux/bcm27xx/base-files/etc/diag.sh | 1 +
target/linux/bcm27xx/image/Makefile | 18 +-
...0-9900-ARM-dts-Add-Pi-Z
On 20/11/2021 15:10, Rafał Miłecki wrote:
> On 20.11.2021 04:41, Stijn Tintel wrote:
>> This chip is used in the Raspberry Pi Zero 2.
>>
>> Signed-off-by: Stijn Tintel
>
> This trivial patch could easily be upstreamed, please send it to
> linux-wireless@.
This is
; Main changes in v4:
> - Use cold restart (full SoC reset) on all devices by default
Thanks, will merge these soon.
Tested-by: Stijn Tintel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
current driver), the networking part of the SoC is not
> reset. This leads to unresponsive network after the restart. By
> resetting both the ethernet NIC and queues, networking always comes up
> reliably.
>
Thanks, will merge this soon.
Tested-by: Stijn Tintel
_
This CPU type is compatible with NXP's PPC based QorIQ processors, and
will be used by the upcoming new qoriq target.
Signed-off-by: Stijn Tintel
---
include/target.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/target.mk b/include/target.mk
index 60760bf602..fb57553f7d 1
ELFv2 ABI.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93157 for more info.
Signed-off-by: Stijn Tintel
---
toolchain/gcc/common.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/toolchain/gcc/common.mk b/toolchain/gcc/common.mk
index a195002888..bef4fa37f8 100644
--- a/toolchain/gcc
perlasm scheme. This will probably break the combination
ppc64 with glibc, but as we really only want to support musl, this
shouldn't be a problem.
Signed-off-by: Stijn Tintel
---
package/libs/openssl/Makefile | 2 +-
...m-ppc-xlate.pl-add-linux64v2-flavour.patch
- CONFIG_RCU_NEED_SEGCBLIST=y
- CONFIG_RCU_STALL_COMMON=y
- CONFIG_RCU_TRACE=y
- CONFIG_SCHED_SMT=y
- CONFIG_SCHED_STACK_END_CHECK=y
- CONFIG_SLUB_DEBUG_ON=y
- CONFIG_TRACE_CLOCK=y
Stijn Tintel (8):
build: add e5500 CPU_TYPE
toolchain/musl: ppc64: check for AltiVec in setjmp/longjmp
Signed-off-by: Stijn Tintel
---
...-check-for-AltiVec-in-setjmp-longjmp.patch | 82 +++
1 file changed, 82 insertions(+)
create mode 100644
toolchain/musl/patches/100-ppc64-check-for-AltiVec-in-setjmp-longjmp.patch
diff --git
a/toolchain/musl/patches/100-ppc64-check-for
As of version 3.7, Nettle added PowerPC64 assembly for several
algorithms. Unfortunately, they cause build to fail due to ABI mismatch:
gcm-hash.o: ABI version 1 is not compatible with ABI version 2 output
Disable assembler when ppc64 and musl are used for now.
Signed-off-by: Stijn Tintel
Backport an upstream patch to make libunwind build on ppc64, and add
powerpc64 to the dependencies.
Signed-off-by: Stijn Tintel
---
package/libs/libunwind/Makefile | 4 +--
...ce-exec_prefix-lib64-libdir-on-ppc64.patch | 29 +++
2 files changed, 31 insertions
The default U-Boot boot entry will now boot OpenWrt from the SD card.
Signed-off-by: Stijn Tintel
---
package/boot/uboot-envtools/files/qoriq | 19 +
.../qoriq/base-files/etc/board.d/02_network | 38 ++
.../base-files/lib/preinit/79_move_config | 17 +
.../qoriq/base-fi
qoriq.ko
AUTOLOAD:=$(call AutoProbe,ptp-qoriq)
diff --git a/target/linux/qoriq/Makefile b/target/linux/qoriq/Makefile
new file mode 100644
index 00..960ab32c98
--- /dev/null
+++ b/target/linux/qoriq/Makefile
@@ -0,0 +1,23 @@
+# SPDX-License-Identifier: GPL-2.0-only
+#
+# Copyright (
Please ignore this patch, it's not required for the M300 and upstream
requested changes. I'll omit it when pushing this series and work on it
before continuing on the M200 and BSAP-3040.
On 20/12/2021 21:00, Stijn Tintel wrote:
Signed-off-by: Stijn Tintel
---
...-check-for-
On 21/12/2021 16:49, Rui Salvaterra wrote:
> Hi, Stijn,
>
> Nice to see this! :) A few nits/comments/questions below…
>
> On Mon, 20 Dec 2021 at 19:01, Stijn Tintel wrote:
>> Add a new target named "qoriq", that will support boards using PowerPC
>> processo
If block is NULL, find_mount_point will segfault when comparing it
against the device name found in /proc/self/mountinfo. Avoid this by
checking if block is NULL.
Signed-off-by: Stijn Tintel
---
libfstools/find.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libfstools/find.c b
one is working on fixing this problem, remove the target
> instead. This target also does not have many users we are aware of.
>
> If someone wants to have this target back, feel free to add a fixed
> version of this target again.
>
> Signed-off-by: Ha
On 22/01/2022 14:37, Petr Štetiar wrote:
> Paul Spooren [2022-01-07 10:34:34]:
>
> Hi,
>
> (adding openwrt-adm@ into the loop)
>
>> None of the OpenWrt project members is willing to setup and maintain a
>> GitLab instance
> so what about having that GitLab instance prepared and co-maintained by so
's set the default dialects used for each of the GCC versions we
support, to avoid these toolchain build failures in the future.
Signed-off-by: Stijn Tintel
---
toolchain/gcc/common.mk | 8
1 file changed, 8 insertions(+)
diff --git a/toolchain/gcc/common.mk b/toolchain/gcc/
very easy.
Signed-off-by: Stijn Tintel
---
.../dts/mt7621_tplink_eap615-wall-v1.dts | 250 ++
target/linux/ramips/image/mt7621.mk | 12 +
.../mt7621/base-files/etc/board.d/02_network | 3 +-
tools/firmware-utils/patches/999-eap615.patch | 55
4 files changed
On 27/01/2022 20:10, Bas Mevissen via openwrt-devel wrote:
>
> On 1/25/22 18:02, Stijn Tintel wrote:
>> GCC has an option "-std=" to set the language standard for C and C++.
>> Newer GCC versions sometimes switch to newer standards by default. This
>> has
Avoid flooding the log with the message below by increasing the log
level to debug:
mt7621-nand 1e003000.nand: Using programmed access timing: 31c07388
Signed-off-by: Stijn Tintel
---
target/linux/ramips/files/drivers/mtd/nand/raw/mt7621_nand.c | 2 +-
1 file changed, 1 insertion(+), 1
101 - 200 of 360 matches
Mail list logo
