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 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
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/bcm27xx/bcm2710
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/linux/bcm27xx
it 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/Makefile
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
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
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
> +++
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 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 board yet, so
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 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 ha
nsole=$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
---
rget/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:=powerpc64
+BO
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 | 6
the 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
me.
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/
Stijn Tintel (6):
build: add e6500 CPU_TYPE
tool
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 100644
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
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
>&g
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 files
| deviceid = mbim_get_string(>deviceid, buffer);
| ^~~
Fix them by disabling padding between fields of struct mbim_string.
This change will be committed to umbim.git and the package bumped in
OpenWrt instead, after being acked.
Signed-off-by: St
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
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 --git
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/package
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
toolchain/gcc: switch
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
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
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 resul
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/config
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
in 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
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 changed, 1
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
On 9/04/2021 01:57, Rui Salvaterra wrote:
> It's in backports-5.4, but it wasn't ever merged. Upstream followed another
> approach, with flow offloading, which has much better performance. Drop this
> obsolete patch and refresh the kernel patches.
Acked-by: Stijn Tintel
Some pe
On 31/03/2021 16:09, Rui Salvaterra wrote:
> Break dependencies into separate lines, to improve the readability. Trim
> trailing whitespace.
>
> Signed-off-by: Rui Salvaterra
> ---
> package/system/zram-swap/Makefile | 12 +---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff
relocation R_X86_64_PC32 against symbol
> `__gmp_binvert_limb_table' can not be used when making a shared object;
> recompile with -fPIC
>
> Cc: Stijn Tintel
> Signed-off-by: Eneas U de Queiroz
> ---
>
> There's an error on one architecture, and all others work fine with
On 12/03/2021 10:50, Petr Štetiar wrote:
Stijn Tintel [2021-03-12 01:25:24]:
Hi,
Having libcap in OpenWrt base allows us to enable libcap support in
other packages in base.
there is same functionality available through procd already so essentialy
you're throwing away that effort, increasing
Having libcap in OpenWrt base allows us to enable libcap support in
other packages in base.
In lldpd, this would allow the monitor process to drop its privileges
instead of running as root, improving security. It will also allow us to
drop our patch to disable libcap.
Signed-off-by: Stijn Tintel
Now that libcap is in OpenWrt base, we can drop our custom patch to
disable libcap support and have lldpd depend on it instead. This will
allow the monitor process to drop its privileges instead of running as
root, improving security.
Signed-off-by: Stijn Tintel
---
package/network/services
Signed-off-by: Stijn Tintel
---
package/libs/libcap/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/libs/libcap/Makefile b/package/libs/libcap/Makefile
index 29ff75c5cd..b8e45a52c7 100644
--- a/package/libs/libcap/Makefile
+++ b/package/libs/libcap
Signed-off-by: Stijn Tintel
---
package/libs/libcap/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/package/libs/libcap/Makefile b/package/libs/libcap/Makefile
index 0206bd9d1d..29ff75c5cd 100644
--- a/package/libs/libcap/Makefile
+++ b/package/libs/libcap/Makefile
@@ -1,6 +1,4
#issuecomment-795174537
I'll bump lldpd to the latest version after this series is merged, and
debug the problem reported by John on the realtek target.
Stijn Tintel (4):
libcap: import from packages feed
libcap: drop invalid copyright header
libcap: bump to 2.48
lldpd: add libcap dependency
On 11/03/2021 14:35, Bjørn Mork wrote:
> Demote a number of debugging printk's to pr_debug to avoid log
> nosie. Several of these functions are called as a result of
> userspace activity. This can cause a lot of log noise when
> userspace does periodic polling.
>
> Most of this could probably be
or other changes, so let's use -fPIC on
arm64 by default.
While comparing the sizes of 141 packages built with -fpic vs -fPIC,
most packages are either equal or smaller in size. Only 9 of the
compared packages turned out slightly larger.
Signed-off-by: Stijn Tintel
---
rules.mk | 2 +-
1 file
On 7/11/2020 16:17, Daniel Golle wrote:
> Hi all!
>
> A while ago we have added some useful kernel features to !SMALL_FLASH
> devices[1]. To make more use of that by default in a way which will
> make exploiting potential vulnerabilities in OpenWrt's services much
> harder, it'd be great to also
On 9/10/2020 15:19, Adrian Schmutzler wrote:
Opinions? Is anybody still using 4.19 at least occasionally?
+1 for removal
Stijn
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
options for CT_KVER from the comment, as it is incorrect
and there are too many versions to sum up and maintain there.
Runtime-tested on ath79.
Signed-off-by: Stijn Tintel
---
package/kernel/ath10k-ct/Makefile | 6 +-
...64-ath10k-commit-rates-from-mac80211.patch | 24 ++--
...rolling
Runtime-tested on ath79.
Signed-off-by: Stijn Tintel
---
package/kernel/ath10k-ct/Makefile | 6 +++---
.../patches/164-ath10k-commit-rates-from-mac80211.patch | 6 +++---
...-and-GPIO-controlling-support-for-various-chipsets.patch | 6 +++---
.../patches/202-ath10k
And since we are using mac80211 5.8, let's also switch the ath10k-ct
driver to the new 5.8 version.
Signed-off-by: Stijn Tintel
---
package/kernel/ath10k-ct/Makefile | 10 +-
.../164-ath10k-commit-rates-from-mac80211.patch| 6 +++---
...GPIO-controlling
On 30/08/2020 10:57, Paul Spooren wrote:
> The question came up if we really want RSA certificates for LuCI or if
> the faster and "more modern" ECC P-256 wouldn't be a better choice.
>
> If px5g is added to the next release, certificates are generated on
> first boot and most users are unlikely
ant, and `which` is not, in
the commit message.
Acked-by: Stijn Tintel
>
> Signed-off-by: Paul Spooren
> ---
> include/rootfs.mk| 6 +++---
> package/base-files/files/lib/upgrade/stage2 | 2 +-
> .../kernel/broadcom-wl/files/lib/wifi/
not force the user to use either of them,
so add them as build-configurable kernel options.
Fixes: d1a8217d87bf ("kernel: clean-up build-configurable kernel config
symbols")
Signed-off-by: Stijn Tintel
---
config/Config-kernel.in | 12
target/linux/generic/config-5.4
This symbol is exposed on ARM64 with EFI enabled in the kernel config.
Currently this happens only on ipq807x, but as there might be new ARM64
targets with EFI in the future it is better to add the symbol to the
generic config.
Signed-off-by: Stijn Tintel
---
target/linux/generic/config-4.14
ac
- wlanmac_a
The first 3 all contain the same MAC address, which is also the one on
the label.
Signed-off-by: Stijn Tintel
---
.../ath79/dts/qca9558_dlink_dap-2695-a1.dts | 176 ++
.../generic/base-files/etc/board.d/02_network | 6 +
.../etc/hotplug.d/firmware/10-ath9k-eeprom
This is required for the D-Link DAP-2695-A1.
Signed-off-by: Stijn Tintel
---
target/linux/ath79/config-4.19 | 1 +
target/linux/ath79/config-5.4 | 1 +
2 files changed, 2 insertions(+)
diff --git a/target/linux/ath79/config-4.19 b/target/linux/ath79/config-4.19
index cfa0ebd759..81fd017aba
s://git.openwrt.org/?p=openwrt/staging/stintel.git;a=summary
Stijn Tintel (3):
mtd: enable wrgg support for ath79
ath79: enable wrgg MTD splitter
ath79: add support for D-Link DAP-2695-A1
package/system/mtd/src/Makefile | 2 +-
target/linux/ath79/config-4.19| 1 +
This is required for the D-Link DAP-2695-A1.
Signed-off-by: Stijn Tintel
---
package/system/mtd/src/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/system/mtd/src/Makefile b/package/system/mtd/src/Makefile
index e504a04478..6da31a04a4 100644
--- a/package
eave
those extra snippets in /etc/config/network, and then the device VLAN
setup would differ from the one used in ar71xx. Therefore, the MAC
addresses of the ethernet interfaces are being set via preinit instead.
Signed-off-by: Stijn Tintel
---
.../ath79/dts/qca9558_dlink_dap-2695-a1.dts |
This is required for the D-Link DAP-2695-A1.
Signed-off-by: Stijn Tintel
---
package/system/mtd/src/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/system/mtd/src/Makefile b/package/system/mtd/src/Makefile
index e504a04478..6da31a04a4 100644
--- a/package
This is required for the D-Link DAP-2695-A1.
Signed-off-by: Stijn Tintel
---
target/linux/ath79/config-4.19 | 1 +
target/linux/ath79/config-5.4 | 1 +
2 files changed, 2 insertions(+)
diff --git a/target/linux/ath79/config-4.19 b/target/linux/ath79/config-4.19
index cfa0ebd759..81fd017aba
label.
* Drop board from /etc/board.d/01_leds.
* Add ath10k-ct and firmware to DEFAULT_PACKAGES.
[0] https://git.openwrt.org/?p=openwrt/staging/stintel.git;a=summary
Stijn Tintel (3):
mtd: enable wrgg support for ath79
ath79: enable wrgg MTD splitter
ath79: add support for D-Link DAP-26
nmac_a
The first 3 all contain the same MAC address, which is also the one on
the label. This MAC address is used for the 2.4GHz interface, eth0 uses
this MAC+1, eth1 uses this MAC+2, as is done in ar71xx.
Signed-off-by: Stijn Tintel
---
.../ath79/dts/qca9558_dlink_dap-2695-a1.dts | 172 ++
This is required for the D-Link DAP-2695-A1.
Signed-off-by: Stijn Tintel
---
package/system/mtd/src/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/system/mtd/src/Makefile b/package/system/mtd/src/Makefile
index e504a04478..6da31a04a4 100644
--- a/package
Move the generic D-Link image definitions to a separate file, as is done
for several other vendors.
Signed-off-by: Stijn Tintel
---
target/linux/ath79/image/Makefile | 1 +
target/linux/ath79/image/generic-dlink.mk | 114 +
target/linux/ath79/image/generic.mk
This series adds support for the D-Link DAP-2695-A1 to the ath79 target.
Also available in my staging tree at [0].
Successfully tested sysupgrade from ar71xx to ath79.
[0] https://git.openwrt.org/?p=openwrt/staging/stintel.git;a=summary
Stijn Tintel (4):
mtd: enable wrgg support for ath79
This is required for the D-Link DAP-2695.
Signed-off-by: Stijn Tintel
---
target/linux/ath79/config-4.19 | 1 +
target/linux/ath79/config-5.4 | 1 +
2 files changed, 2 insertions(+)
diff --git a/target/linux/ath79/config-4.19 b/target/linux/ath79/config-4.19
index cfa0ebd759..81fd017aba
On 16/03/2020 09:37, Hans Dedecker wrote:
>>> One would argue that ip-full should correspond to the full fledged
>>> version of the packet. If the dependency of an external package is the
>>> issue, how about making a different variant with HAVE_CAP support? It
>>> could be called ip-really-full
On 3/03/2020 17:21, Petr Štetiar wrote:
> Otherwise we would need to enable IIO_TRIGGERED_BUFFER symbol in all
> kernels in order to be able to use any of the IIO modules which are
> utilizing triggered buffer based data acquisition method.
Acked-by: Sti
On 3/03/2020 17:21, Petr Štetiar wrote:
> Adds into 4.19 backported kernel module from 5.1 for Sensirion SPS30
> particulate matter sensor, for kernel 5.4 backported dependency fix.
>
I have my doubts about the backport for 4.19. I would prefer to skip it,
as we're moving master to 5.4.
Stijn
On 28/02/2020 18:56, Tim Harvey wrote:
> Signed-off-by: Tim Harvey
> ---
> package/kernel/linux/modules/can.mk | 17 +
> 1 file changed, 17 insertions(+)
>
> diff --git a/package/kernel/linux/modules/can.mk
> b/package/kernel/linux/modules/can.mk
> index c2c7411..3bf0359 100644
This activates PIE ASLR support by default when the regular option is
selected. This is required to enable PIE ASLR support by default in ppp,
as it fails to build without it, on x86/64.
The .so file size stays identical.
Suggested-by: Felix Fietkau
Signed-off-by: Stijn Tintel
---
package
On 22/02/2020 11:10, Felix Fietkau wrote:
> On 2020-02-22 09:54, Stijn Tintel wrote:
>> On 20/02/2020 11:56, Petr Štetiar wrote:
>>> This activates PIE ASLR support by default when the regular option is
>>> selected.
>>>
>> Unfortunately this seems to b
On 20/02/2020 11:56, Petr Štetiar wrote:
> This activates PIE ASLR support by default when the regular option is
> selected.
>
Unfortunately this seems to break build on x86/64:
x86_64-openwrt-linux-musl-gcc -O2 -pipe -fno-caller-saves -fno-plt
-fhonour-copts -Wno-error=unused-but-set-variable
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 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
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
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 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
/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
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
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_id=2593
>
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_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
> The
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.openwrt.org
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 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
/linker flags.
Tested-by: Stijn Tintel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
| 1 -
> package/utils/usbmode/files/usbmode.init | 1 -
> 32 files changed, 32 deletions(-)
>
>
Acked-by: Stijn Tintel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
; package/base-files/files/etc/rc.common | 113 ++---
> 1 file changed, 47 insertions(+), 66 deletions(-)
>
Acked-by: Stijn Tintel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 8/06/19 14:48, André Valentin wrote:
> This package adds scripts for xfrm interfaces support.
> Example configuration via /etc/config/network:
>
> config interface 'xfrm0'
> option proto 'xfrm'
> option mtu '1300'
> option zone 'VPN'
> option tunlink 'wan'
>
Hi,
Since we now have a 19.07 branch, is it OK to switch KERNEL_PATCHVER for
targets in master that have 4.19 support to 4.19?
Thanks,
Stijn
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
On 23/01/19 19:59, Linus Walleij wrote:
> This adds a config and augments the gemini makefile to
> use kernel v4.19.
>
> These devices work so much better with v4.19 so let's
> immediately make it the default.
NAK. All targets need to be on 4.14 until 19.01 is branched.
Stijn
On 7/12/18 05:06, Stijn Tintel wrote:
> On 11/11/18 18:37, Stijn Tintel wrote:
>> Hi,
>>
>> I have just pushed support for the 4.14 kernel on the brcm2708 target to
>> my staging tree [1], and would like to get some feedback before pushing
>> it to master. It woul
On 7/12/18 10:17, Alexandru Ardelean wrote:
> On Fri, Dec 7, 2018 at 5:06 AM Stijn Tintel wrote:
>> On 11/11/18 18:37, Stijn Tintel wrote:
>>> Hi,
>>>
>>> I have just pushed support for the 4.14 kernel on the brcm2708 target to
>>> my staging tree [1
On 11/11/18 18:37, Stijn Tintel wrote:
> Hi,
>
> I have just pushed support for the 4.14 kernel on the brcm2708 target to
> my staging tree [1], and would like to get some feedback before pushing
> it to master. It would also be nice if people could do runtime tests on
> bcm2709
On 12/11/18 19:00, Christian Lamparter wrote:
> (Did some EMails get mangled?:
> "openwrt-devel@lists.openwrt.org j...@openwrt.org" ")
>
> On Monday, November 12, 2018 4:55:12 PM CET Stijn Tintel wrote:
>> On 12/11/18 15:26, Alexandru Ardelean wrote:
>>> [
On 12/11/18 17:56, Jonathan Thibault wrote:
> This is a very simple patch that completes sysupgrade functionality on
> UBNT ER8.
>
> Default layout leaves about 128MB free on the kernel partition so
> there is plenty of space for temporary config backups.
>
>
> diff --git
master, and preferably sooner rather than later.
>
> Thanks
> Alex
>
> On Sun, Nov 11, 2018 at 6:37 PM Stijn Tintel wrote:
>> Hi,
>>
>> I have just pushed support for the 4.14 kernel on the brcm2708 target to
>> my staging tree [1], and would like to get some fee
Hi,
I have just pushed support for the 4.14 kernel on the brcm2708 target to
my staging tree [1], and would like to get some feedback before pushing
it to master. It would also be nice if people could do runtime tests on
bcm2709 and bcm2710, as I don't own such hardware.
Thanks,
Stijn
[1]
101 - 200 of 348 matches
Mail list logo
