On 13.11.20 13:35, Adrian Schmutzler wrote:
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Josef Schlehofer
Sent: Freitag, 13. November 2020 09:33
To: openwrt-devel@lists.openwrt.org
Cc: Hauke Mehrtens
Subject: [PATCH 19.07] kernel:
Hi all,
I'm playing around with Mikrotik stuff to test flashing from 19.07
ar71xx towards master using sysupgrade.
Trying this natively using sysupgrade shows Invalid firmware image:
dd
'if=/tmp/openwrt-ath79-mikrotik-mikrotik_routerboard-922uags-5hpacd-squashfs-sysupgrade.bin'
'skip=0' 'b
On 12.04.21 17:31, Daniel Golle wrote:
On Mon, Apr 12, 2021 at 10:45:14PM +0800, DENG Qingfang wrote:
After the commit, devices with mtd-concat such as HC5962 no longer work.
Several "sysfs: cannot create duplicate filename '/devices/..." warnings
can be seen in kernel log.
I'm working on it,
Hi all,
I found another interesting issue testing on a rb922
The board gets a random mac on each boot.
This is normal and should be automatically corrected by 02_network
afterwards when hard_config is available, but it seems it's not getting
applied correctly.
Debugging the 02_network script s
Hi All,
Another week .. another kernel bump ..
This week, stable 4.19 received a fair amount of changes for netfilter
and offloading stuff.
The bump required some altering of patches at critical locations to make
everything apply squeaky clean.
To be absolutely sure, I would like to file
On 27.02.19 08:13, Lorenzo Bianconi wrote:
What I mean is just a p2p link running in AP-STA mode, I guess there is no
difference for users. Am I missing something?
Is dynack going to receive the late acks if I manage to run
wpa_supplicant (wpad-mini?) in plaintext or key_mgmt=NONE mode?
Hi All,
Could someone with more knowledge regarding dependencies take a look at
this?
koen@bob:~/firmware/builds/generic_cns3xxx$ make menuconfig
feeds/packages/net/openconnect/Config.in:6:error: recursive dependency
detected!
For a resolution refer to Documentation/kbuild/kconfig-language
Hi Daniel,
When running the image builder for my targets, I'm getting following error:
"Can't use an undefined value as an ARRAY reference at
/mnt/ramdisk/koen/firmware/.21128/openwrt-imagebuilder-cns3xxx.Linux-x86_64/scripts/target-metadata.pl
line 426."
It seems you made 2 changes last w
ncurrently.
Selection can be done by toggling a GPIO.
By default, the USB is routed to the mini-PCIe slot.
Installation:
- Boot vmlinux-initramfs image via BOOTP/TFTP and then flash sysupgrade
image using "sysupgrade -n"
Signed-off-by: Koen Vandeputte
---
.../ar71xx/base-files/et
ncurrently.
Selection can be done by toggling a GPIO.
By default, the USB is routed to the mini-PCIe slot.
Installation:
- Boot vmlinux-initramfs image via BOOTP/TFTP and then flash sysupgrade
image using "sysupgrade -n"
Signed-off-by: Koen Vandeputte
---
v2: fix double init of PCI
Hi Ben,
Following our conversation from yesterday, here is a summary of all
issues seen so far:
Test setup:
- Board: Mikrotik RB922
- Hardware used: on-board QCA9882 (QCA988x), Wave1 2x2 .ac
- firmware's tested: both non-HTT and HTT flavours for qca988x
Synopsis:
- Setting the interface in
On 26.03.19 14:50, Ben Greear wrote:
On 03/26/2019 03:09 AM, Koen Vandeputte wrote:
Hi Ben,
Following our conversation from yesterday, here is a summary of all
issues seen so far:
Test setup:
- Board: Mikrotik RB922
- Hardware used: on-board QCA9882 (QCA988x), Wave1 2x2 .ac
On 15.03.19 10:00, Koen Vandeputte wrote:
Hi Daniel,
When running the image builder for my targets, I'm getting following
error:
"Can't use an undefined value as an ARRAY reference at
/mnt/ramdisk/koen/firmware/.21128/openwrt-imagebuilder-cns3xxx.Linux-x86_64/scripts/tar
On 27.03.19 22:56, Daniel Golle wrote:
Hi Koen,
I hope I fixed the issue with commit
7204736076 IB: fix generating .profile.mk for profiles without metadata
Please report back if you also see it fixed by this.
Hi Daniel,
I'm pleased to confirm it's fixed :-)
Appreciated!
Koen
___
On 26.03.19 19:39, Ben Greear wrote:
On 3/26/19 6:59 AM, Koen Vandeputte wrote:
On 26.03.19 14:50, Ben Greear wrote:
On 03/26/2019 03:09 AM, Koen Vandeputte wrote:
Hi Ben,
Following our conversation from yesterday, here is a summary of all
issues seen so far:
Test setup:
- Board
On 31.03.19 15:45, Lorenzo Bianconi wrote:
could you please try to attached patch? The max distance the hw can
support depends of channel width:
e.g @20MHz (HT20, 5GHz)
max distance is ~ 61Km
@Koen: do you have any chance to test the attached patch in your
environment? Thx
Hi Lorenzo,
I d
On 12.04.19 16:32, Roman Yeryomin wrote:
Compile and run tested on mt7621 and ar71xx
new features:
- priority-inheritance mutexes
- membarrier syscall, pre-registration to use it, fallback emulation
- header-level support for new linux features in 4.19, 4.20, 5.0
major internal changes:
- com
On 12.04.19 17:04, Roman Yeryomin wrote:
On 2019-04-12 17:39, Koen Vandeputte wrote:
On 12.04.19 16:32, Roman Yeryomin wrote:
Compile and run tested on mt7621 and ar71xx
new features:
- priority-inheritance mutexes
- membarrier syscall, pre-registration to use it, fallback emulation
- header
On 29.03.19 13:55, Hauke Mehrtens wrote:
On 3/29/19 1:43 PM, Ben Greear wrote:
On 03/29/2019 02:58 AM, Koen Vandeputte wrote:
On 26.03.19 19:39, Ben Greear wrote:
On 3/26/19 6:59 AM, Koen Vandeputte wrote:
On 26.03.19 14:50, Ben Greear wrote:
On 03/26/2019 03:09 AM, Koen Vandeputte wrote
Hi All,
It seems the latest state (or packages) seems to contain a recursive
dependency:
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:63605: symbol PACKAGE_libmicrohttpd-ssl
depends on PACKAGE_libmicrohttpd-no-ssl
For a resolution refer to Documentation/kb
(2048 bytes) now.
Signed-off-by: Koen Vandeputte
---
target/linux/ar71xx/files/arch/mips/ath79/mach-rb2011.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-rb2011.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-rb2011.c
On 11.06.19 23:12, Jonas Gorski wrote:
Hi,
On Tue, 11 Jun 2019 at 23:08, Stijn Tintel wrote:
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?
Fine by me. The earlier we start testing 4.19, the faster we can iron
On 12.06.19 14:06, Jonas Gorski wrote:
On Wed, 12 Jun 2019 at 11:02, Koen Vandeputte
wrote:
On 11.06.19 23:12, Jonas Gorski wrote:
Hi,
On Tue, 11 Jun 2019 at 23:08, Stijn Tintel wrote:
Hi,
Since we now have a 19.07 branch, is it OK to switch KERNEL_PATCHVER for
targets in master that
On 14.05.19 16:49, Petr Štetiar wrote:
Tautvydas Belgeras [2019-05-14 16:20:05]:
Hi,
Patch fixes utility returning "Unknown error" when generating a request
after a wait of a few minutes
quoting from https://openwrt.org/submitting-patches
* commit subject
- must have a prefix that de
On 19.06.19 11:41, Tautvydas Belgeras wrote:
When the utility sends a request it expects a response type message,
but does not explicitly check for it. When a device stays idle for
some time, it switches into a sleep mode, and notifies the utility with an
identification type message. In some co
Hi Ben,
Hi All,
So I'm going to give this another try ..
As the IBSS functionality is heavily advertised as a delta to mainline,
it would be very nice to get it working also :)
Testing the latest ath10k-ct driver and firmware seems to be a step back
compared to roughly a month ago.
I'm curr
On 24.06.19 22:04, Ben Greear wrote:
On 6/24/19 8:32 AM, Koen Vandeputte wrote:
Hi Ben,
Hi All,
So I'm going to give this another try ..
As the IBSS functionality is heavily advertised as a delta to
mainline, it would be very nice to get it working also :)
Testing the latest ath1
tmp/.config-package.in:88518:error: recursive dependency detected!
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:88518: symbol PACKAGE_nfs-kernel-server
depends on NFS_KERNEL_SERVER_V4
For a res
On 25.06.19 15:54, Ben Greear wrote:
On 06/25/2019 02:53 AM, Koen Vandeputte wrote:
On 24.06.19 22:04, Ben Greear wrote:
On 6/24/19 8:32 AM, Koen Vandeputte wrote:
Hi Ben,
Hi All,
So I'm going to give this another try ..
As the IBSS functionality is heavily advertised as a del
On 25.06.19 15:54, Ben Greear wrote:
On 06/25/2019 02:53 AM, Koen Vandeputte wrote:
On 24.06.19 22:04, Ben Greear wrote:
On 6/24/19 8:32 AM, Koen Vandeputte wrote:
Hi Ben,
Hi All,
So I'm going to give this another try ..
As the IBSS functionality is heavily advertised as a del
On 26.06.19 11:02, Koen Vandeputte wrote:
On 25.06.19 15:54, Ben Greear wrote:
On 06/25/2019 02:53 AM, Koen Vandeputte wrote:
On 24.06.19 22:04, Ben Greear wrote:
On 6/24/19 8:32 AM, Koen Vandeputte wrote:
Hi Ben,
Hi All,
So I'm going to give this another try ..
As the
On 26.06.19 18:16, Ben Greear wrote:
On 6/26/19 2:02 AM, Koen Vandeputte wrote:
On 25.06.19 15:54, Ben Greear wrote:
On 06/25/2019 02:53 AM, Koen Vandeputte wrote:
On 24.06.19 22:04, Ben Greear wrote:
On 6/24/19 8:32 AM, Koen Vandeputte wrote:
Hi Ben,
Hi All,
So I'm going to give
On 20.06.19 12:45, Tautvydas Belgeras wrote:
When the utility sends a request it expects a response type message,
but does not explicitly check for it. When a device stays idle for
some time, it switches into a sleep mode, and notifies the utility with an
identification type message. In some co
On 26.06.19 18:39, Ben Greear wrote:
On 6/26/19 9:28 AM, Koen Vandeputte wrote:
On 26.06.19 18:16, Ben Greear wrote:
On 6/26/19 2:02 AM, Koen Vandeputte wrote:
On 25.06.19 15:54, Ben Greear wrote:
On 06/25/2019 02:53 AM, Koen Vandeputte wrote:
On 24.06.19 22:04, Ben Greear wrote:
On
On 27.06.19 16:24, Ben Greear wrote:
On 6/27/19 7:17 AM, Koen Vandeputte wrote:
On 26.06.19 18:39, Ben Greear wrote:
On 6/26/19 9:28 AM, Koen Vandeputte wrote:
On 26.06.19 18:16, Ben Greear wrote:
On 6/26/19 2:02 AM, Koen Vandeputte wrote:
On 25.06.19 15:54, Ben Greear wrote:
On 06
On 07.07.19 19:28, Hauke Mehrtens wrote:
This updates to backports-4.19.57-1 which contains the wireless
subsystem and driver from kernel 4.19.57.
The removed patches are applied upstream.
Tested-by: Koen Vandeputte
- Quad radio 802.11n (ar9220) on cns3xxx
- Dual radio 802.11n (ar9582) on
Hi All,
I've been playing around the last few days stresstesting latest 19.07 on
different targets (ar71xx, cns3xxx, imx6, ...) with extra kernel debug
features enabled.
I'll post some results here as maybe somebody has a clue. :)
Some interesting splats already showed up, actually also *br
On 01.08.19 17:27, Koen Vandeputte wrote:
Hi All,
I've been playing around the last few days stresstesting latest 19.07
on different targets (ar71xx, cns3xxx, imx6, ...) with extra kernel
debug features enabled.
I'll post some results here as maybe somebody has a clue.
On 05.08.19 18:17, Koen Vandeputte wrote:
On 05.08.19 17:47, Koen Vandeputte wrote:
On 27.06.19 16:24, Ben Greear wrote:
On 6/27/19 7:17 AM, Koen Vandeputte wrote:
On 26.06.19 18:39, Ben Greear wrote:
On 6/26/19 9:28 AM, Koen Vandeputte wrote:
On 26.06.19 18:16, Ben Greear wrote:
On 6
On 09.08.19 14:48, Ben Greear wrote:
On 8/6/19 2:26 AM, Koen Vandeputte wrote:
Hi Ben,
I finally managed to get to some time to properly take a look using
a simple setup.
Attached all required files to simulate the issue.
I compiled the latest OpenWrt master state, (included a full
On 09.08.19 15:31, Koen Vandeputte wrote:
On 09.08.19 14:48, Ben Greear wrote:
On 8/6/19 2:26 AM, Koen Vandeputte wrote:
Hi Ben,
I finally managed to get to some time to properly take a look
using a simple setup.
Attached all required files to simulate the issue.
I compiled the latest
Hi Joe,
Lorenzo, I deployed an ath9k auto distance solution in April that is
working for the AREDN community http://www.arednmesh.org .
https://github.com/aredn/aredn_ar71xx/blob/develop/patches/712-auto-distance-settings.patch
Summary of solution:
* no dependency on wpa_supplicant
* init
These are added in ath79, but were not backported here
Signed-off-by: Koen Vandeputte
---
.../files/drivers/net/ethernet/atheros/ag71xx/ag71xx_main.c | 5 +
1 file changed, 5 insertions(+)
diff --git
a/target/linux/ar71xx/files/drivers/net/ethernet/atheros/ag71xx/ag71xx_main.c
b/target
initialized the ackto to max:
A) avoidance of late-ack state
B) not require wpa_supplicant -- not in use by our community today
C) Suspect some conditions, e.g. low SNR Neighbors, do not trigger
"late ack" (consistent, with observation of low SNR Neighbors sticking
at max ack_to with my chang
On 28.08.19 19:34, Joe Ayers wrote:
initialized the ackto to max:
A) avoidance of late-ack state
B) not require wpa_supplicant -- not in use by our community today
C) Suspect some conditions, e.g. low SNR Neighbors, do not trigger
"late ack" (consistent, with observation of low SNR Neighbors
On 2018-07-30 21:31, Stijn Segers wrote:
* Refreshed patches.
* Patches made redundant by changes upstream:
-
target/linux/ramips/patches-4.14/0036-mtd-fix-cfi-cmdset-0002-erase-status-check.patch
* Patches accepted upstream:
-
target/linux/apm821xx/patches-4.14/020-0001-crypto-crypto4
On 2018-07-30 21:31, Stijn Segers wrote:
* Refreshed patches.
* Removed patches:
-
target/linux/ar71xx/patches-4.9/103-MIPS-ath79-fix-register-address-in-ath79_ddr_wb_flus.patch
superseded by upstream
-
target/linux/ar71xx/patches-4.9/403-mtd_fix_cfi_cmdset_0002_status_check.patch
su
Hi Stijn,
It seems a new helper was introduced in newer kernels:
-- a/fs/ext4/super.c
++ b/fs/ext4/super.c
@@ -3103,14 +3103,8 @@ static ext4_group_t ext4_has_uninit_itab
if (!gdp)
continue;
- if (gdp->bg_flags & cpu_to_le16(EXT4_BG_INODE_Z
Hi All,
During bumping this morning, I noticed the master already mentions 4
different kernel versions currently ..
In master:
- kernel 4.4 is not used by any target
In 18.06:
- kernel 3.18 is not used by any target
- kernel 4.4 is not used by any target
Removing these would already provid
During compiling/testing the new kernel bumps, I'm getting this on 7
different builds:
make[3]: Entering directory
'/mnt/ramdisk/koen/firmware/builds/generic_cns3xxx/package/base-files'
rm -f
/mnt/ramdisk/koen/firmware/builds/generic_cns3xxx/build_dir/target-arm_mpcore+vfp_musl_eabi/linux-cn
Refreshed all patches.
Compile-tested on: adm5120, adm8668, au1000, mcs814x, ppc40x, ppc44x, xburst
Runtime-tested on: none
Signed-off-by: Koen Vandeputte
---
include/kernel-version.mk | 4 +-
.../patches-3.18/007-adm5120_pci.patch| 2 +-
.../101
This target is on 4.9 currently.
It seems the support for this old kernel never got dropped.
Signed-off-by: Koen Vandeputte
---
target/linux/ar7/config-3.18 | 129
.../001-mips-ar7-fix-serial.patch | 23 --
...re-the-port-type-s-FCR-value-is-used.patch
On 2018-08-13 17:14, John Crispin wrote:
Hi,
as 19.01 will probably use v4.14 as baseline and ath79 wont be a full
replacement for ar71xx by then we decided to bump ar71xx to v4.14.
This is available for testing inside my staging tree ->
https://git.openwrt.org/?p=openwrt/staging/blogic.gi
^
arch/mips/ath79/mach-rb2011.c:23:10: fatal error: linux/mtd/rawnand.h: No such
file or directory
#include
^
cc1: all warnings being treated as errors
compilation terminated.
Fixes: 318e19ba6755 ("ar71xx: add v4.14 support")
^
Fixes: 318e19ba6755 ("ar71xx: add v4.14 support")
Signed-off-by: Koen Vandeputte
---
target/linux/ar71xx/files/arch/mips/ath79/mach-c60.c | 1 +
target/linux/ar71xx/files/arch/mips/ath79/mach-domywifi-dw33d.c | 1 +
target/linux/ar71xx
linux/mtd/rawnand.h: No such
file or directory
#include
^
compilation terminated.
Fixes: 318e19ba6755 ("ar71xx: add v4.14 support")
Signed-off-by: Koen Vandeputte
---
target/linux/ar71xx/files/drivers/mtd/nand/ar934x_nfc.c | 6 +-
target/linux
ar71xx:
I'm now currently testing your ar71xx 4.14 bump (comitted today in
master) on a few different targets:
- Gl-mifi
- Rocket-m5
- RB912
- RB2011
...
Will let you know the results.
Hi John,
I started with trying on a Mikrotik RB2011 as these have a Serial port.
Ethernet does not fu
On 2018-08-22 16:14, Koen Vandeputte wrote:
ar71xx:
I'm now currently testing your ar71xx 4.14 bump (comitted today in
master) on a few different targets:
- Gl-mifi
- Rocket-m5
- RB912
- RB2011
...
Will let you know the results.
Hi John,
I started with trying on a Mikrotik RB20
hin the mediatek target,
which otherwise is applied twice and results in a build error.
Fixes: 7af1fb9faafb ("kernel: add a RPS balancer")
Signed-off-by: Koen Vandeputte
---
.../0048-net-core-add-RPS-balancer.patch | 90 ---
1 file changed, 90 deletions(-)
delete mo
On 2018-08-23 19:00, Sven Schönhoff wrote:
curious what i missed as my archer-c7-v4 is working fine. TPLINK
AC1750 device
Hi,
please dont top post
I have no idea what you are asking.
Meaning I don't understand his issue mine works fine, so I'm curious as to
what's different
I would gues
Hi John,
Thanks for the updates!
mac80211:
I've tested mac80211 on a large number of targets in the field:
- ~25 devices
- half of them having up to 4 wlan ifaces
- all running in IBSS
- Distance varying from 20m up to ~50km
For my cases, it seems to work well.
Small nit-pick:
In the bo
Hi Felix,
Starting from commit [1], I'm getting this error when trying to use the
Imagebuilder, even when selecting them in the build:
...
Package libc (1.1.19-1) installed in root is up to date.
Package libgcc (7.3.0-1) installed in root is up to date.
Package logd (2018-02-14-128bc35f-2) ins
Backport most significant upstream fixes (excl. hwsim fixes)
Refreshed all patches.
Contains important fixes for CSA (Channel Switch Announcement)
and A-MSDU frames.
Signed-off-by: Koen Vandeputte
---
...-teardown-code-before-de-registering.patch | 38 +++
...x-HWMP-sequence-numbering-to
On 2018-09-05 10:01, Felix Fietkau wrote:
On 2018-09-04 22:04, Felix Fietkau wrote:
On 2018-09-04 18:39, Koen Vandeputte wrote:
Hi Felix,
Starting from commit [1], I'm getting this error when trying to use the
Imagebuilder, even when selecting them in the build:
...
Package libc (1.1
On 2018-09-05 10:01, Felix Fietkau wrote:
On 2018-09-04 22:04, Felix Fietkau wrote:
Just tested it, and it works just fine in my build. Did you use the
image builder from the snapshot build, or did you build your own?
Will provide an update asap.
Hi Felix,
I found the culprit ..
I inclu
This one is running stable here on a lot of different devices (and
targets) for the past 48 hours
Tested-by: Koen Vandeputte
Christian,
A few hours after release, Rich committed some quick-fixes for various
stuff.
Do some of these need backporting on top of this patch in your opinion
On 2018-09-06 18:16, Christian Lamparter wrote:
On Thursday, September 6, 2018 12:31:23 PM CEST Koen Vandeputte wrote:
This one is running stable here on a lot of different devices (and
targets) for the past 48 hours
Tested-by: Koen Vandeputte
That's good to hear. Did you see an
Hi Richard,
I'm currently in the process of updating the kernel version within
OpenWrt. (4.14.68 to 4.14.69)
Testing shows some issues on devices using specifically UBIFS.
Altering a perfect valid writable file shows weird errors:
[ Node 2 | node-2 ] ls -l /root/custom/scripts/banner.sh
-rwx
On 2018-09-11 15:46, Koen Vandeputte wrote:
Hi Richard,
...
I'm only seeing these issues on UBIFS enabled volumes.
It seems it's related to one of your 5 commits, but I'm still in the
process of bisecting to find the actual culprit.
As soon as I've found it, I'l
Hi All,
When I'm doing a lot of fresh builds for testing purposes, some of them
tend to fail sometimes with following error:
make[3]: Entering directory
'/mnt/ramdisk/koen/firmware/builds/generic_imx6/package/base-files'
rm -f
/mnt/ramdisk/koen/firmware/builds/generic_imx6/build_dir/target-a
On 16-09-18 21:39, Richard Weinberger wrote:
Koen,
Am Samstag, 15. September 2018, 09:13:09 CEST schrieb Richard Weinberger:
Koen,
Am Dienstag, 11. September 2018, 16:26:34 CEST schrieb Koen Vandeputte:
On 2018-09-11 15:46, Koen Vandeputte wrote:
Hi Richard,
...
I'm only seeing
On 16-09-18 17:28, Stijn Segers wrote:
Refreshes patches and bumps 4.14 kernel to 4.14.70 for OpenWrt 18.06.
Compile-tested on ramips/mt7621, x86/64.
Run-tested on ramips/mt7621, x86/64.
Signed-off-by: Stijn Segers
---
Hi Stijn,
Thanks for the patch.
I've notified Richard Weinberger of
On 2018-09-16 23:05, Koen Vandeputte wrote:
On 16-09-18 17:28, Stijn Segers wrote:
Refreshes patches and bumps 4.14 kernel to 4.14.70 for OpenWrt 18.06.
Compile-tested on ramips/mt7621, x86/64.
Run-tested on ramips/mt7621, x86/64.
Signed-off-by: Stijn Segers
---
Hi Stijn,
Thanks for
On 2018-09-23 00:42, Hauke Mehrtens wrote:
Hi,
We talked about plans for the next OpenWrt releases in this mail thread:
http://lists.infradead.org/pipermail/openwrt-adm/2018-July/000849.html
This mail is more or less a summary of the conclusions, this is still
open for change especially the d
On 2018-10-02 12:22, Kevin Darbyshire-Bryant wrote:
Refresh patches.
Remove upstreamed patch:
generic/pending-4.14/192-Revert-ubifs-xattr-Don-t-operate-on-deleted-inodes.patch
Compile-tested on: ath79
Runtime-tested on: ath79
Signed-off-by: Kevin Darbyshire-Bryant
---
This could do with
On 2018-08-13 17:14, John Crispin wrote:
Hi,
as 19.01 will probably use v4.14 as baseline and ath79 wont be a full
replacement for ar71xx by then we decided to bump ar71xx to v4.14.
This is available for testing inside my staging tree ->
https://git.openwrt.org/?p=openwrt/staging/blogic.gi
On 04-10-18 02:49, Paul Blazejowski wrote:
Koen,
Please see below, i don't know if John got my mail but i surely missed
the updated mailing list address last time...
If full console logs are needed, please let me know.
Thank you,
-paul
Hi Paul,
I fixed this a while ago [1]
Could you r
On 2018-10-03 20:06, Dirk Brenken wrote:
On Mi, 2018-10-03 at 17:59 +0200, Koen Vandeputte wrote:
On 2018-08-13 17:14, John Crispin wrote:
Hi,
as 19.01 will probably use v4.14 as baseline and ath79 wont be a
full
replacement for ar71xx by then we decided to bump ar71xx to v4.14.
This is
Hi All,
Regarding bumping ar71xx to 4.14, from my point of view all known issues
seem to be fixed.
Therefore, I'm planning to actually make 4.14 the default for this
target mid next week.
If you still have issues which would not allow this, please let me know
asap. (and provide a log of the
On 2018-10-15 16:20, Nick wrote:
Hi,
did someone manage to follow the Readme.md?
I got several problems when compiling juci in Xubuntu 18.04.
First where was a Regex mismatch.
And then npm makes trouble.
Now there is a new issue:
touch
/home/user/openwrt_juci/staging_dir/target-x86_64_musl-1.
t releases.
Support can be gracefully ended when a new release-branch is created.
Signed-off-by: Koen Vandeputte
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.14.77&id=577b4eb23811dfc8e38924dc476dbc866be74253
[2] https://lore.kernel.org/patchwor
On 20.10.18 17:46, Hauke Mehrtens wrote:
On 10/18/2018 02:28 PM, Koen Vandeputte wrote:
starting from upstream commit 577b4eb23811 ("ubi: Reject MLC NAND")
it is not allowed to use UBI and UBIFS on a MLC flavoured NAND flash chip. [1]
According to David Oberhollenzer [2]:
The re
On 22.10.18 19:27, Christian Lamparter wrote:
On Monday, October 22, 2018 3:48:29 PM CEST Koen Vandeputte wrote:
On 20.10.18 17:46, Hauke Mehrtens wrote:
On 10/18/2018 02:28 PM, Koen Vandeputte wrote:
starting from upstream commit 577b4eb23811 ("ubi: Reject MLC NAND")
it is not
On 23.10.18 14:56, w...@reboot.ch wrote:
Hi, wondering why ar71xx snapshots are stuck at October 9
https://downloads.openwrt.org/snapshots/targets/ar71xx/generic/
Thank you!
- will
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http
On 20.10.18 20:26, Rosen Penev wrote:
Moved the config option to the proper location.
Signed-off-by: Rosen Penev
---
target/linux/mvebu/config-4.14 | 1 +
target/linux/mvebu/cortexa9/config-default | 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
delete mode 100644 targ
On 23.10.18 17:43, Christian Lamparter wrote:
Sorry, hit "Send" by accident
On Tuesday, October 23, 2018 2:37:16 PM CEST Koen Vandeputte wrote:
On 22.10.18 19:27, Christian Lamparter wrote:
On Monday, October 22, 2018 3:48:29 PM CEST Koen Vandeputte wrote:
On 20.10.18 17:46, Hauk
Hi All,
As most of you know, ar71xx bumped to 4.14 which caused a slight kernel
oversize for some targets.
I crafted some patches to address this, but it requires testing.
As I don't have any of these devices locally, I would like to request
for some testing on any of the following devices:
On 25.10.18 23:43, Christian Lamparter wrote:
On Thursday, October 25, 2018 10:57:48 AM CEST Koen Vandeputte wrote:
On 23.10.18 17:43, Christian Lamparter wrote:
Sorry, hit "Send" by accident
On Tuesday, October 23, 2018 2:37:16 PM CEST Koen Vandeputte wrote:
On 22.10.18 19:27,
On 26.10.18 10:50, Koen Vandeputte wrote:
On 25.10.18 23:43, Christian Lamparter wrote:
On Thursday, October 25, 2018 10:57:48 AM CEST Koen Vandeputte wrote:
On 23.10.18 17:43, Christian Lamparter wrote:
Sorry, hit "Send" by accident
On Tuesday, October 23, 2018 2:37:16 PM
Tested on cns3xxx, imx6, ar71xx, x86_64 (armv6k/mpcore, armv7, mips r2,
x86_64)
All ok
Tested-by: Koen Vandeputte
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Other than that:
Tested-by: Koen Vandeputte
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
done & verified.
Thanks Ben!
Koen
On 03.02.19 04:27, Ben Greear wrote:
Here are the sha-sums, the 002 version changes to 003.
If someone could update openwrt to use them I'd appreciate it. Changelog
is at the bottom. I am hoping this resolves the crashes related to
rate-ctrl.
9980
6685623e
On 24.02.19 21:32, Joe Ayers wrote:
First of all, thanks for contributing this fix. I've incorporated
into the http://www.arednmesh.org project, just getting into our
nightly builds now. A comment and a couple questions...
The MAX_DELAY was way too short for our community, had to increase
On 25.02.19 17:33, Joe Ayers wrote:
On Mon, Feb 25, 2019 at 1:56 AM Lorenzo Bianconi
wrote:
On 24.02.19 21:32, Joe Ayers wrote:
Hi Joe,
Hi Joe,
First of all, thanks for contributing this fix. I've incorporated
into the http://www.arednmesh.org project, just getting into our
nightly build
On 26.02.19 06:28, Joe Ayers wrote:
On Mon, Feb 25, 2019 at 8:42 AM Koen Vandeputte
wrote:
On 25.02.19 17:33, Joe Ayers wrote:
On Mon, Feb 25, 2019 at 1:56 AM Lorenzo Bianconi
wrote:
On 24.02.19 21:32, Joe Ayers wrote:
Hi Joe,
Hi Joe,
First of all, thanks for contributing this fix
1)
Your file shows awk is missing.
I would recommend adding it, as it's a common tool used by many scripts
this can cause nasty side effects.
2)
Which target device is this?
Some targets with small flash build the kernel for size iso speed by
default.
If you target is such one, you can run "
Refreshed all patches
Added new ARM64 symbol: ARM64_ERRATUM_1024718
Compile-tested on: ar71xx
Runtime-tested on: ar71xx
Signed-off-by: Koen Vandeputte
---
V2:
-> Added new arm64 symbol
-> rebased on latest master commit ("wireguard: bump to 20180514")
include/k
On 2018-05-17 15:46, Koen Vandeputte wrote:
On 2018-05-17 14:22, Tomasz Maciej Nowak wrote:
W dniu 16.05.2018 o 13:36, Koen Vandeputte pisze:
Refreshed all patches
Dropped upstreamed patches:
522-PCI-aardvark-fix-logic-in-PCI-configuration-read-write-functions.patch
523-PCI-aardvark
Hi Ben,
I'm trying to build todays OpenWrt master with following options:
- ath10k-ct
- qca988x-ct-htt
When disabling this option (CONFIG_PACKAGE_MAC80211_DEBUGFS), I'm
getting the build errors below.
Is it *really* required to have this enabled for the driver to function
properly?
Is ther
Refreshed all patches
Compile-tested on: cns3xxx, imx6, x86_64
Runtime-tested on: cns3xxx, imx6, x86_64
Signed-off-by: Koen Vandeputte
---
Contains an important fix for UDP sockets! ("udp: fix SO_BINDTODEVICE")
include/kernel-version.mk| 4 ++--
..
1 - 100 of 224 matches
Mail list logo
