[PATCH] Remove ccache wrappers

2023-01-20 Thread Paul Fertser
ot;ccache". [1] https://github.com/ccache/ccache/blob/master/src/ccache.cpp#L2105 [2] https://github.com/ccache/ccache/blob/master/src/Util.cpp#L802 Reported-by: Karl Palsson Signed-off-by: Paul Fertser --- I tried CONFIG_ALL=y build and fixed bad packaging where I noticed: https:

Re: [RFT 0/5] realtek: support boards similar to DGS-1210-10

2022-07-17 Thread Paul Fertser
On Sat, Jul 16, 2022 at 11:32:52PM -0300, Luiz Angelo Daros de Luca wrote: > It uses SOC := rtl8380 while all existing dgs-1210 F1 variants use > rtl8382 (except for the pending -52 variant). The commit didn't > mention why that happened. It's just cosmetic AFAICT but the datasheet clearly states

[PATCH] x86: geode: add kmod-crypto-ebc needed for hw acceleration

2022-01-21 Thread Paul Fertser
Module kmod-crypto-hw-geode provides accelerated cbc(aes) and ecb(aes) but the software implementation is also needed when AES key size isn't 128 so that the operation can fall back. Add the kmod so that it would all work as expected out of the box. Tested-by: timur_davletshin Signed-off-by: Paul

[PATCH] x86: geode: use kernel [hwrng] to provide randomness

2022-01-21 Thread Paul Fertser
s upstream as I have no idea how to estimate quality properly. Tested-by: timur_davletshin Signed-off-by: Paul Fertser --- target/linux/x86/geode/target.mk | 1 + .../960-hwrng-geode-set-quality-to-1000.patch| 12 2 files changed, 13 insertions(+) create

Re: [RFT 1/5] realtek: split DGS-1210-10P DTS

2022-01-10 Thread Paul Fertser
Hi Adrian, Thank you very much for the review of these patches, all comments make sense to me, and I would have fixed that all BUT Apparently finding even a single person to actually test this code on older revision or on similar Trendnet device is impossible so I guess the best I can do is to

Re: [PATCH v4 5/5] realtek: Remove _machine_restart and _machine_halt

2021-11-15 Thread Paul Fertser
Hello, On Sun, Nov 14, 2021 at 07:45:34PM +0100, Sander Vanheule wrote: > By dropping _machine_restart, users can provide more reliable or > device-specific restart modes. For the whole series Tested-by: Paul Fertser The tests were performed on D-Link DGS-1210-10P R1 (RTL8380), both

[RFT 4/5] realtek: support D-Link DGS-1210-10P H/W:R1

2021-10-05 Thread Paul Fertser
-d-link_dgs-1210-10p-r1-initramfs-kernel.bin > bootm * Once OpenWrt has booted reconfigure your client to use VID 100 and DHCP, scp the sysupgrade image to /tmp and run sysupgrade. [0] https://patchwork.ozlabs.org/project/openwrt/patch/20210511152243.1167160-1-j...@phrozen.org/ S

[RFT 5/5] realtek: support Trendnet TPE-082WS V1

2021-10-05 Thread Paul Fertser
According to photos and specs for Trendnet TPE-082WS V1.2R it should be the same as D-Link DGS-1210-10P R1 but with more powerful PSU (90 W) so the PoE budget is specified as 75 W. Signed-off-by: Paul Fertser --- .../realtek/base-files/etc/board.d/02_network | 3 + .../rtl8380_trendnet_tpe

[RFT 3/5] realtek: add non-PoE version of DGS-1210-10 F1

2021-10-05 Thread Paul Fertser
Signed-off-by: Paul Fertser --- .../rtl8380_d-link_dgs-1210-10-f1.dts | 8 +++ .../rtl8380_d-link_dgs-1210-10-f1.dtsi| 61 +++ .../rtl8380_d-link_dgs-1210-10p-f1.dts| 60 +- target/linux/realtek/image/Makefile | 10 ++- 4 files

[RFT 2/5] realtek: add all LEDs, buttons and SFP signals to DGS-1210-10

2021-10-05 Thread Paul Fertser
These GPIO numbers were obtained by physically inspecting a DGS-1210-10P R1 board but should be common for other devices based on same PCB layout. Signed-off-by: Paul Fertser --- .../dts-5.10/rtl8380_d-link_dgs-1210-10.dtsi | 88 +-- 1 file changed, 83 insertions(+), 5

[RFT 1/5] realtek: split DGS-1210-10P DTS

2021-10-05 Thread Paul Fertser
In preparations to add support for more similar boards the common part is split into a DTSI. The model that's currently supported is known to be revision F1 so mark it accordingly and provide appropriate compatible string for sysupgrade to work. Signed-off-by: Paul Fertser --- ...0p.dts

[RFT 0/5] realtek: support boards similar to DGS-1210-10

2021-10-05 Thread Paul Fertser
I only have D-Link DGS-1210-10P R1 for testing but other devices should be very similar judging by the photos. Would be nice to share support for all the features available rather than get just R1 fully working. Paul Fertser (5): realtek: split DGS-1210-10P DTS realtek: add all LEDs, buttons

[PATCH] realtek: do not hardcode restart handler and enable gpio-restart

2021-10-05 Thread Paul Fertser
Most boards supported by this target have a dedicated GPIO line connected to SoC's /RESET to allow full clean reliable reboot. Use regular kernel notifier methods for default restart routines to allow higher-priority handlers (such as gpio-restart) to override it. Signed-off-by: Paul Fertser

Re: [PATCH v3] realtek: ensure output drivers are enabled in RTL8231

2021-10-02 Thread Paul Fertser
t but output > > operations will have no effect. ... > > Reviewed-by: Sander Vanheule > > Signed-off-by: Paul Fertser > > I added > > Fixes: 16ae56b4f9ec ("realtek: fix RTL8231 gpio expander for high GPIOs") Even though the patch changes the code that was introduc

[PATCH v3] realtek: ensure output drivers are enabled in RTL8231

2021-10-01 Thread Paul Fertser
. pulling SoC's reset to 0) reconfigure everything as input. Reviewed-by: Sander Vanheule Signed-off-by: Paul Fertser --- Notes: Changes from v2: - Fix 5.10 as well Changes from v1: - Fix comment to mention we affect two extra GPIOs - Remove unused "v" d

[PATCH v2] realtek: ensure output drivers are enabled in RTL8231

2021-09-30 Thread Paul Fertser
. pulling SoC's reset to 0) reconfigure everything as input. Signed-off-by: Paul Fertser --- Notes: Changes from v1: - Fix comment to mention we affect two extra GPIOs - Remove unused "v" declaration. .../realtek/files-5.4/drivers/gpio/gpio-rtl8231.c| 12 +++---

[PATCH] realtek: ensure output drivers are enabled in RTL8231

2021-09-29 Thread Paul Fertser
. pulling SoC's reset to 0) reconfigure everything as input. Thanks to Sander Vanheule for telling about LED_Start. Signed-off-by: Paul Fertser --- My previous patch to this part of the code is marked Accepted in the Patchwork so this one is on top of it. Feel free to squash them together

[PATCH] dnsmasq: add explicit "set:" for client-matching options

2021-09-25 Thread Paul Fertser
Bring the usage in line with the dnsmasq man page and the other options where set: is mandatory. No functional change. Signed-off-by: Paul Fertser --- package/network/services/dnsmasq/files/dnsmasq.init | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/package

Re: [PATCH] realtek: add support for D-Link DGS-1210-10P H/W:R1

2021-09-24 Thread Paul Fertser
Hi Adrian, On Fri, Sep 24, 2021 at 11:36:39PM +0200, Adrian Schmutzler wrote: > > Subject: [PATCH] realtek: add support for D-Link DGS-1210-10P H/W:R1 > > Some mostly nitpick comments below. ... Appreciated, all noted, will take everything into account when preparing v2. Chances are we'll have

[PATCH] dnsmasq: add match_tag for --dhcp-host

2021-09-23 Thread Paul Fertser
'switch.10' list match_tag 'udhcp' option ip '192.168.25.10' Signed-off-by: Paul Fertser --- package/network/services/dnsmasq/files/dnsmasq.init | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) mode change 100644 => 100755 package/network/services/dnsmasq/fi

Re: [PATCH] realtek-poe: add support for PoE on Realtek switches

2021-09-22 Thread Paul Fertser
Hello John, Thank you for the rather useful tool. One comment below. On Tue, May 11, 2021 at 05:22:43PM +0200, John Crispin wrote: > +/* 0x17 - Set power management mode > + * 0: None (No Power Management mode) (Default in Semi-Auto mode) > + * 1: Static Power Management with Port

Re: [PATCH] realtek: fix RTL8231 gpio expander for high GPIOs

2021-09-20 Thread Paul Fertser
Hi Sander, Thank you for review, it made me think about consistency. On Mon, Sep 20, 2021 at 05:45:06PM +0200, Sander Vanheule wrote: > On Fri, 2021-09-17 at 16:11 +0300, Paul Fertser wrote: > > rtl8231_write(gpios, RTL8231_GPIO_PIN_SEL(0), 0x); > > rtl8

[PATCH v2] realtek: fix RTL8231 gpio expander for high GPIOs

2021-09-20 Thread Paul Fertser
GPIOs > 31 require special handling. This patch fixes both the initialisation and direction get/set operations. Signed-off-by: Paul Fertser --- Notes: Changes from v1: - Do not modify high GPIOs direction bits on init .../realtek/files-5.4/drivers/gpio/gpio-rtl8231.c |

[PATCH] realtek: add support for D-Link DGS-1210-10P H/W:R1

2021-09-17 Thread Paul Fertser
ed reconfigure your client to use VID 100 and DHCP, scp the sysupgrade image to /tmp and run sysupgrade. [0] https://git.openwrt.org/?p=openwrt/staging/blogic.git;a=tree;f=package/rtl83xx-poe;hb=2540faec92abf8f5e52eae0e77bfbdb47457252d Signed-off-by: Paul Fertser --- .../realtek/base-files/et

[PATCH] realtek: fix RTL8231 gpio expander for high GPIOs

2021-09-17 Thread Paul Fertser
GPIOs > 31 require special handling. This patch fixes both the initialisation (defaulting to input) and direction get/set operations. Runtime-tested on D-Link DGS-1210-10P-R1 which has "reset" button on GPIO[33]. Signed-off-by: Paul Fertser --- .../realtek/files-5.4/drivers/gpio/g

[PATCH] config/Config-images: fix unit of partition sizes

2021-06-16 Thread Paul Fertser
The code interprets these config values as Mebibytes rather than Megabytes so modify the description accordingly. Signed-off-by: Paul Fertser --- config/Config-images.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config/Config-images.in b/config/Config-images.in

[PATCH v2] ath79/nand: fix factory image generation for Netgear and Zyxel boards

2021-02-14 Thread Paul Fertser
The factory images need to embed specific IDs to pass verification with the OEM firmware (including TFTP recovery), so they need to be per-device variables. Fixes: ab1584a797 ("ath79: netgear: trim down uImage customisations") Reported-by: Marcin Juszkiewicz Signed-off-by: Paul Fertse

[PATCH] ath79/nand: fix factory image generation for Netgear boards

2021-02-11 Thread Paul Fertser
The factory images need to embed specific IDs to pass verification with the OEM firmware (including TFTP recovery), so they need to be per-device variables. Fixes: ab1584a797 ("ath79: netgear: trim down uImage customisations") Acked-By: Marcin Juszkiewicz Signed-off-by: Paul Fertser -

[PATCH v2 2/2] ipq806x: add support for TP-Link Talon AD7200

2021-01-04 Thread Paul Fertser
From: Gary Cooper Device hardware: https://deviwiki.com/wiki/TP-LINK_AD7200_(Talon) The Talon AD7200 is basically an Archer C2600 with a third PCIe lane and an 802.11ad radio. It looks like the Archers C2600/5400 but the housing is slightly larger. Specifications -- - IPQ8064

[PATCH v2 1/2] mac80211: add 802.11ad-support

2021-01-04 Thread Paul Fertser
From: Gary Cooper This adds some logic to properly populate defaults in /etc/config/wireless and support for WPA*-GCMP. TP-Link AD7200, Mikrotik WAP60g, LHGG-60ad, etc Signed-off-by: Gary Cooper --- package/base-files/files/sbin/wifi | 1 +

[PATCH v2] ath79: fix ath10k caldata extraction on some D-Link DIR-842 C3 devices

2020-10-27 Thread Paul Fertser
://forum.openwrt.org/t/d-link-dir-842-cant-access-firmware-upload-form/65454 Signed-off-by: Paul Fertser --- Changes in v2: - Separate out nec,wg1200cr section as those boards do not even have a "reserved" partition (Adrian Schmutzler) .../base-files/etc/hotplug.d/firmware/11-ath1

[PATCH] ath79: fix ath10k caldata extraction on some D-Link DIR-842 C3 devices

2020-10-27 Thread Paul Fertser
://forum.openwrt.org/t/d-link-dir-842-cant-access-firmware-upload-form/65454 Signed-off-by: Paul Fertser --- .../generic/base-files/etc/hotplug.d/firmware/11-ath10k-caldata | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/ath79/generic/base-files/etc/hotplug.d/firmware/11-ath10k

[PATCH] mac80211: fix MAC address allocations when local bit set on base addr

2020-10-16 Thread Paul Fertser
-by: Zero_Chaos Signed-off-by: Paul Fertser --- package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh b/package/kernel/mac80211/files/lib/netifd/wireless/mac80211

Re: ipq806x: add support for TP-Link Talon AD7200

2020-10-12 Thread Paul Fertser
Hey Robert, On Mon, Oct 12, 2020 at 09:52:07AM +0200, Robert Marko wrote: > Paul, where did you get the 802.11ad support code for OpenWrt? I just forwarded Gary's commit to the mailing list as somehow the subscription confirmation mail doesn't get through to him. That said, the commit doesn't

ipq806x: add support for TP-Link Talon AD7200

2020-10-11 Thread Paul Fertser
From: Gary Cooper Device hardware: https://deviwiki.com/wiki/TP-LINK_AD7200_(Talon) The Talon AD7200 is basically an Archer C2600 with larger flash, a third PCIe lane and an 802.11ad radio. It comes in a different housing reminiscent of the Archers C3200 and C5400. Specifications

Re: [OpenWrt-Devel] Build error on latest trunk: meson, python, zstd

2020-06-09 Thread Paul Fertser
Hello, On Tue, Jun 09, 2020 at 11:11:06AM +0200, Reiner Karlsberg wrote: > ['/etc/openwrt/WE826/staging_dir/host/bin/python']> is not a valid python or > it is missing setuptools OpenWrt build system checks for Python3 presence in the prereq stage but it doesn't check if it has setuptools

Re: [OpenWrt-Devel] [PATCH] base-files: add list-enabled/disabled to service function in /etc/profile

2020-06-04 Thread Paul Fertser
On Thu, Jun 04, 2020 at 06:31:36AM -0700, Stan Grishin wrote: > Thanks. Should I replace list-enabled and list-disabled with list, doing this: I'm not sure it's anywhere close to the optimal solution with ubus and jsonfilter, but I'm not well-versed in the area enough to suggest a proper one,

Re: [OpenWrt-Devel] [PATCH] base-files: add list-enabled/disabled to service function in /etc/profile

2020-06-04 Thread Paul Fertser
On Thu, Jun 04, 2020 at 02:56:31AM -0700, Stan Grishin wrote: > If there's a one/two liner to figure out if a service is running or > not, ubus call service list '{ "verbose": true, "name": "openvpn" }' | \ jsonfilter -e '@.openvpn.instances["foo"].running -- Be free, use free

Re: [OpenWrt-Devel] [PATCH v2] wireguard-tools: fix version indicator

2020-05-11 Thread Paul Fertser
On Mon, May 11, 2020 at 05:43:56PM +0300, Paul Fertser wrote: > Probably the right way to solve this would be to have means to > override the default git describe behaviour (and force specific > version string instead) by a configure (or similar) flag. Another (probably sick) idea: afte

Re: [OpenWrt-Devel] [PATCH v2] wireguard-tools: fix version indicator

2020-05-11 Thread Paul Fertser
Hello, I'm not talking about this specific patch but rather about the general problem I'm aware of, in this specific case it might be not applicable. On Mon, May 11, 2020 at 04:25:42PM +0200, Petr Štetiar wrote: > > If we execute `wg --version` we get a diffrent version string that does > > not

[OpenWrt-Devel] Booting boards with UART attached (was: Re: [PATCH] ramips: mt7621: use lzma-loader for D-Link DIR-860L B1)

2020-04-20 Thread Paul Fertser
Hello, On Mon, Apr 20, 2020 at 11:01:46AM +0200, Szabolcs Hubai wrote: > I have a CP2102 USB to TTL module, and used with "minicom -D /dev/ttyUSB0". > > > Intereestingly, when I connected with serial to the router it was > sometime unstable: > * refuse to start > * freeze at boot soon after:

Re: [OpenWrt-Devel] [PATCH] om-watchdog: Add support for GL-X1200 (GL.iNet)

2020-04-11 Thread Paul Fertser
Hi, On Fri, Apr 10, 2020 at 07:23:44PM +0800, guilin.wang wrote: > now the external single-chip cannot detect the level change of GPIO How often do you really need to feed the watchdog? Why do you have an additional MCU taking care of capturing the level change, what else is it doing? Can this

Re: [OpenWrt-Devel] [PATCH] om-watchdog: Add support for GL-X1200 (GL.iNet)

2020-04-10 Thread Paul Fertser
Hi, On Fri, Apr 10, 2020 at 06:55:59PM +0800, guilin.wang wrote: > but found that the dog could not be fed successfully. Why exactly? > Our external microcontroller feeds the dog. The cpu just gives the > microcontroller a trigger signal, but I tested that the > microcontroller cannot detect

Re: [OpenWrt-Devel] [PATCH] generic: spi-nor: rework broken-flash-reset

2020-04-08 Thread Paul Fertser
Hello, On Mon, Apr 06, 2020 at 07:44:28PM +0800, Chuanhong Guo wrote: > Instead of resetting flash to 3B address on remove hook, this > implementation only enters 4B mode when needed, which prevents more > unexpected reboot stuck. Probably a naive question, but does this have any measurable

Re: [OpenWrt-Devel] Openwrt TpLink Archer D2

2020-04-06 Thread Paul Fertser
Hello, On Mon, Apr 06, 2020 at 07:05:44PM +0200, Martin Heck via openwrt-devel wrote: > i have a Tp Link Archer D2 Router This page https://openwrt.org/toh/tp-link/archer_d2_ac750 tells me it has 64 MiB RAM. > DDR size from 0xa000 - 0xa3ff This confirms the size. > DRAM:  64 MiB And

Re: [OpenWrt-Devel] [PATCH v1] umdns: suppress address-of-packed-member warning

2020-04-04 Thread Paul Fertser
Hello, On Sat, Apr 04, 2020 at 09:27:34AM +0100, Kevin Darbyshire-Bryant wrote: > dns.c:261:2: error: converting a packed ‘struct dns_question’ pointer > (alignment 1) to a ‘uint16_t’ {aka ‘short unsigned int’} pointer > (alignment 2) may result in an unaligned pointer value >

Re: [OpenWrt-Devel] How can I include strace into the firmware?

2020-03-24 Thread Paul Fertser
On Tue, Mar 24, 2020 at 08:08:08PM +0900, Jeonghum Joh wrote: > Do you have some suggestion for me? opkg update before trying to install -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___

Re: [OpenWrt-Devel] How can I include strace into the firmware?

2020-03-24 Thread Paul Fertser
Hello, On Tue, Mar 24, 2020 at 07:39:05PM +0900, Jeonghum Joh wrote: > I'd like to use "strace" in openwrt firmware. Just install "strace" package, it's in base. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com

Re: [OpenWrt-Devel] [PATCH] ath79: move lzma-loader to the end of available RAM

2020-01-21 Thread Paul Fertser
Hi, On Tue, Jan 21, 2020 at 10:48:28PM +0100, m...@adrianschmutzler.de wrote: > I can't tell you why overwrite works this direction without further > research though. "If a variable has been set with a command argument (*note Overriding Variables: Overriding.), then ordinary assignments in the

[OpenWrt-Devel] Replying to old mails (Was: Re: [OpenWrt-Devel, v5, 2/2] Allow sysupgrade restore on ER)

2020-01-03 Thread Paul Fertser
Hi, Somewhat related, On Fri, Jan 03, 2020 at 01:34:43PM +0100, m...@adrianschmutzler.de wrote: > I do not have the old e-mails for those changes, thus I cannot respond > correctly. One can do wget http://lists.infradead.org/mailman/private/openwrt-devel.mbox/openwrt-devel.mbox?username=\=

Re: [OpenWrt-Devel] Preserving configs over sysupgrade on ath79/tiny broken for some boards (on 19.07 and master), possible solutions

2019-12-31 Thread Paul Fertser
Hello David, On Tue, Dec 31, 2019 at 04:20:29PM +0100, David Bauer wrote: > > If no users speak up probably it's better to remove all the support > > code altogether to avoid wasting maintainers' time on it? > > The code is not really an issue, as there's not much code dedicated for 4M >

Re: [OpenWrt-Devel] Preserving configs over sysupgrade on ath79/tiny broken for some boards (on 19.07 and master), possible solutions

2019-12-31 Thread Paul Fertser
Hello gents, On Mon, Dec 30, 2019 at 02:41:12PM +0100, Piotr Dymacz wrote: > > On 12/30/19 12:42 PM, Jo-Philipp Wich wrote: > > > Hi, > > > > > > given that (binary release) support for 4MB devices will end with 19.07, > > > I'd vote for reverting the 4K sector change in ath79 and stick with 64K

[OpenWrt-Devel] Preserving configs over sysupgrade on ath79/tiny broken for some boards (on 19.07 and master), possible solutions

2019-12-28 Thread Paul Fertser
Hi, Status quo summary: Many ath79/tiny devices will lose configs (almost) each time sysupgrading. This is easy to fix for most of the boards that consistently have compatible flash memory ICs (some TP-Links are not elements of this set). The only easy fix for all the boards is to revert the 4K

[OpenWrt-Devel] [PATCH v2] ath79: tp-link: use ath10k-ct-smallbuffers for 64 MiB devices

2019-12-24 Thread Paul Fertser
Signed-off-by: Paul Fertser --- target/linux/ath79/image/generic-tp-link.mk | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/target/linux/ath79/image/generic-tp-link.mk b/target/linux/ath79/image/generic-tp-link.mk index 8a030492c5..97c4bb9441 100644 --- a/target

Re: [OpenWrt-Devel] [PATCH] ath79: tp-link: use ath10k-ct-smallbuffers for 64 MiB devices

2019-12-24 Thread Paul Fertser
On Tue, Dec 24, 2019 at 09:27:21PM +0100, Lech Perczak wrote: > > On Tue, Dec 24, 2019 at 08:26:09PM +0100, Lech Perczak wrote: > > > I think that TL-WR902AC v1 should be included as well, as it is 64M device > > > and I also experienced issues with ath10k-ct on it while porting. > > Device like

Re: [OpenWrt-Devel] [PATCH] use strncpy instead of strcpy

2019-12-24 Thread Paul Fertser
Hi, On Tue, Dec 24, 2019 at 10:02:13AM -0800, Khem Raj wrote: > + hdr->name[strlen((char*)hdr->name)] = '\0'; > + strncpy((char *) hdr->name, (const char *)name, > strlen((char*)hdr->name)); strlen((char*)hdr->name) doesn't seem to be meaningful in this context, are you sure you were

[OpenWrt-Devel] [PATCH] ipq40xx: use ath10k-ct-smallbuffers for 128 MiB devices

2019-12-24 Thread Paul Fertser
Signed-off-by: Paul Fertser --- target/linux/ipq40xx/image/Makefile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/target/linux/ipq40xx/image/Makefile b/target/linux/ipq40xx/image/Makefile index fada35a49d..1fe563c7a5 100644 --- a/target/linux/ipq40xx/image/Makefile

[OpenWrt-Devel] [PATCH] ath79: tp-link: use ath10k-ct-smallbuffers for 64 MiB devices

2019-12-24 Thread Paul Fertser
Signed-off-by: Paul Fertser --- target/linux/ath79/image/generic-tp-link.mk | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/target/linux/ath79/image/generic-tp-link.mk b/target/linux/ath79/image/generic-tp-link.mk index 8a030492c5..f4e16e6e43 100644 --- a/target/linux

[OpenWrt-Devel] [PATCH for-19.07] ath79: use ath10k-ct-smallbuffers for 64 MiB devices

2019-12-24 Thread Paul Fertser
Signed-off-by: Paul Fertser --- target/linux/ath79/image/generic-tp-link.mk | 14 +++--- target/linux/ath79/image/generic-ubnt.mk| 8 target/linux/ath79/image/generic.mk | 6 +++--- 3 files changed, 14 insertions(+), 14 deletions(-) diff --git a/target/linux/ath79

Re: [OpenWrt-Devel] [PATCH v3] kernel: ath10k-ct: provide a build variant for small RAM devices

2019-12-23 Thread Paul Fertser
Hi Bjørn, On Mon, Dec 23, 2019 at 10:17:11AM +0100, Bjørn Mork wrote: > Paul Fertser writes: > > --- /dev/null > > +++ > > b/package/kernel/ath10k-ct/patches/960-0011-ath10k-limit-pci-buffer-size.patch > > @@ -0,0 +1,100 @@ > > +--- a/ath10k-4.19/p

[OpenWrt-Devel] [PATCH] ath79: use ath10k-ct-smallbuffers for 64 MiB devices

2019-12-22 Thread Paul Fertser
Signed-off-by: Paul Fertser --- These should be all the affected ath79 devices. There're also some in ipq40xx and ipq806x. And, of course, plenty in ar71xx, not sure if it's worth caring about those. target/linux/ath79/image/generic-tp-link.mk | 10 +- target/linux/ath79/image/generic

[OpenWrt-Devel] [PATCH v3] kernel: ath10k-ct: provide a build variant for small RAM devices

2019-12-22 Thread Paul Fertser
unk-gluon/gluon/pull/1440#issue-195607701 Signed-off-by: Paul Fertser --- This is compile-tested only! Changes for v3: - Apply all patches to both build variants, select by a preprocessor symbol Changes for v2: - Added performance impact details to the commit message - Fix

[OpenWrt-Devel] [PATCH] ubox: print an error when no kernel module dir can be found

2019-12-18 Thread Paul Fertser
Do not just silently fail when kernel modules are nowhere to be found. This is essential for diagnosing mismatched kernel version failures. Signed-off-by: Paul Fertser --- kmodloader.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/kmodloader.c b/kmodloader.c index

[OpenWrt-Devel] [PATCH v2] kernel: ath10k-ct: provide a build variant for small RAM devices

2019-12-15 Thread Paul Fertser
unk-gluon/gluon/pull/1440#issue-195607701 Signed-off-by: Paul Fertser --- Changes for v2: - Added performance impact details to the commit message - Fixed QUILT=1 operation - Refreshed the new patches package/kernel/ath10k-ct/Makefile | 30 +++- ...0-0010-ath1

Re: [OpenWrt-Devel] [PATCH] kernel: ath10k-ct: provide a build variant for small RAM devices

2019-12-15 Thread Paul Fertser
On Sun, Dec 15, 2019 at 12:00:48PM +0100, Christian Lamparter wrote: > From what I remember Sven Eckelmann also measured the impact from the > patches on the performance and posted his results to the OpenWrt ML > (google will find them). https://github.com/freifunk-gluon/gluon/pull/1440 is what

Re: [OpenWrt-Devel] [PATCH] kernel: ath10k-ct: provide a build variant for small RAM devices

2019-12-15 Thread Paul Fertser
Thank you for the answer Christian, On Sun, Dec 15, 2019 at 12:00:48PM +0100, Christian Lamparter wrote: > I think for this to have any chance of moving forward you'll need to > pressure your ODMs and if that doesn't work: Go with a different WIFI > chip vendor that supports low memory devices,

Re: [OpenWrt-Devel] LEDs in system UCI config (was: Re: [PATCH 19.07] ath79: add support for gl-ar750)

2019-12-14 Thread Paul Fertser
On Sat, Dec 14, 2019 at 02:12:55PM +0300, Paul Fertser wrote: > Should a uci-defaults script be added to base-files that would > populate the system config with all the LEDs present in the DT but not > added by board config? cd /sys/class/leds for i in *; do uci show system

[OpenWrt-Devel] LEDs in system UCI config (was: Re: [PATCH 19.07] ath79: add support for gl-ar750)

2019-12-14 Thread Paul Fertser
Hello, Some follow-up thoughts, could someone clarify please? On Sat, Dec 14, 2019 at 02:10:28AM +0300, Paul Fertser wrote: > On Fri, Dec 13, 2019 at 11:51:14PM +0100, Sven Roederer wrote: > > good point. But also on master seems to be no entry for this board in > > "0

Re: [OpenWrt-Devel] [PATCH 19.07] ath79: add support for gl-ar750

2019-12-13 Thread Paul Fertser
Hey Sven, On Fri, Dec 13, 2019 at 11:51:14PM +0100, Sven Roederer wrote: > good point. But also on master seems to be no entry for this board in > "01_leds". So I assume the default case fits for it. I looked several times through the config and was unable to see the default case. Apparently,

Re: [OpenWrt-Devel] [PATCH 19.07] ath79: add support for gl-ar750

2019-12-13 Thread Paul Fertser
Hello, On Fri, Dec 13, 2019 at 08:50:46PM +0100, Sven Roederer wrote: > .../ath79/base-files/etc/board.d/02_network | 5 + > .../etc/hotplug.d/firmware/11-ath10k-caldata | 1 + > .../ath79/dts/qca9531_glinet_gl-ar750.dts | 142 ++ > target/linux/ath79/image/generic.mk

Re: [OpenWrt-Devel] [PATCH] kernel: ath10k-ct: provide a build variant for small RAM devices

2019-12-11 Thread Paul Fertser
Hey Ben, On Wed, Dec 11, 2019 at 10:06:26AM -0800, Ben Greear wrote: > On 12/11/19 6:44 AM, Paul Fertser wrote: > > According to many bugreports [0][1][2] the default ath10k-ct kernel ... > And also if you want to just have the makefile pass a -DBUILD_ATH10K_SMALL or > s

Re: [OpenWrt-Devel] [PATCH] kernel: ath10k-ct: provide a build variant for small RAM devices

2019-12-11 Thread Paul Fertser
On Wed, Dec 11, 2019 at 05:44:59PM +0300, Paul Fertser wrote: > +define Build/Patch > + $(if $(QUILT),rm -rf $(PKG_BUILD_DIR)/patches; mkdir -p > $(PKG_BUILD_DIR)/patches) > + $(call PatchDir,$(PKG_BUILD_DIR),$(PATCH_DIR),) > +ifeq ($(BUILD_VARIANT),smallbuffers)

[OpenWrt-Devel] [PATCH] kernel: ath10k-ct: provide a build variant for small RAM devices

2019-12-11 Thread Paul Fertser
-December/020573.html [1] https://github.com/openwrt/openwrt/pull/1077 [2] https://bugs.openwrt.org/index.php?do=details_id=2664 Signed-off-by: Paul Fertser --- package/kernel/ath10k-ct/Makefile | 30 +++- ...0-0010-ath10k-limit-htt-rx-ring-size.patch | 22 ++ ...60-0011-ath10k

Re: [OpenWrt-Devel] [RFC][PATCH] base-files: send informational UDP message each second waiting

2019-12-11 Thread Paul Fertser
On Wed, Dec 11, 2019 at 12:47:22PM +0100, Petr Štetiar wrote: > Paul Fertser [2019-12-11 14:03:53]: > > Waiting with a timeout poses a question of what that timeout should be set > > to; and if that's reasonable to extend current 2 seconds with any > > significant amount. >

Re: [OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615 rev. E4

2019-12-11 Thread Paul Fertser
Hello Lars, On Fri, Nov 08, 2019 at 03:12:02PM +0700, Lars Melin wrote: > On 11/8/2019 14:50, Paul Fertser wrote: > > From working with uIP before on an embedded target I know that it > > doesn't support delayed ACKs in any form, for any packet it sends it > > waits for

Re: [OpenWrt-Devel] [RFC][PATCH] base-files: send informational UDP message each second waiting

2019-12-11 Thread Paul Fertser
Hi, On Tue, Dec 10, 2019 at 03:42:13PM +0100, Petr Štetiar wrote: > Paul Fertser [2019-12-10 17:24:20]: > > in cases when the interface is brought up faster it leads to two messages > > in cases when the interface is brought up slower it leads to no message. > > To

[OpenWrt-Devel] [RFC][PATCH] base-files: send informational UDP message each second waiting

2019-12-10 Thread Paul Fertser
" documentation. Signed-off-by: Paul Fertser --- package/base-files/files/lib/preinit/30_failsafe_wait | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/package/base-files/files/lib/preinit/30_failsafe_wait b/package/base-files/files/lib/preinit/30_failsafe_wait index dd

[OpenWrt-Devel] [PATCH v3] ath79: add D-Link DIR-615 E4

2019-12-10 Thread Paul Fertser
d uIP TCP/IP protocol stack is not compatible with modern Linux, the kernel, so you'll need to use some other OS to do this). Can be performed without a Web-browser too: curl http://192.168.0.1/cgi/index \ -F Send=@openwrt-ath79-tiny-dlink_dir-615-e4-squashfs-factory.bin Signed-off-by:

Re: [OpenWrt-Devel] [PATCH v2] ath79: add D-Link DIR-615 E4

2019-12-07 Thread Paul Fertser
On Sat, Dec 07, 2019 at 11:11:27PM +0100, m...@adrianschmutzler.de wrote: > Well, address the issues we have agreed on in a v3. Sure, will do tomorrow, thanks! -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com

Re: [OpenWrt-Devel] [PATCH v2] ath79: add D-Link DIR-615 E4

2019-12-07 Thread Paul Fertser
On Sat, Dec 07, 2019 at 09:58:26PM +0100, Petr Štetiar wrote: > > I'll be happy to change the patch in any way that will get it accepted. > > Then just do the requested changes in v3, solved. I got an impression Adrian is not sure anymore he's requesting all the changes we talked about, as I

Re: [OpenWrt-Devel] [PATCH v2] ath79: add D-Link DIR-615 E4

2019-12-07 Thread Paul Fertser
Hi Petr, On Sat, Dec 07, 2019 at 04:04:13PM +0100, Petr Štetiar wrote: > > You changed the status of the patch to "Changes requested" but you > > I've marked it as such, because of that discussion[1], but I admit, that I > didn't read it thoroughly. One thing I find a bit annoying about

Re: [OpenWrt-Devel] [PATCH v2] ath79: add D-Link DIR-615 E4

2019-12-07 Thread Paul Fertser
Hello dear maintainer, You changed the status of the patch to "Changes requested" but you haven't expressed your opinion on the topics raised during the discussion. Please do so that I can make the changes to your liking. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html)

[OpenWrt-Devel] [RFC][PATCH] ath79-tiny: enable 4k sectors

2019-11-26 Thread Paul Fertser
without this feature will likely not allow to preserve configs automatically but since ath79 is considered to be in a "technology preview" state it shouldn't be a problem. Signed-off-by: Paul Fertser --- target/linux/ath79/tiny/config-default | 1 + 1 file changed, 1 insertion(+) diff --gi

Re: [OpenWrt-Devel] [PATCH v2] ath79: add D-Link DIR-615 E4

2019-11-11 Thread Paul Fertser
On Mon, Nov 11, 2019 at 01:53:10PM +0100, Adrian Schmutzler wrote: > > I've made specific effort to flash vendor firmware and confirmed by > > testing on hardware that the vendor firmware doesn't need those > > partitions. Isn't that enough? What important aspects did I not check? > > I haven't

Re: [OpenWrt-Devel] [PATCH v2] ath79: add D-Link DIR-615 E4

2019-11-11 Thread Paul Fertser
Hello Adrian, Thank you very much for the review. On Mon, Nov 11, 2019 at 12:12:47PM +0100, Adrian Schmutzler wrote: > > + power_green: power_green { > > As stated above, change the _label_ to include a "led_" prefix, so > this becomes "led_power_green: power_green {". Same for

[OpenWrt-Devel] 4K sectors on ath79-tiny

2019-11-09 Thread Paul Fertser
Hello, What is the reason for not enabling 4K erase sectors for the 4M devices in ath79 target? jffs2 needs minimum 5 erase blocks so for those space-constrained devices this option seems to be really useful (to be able to keep configs when the space gets tight). However please note that if

[OpenWrt-Devel] [PATCH v2] ath79: add D-Link DIR-615 E4

2019-11-09 Thread Paul Fertser
rsion:" field in the web interface page header (one can append "mac" partition contents to the vendor firmware dump prior to flashing if that's too worrying). Signed-off-by: Paul Fertser --- Changes for v2: - Remove "rev." from board name - Use a single DTS file

Re: [OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615 rev. E4

2019-11-08 Thread Paul Fertser
On Fri, Nov 08, 2019 at 07:41:33PM +0300, Paul Fertser wrote: > "lp" might be a "language pack" which is to be downloaded and > flashed separately when using vendor firmware. One forum post[1] says that the only language pack the person was able to ever find for this

Re: [OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615 rev. E4

2019-11-08 Thread Paul Fertser
Hi Adrian, On Fri, Nov 08, 2019 at 03:53:59PM +0100, Adrian Schmutzler wrote: > > With that I have 6 eraseblocks left for the rootfs_data partition (5 > > is the absolute minimum jffs2 allows). > > > > > Be aware that you might not find someone willing to merge this. > > > > I do not think this

Re: [OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615 rev. E4

2019-11-07 Thread Paul Fertser
On Thu, Nov 07, 2019 at 08:19:27AM +0300, Paul Fertser wrote: > I see there's some http server mentioned in the wiki article, haven't > tried it yet (and I can't understand what "simple" web browser it > talks about, probably there should be a curl command instead?),

Re: [OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615 rev. E4

2019-11-06 Thread Paul Fertser
Hello Thomas, On Wed, Nov 06, 2019 at 11:31:23PM +0100, tm...@gmx.de wrote: > > Support ported from ar71xx. > > > > Signed-off-by: Paul Fertser > > [...] > > Can you please add installation instructions? Please notice that this patch is WiP and some additiona

Re: [OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615 rev. E4

2019-11-04 Thread Paul Fertser
On Mon, Nov 04, 2019 at 05:16:15PM +0100, Adrian Schmutzler wrote: > > + power_green: power_green { > > + label = "d-link:green:power"; > > It's policy to use boardname instead of "d-link" here, except for tplink as > far as I know. But in this case there're three

Re: [OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615 rev. E4

2019-11-04 Thread Paul Fertser
Hello, Thank you for the review indeed! On Mon, Nov 04, 2019 at 05:16:15PM +0100, Adrian Schmutzler wrote: > > + power_green: power_green { > > + label = "d-link:green:power"; > > It's policy to use boardname instead of "d-link" here, except for tplink as > far as I

Re: [OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615 rev. E4

2019-11-03 Thread Paul Fertser
Hello dear reviewers, On Sun, Nov 03, 2019 at 02:32:47PM +0300, Paul Fertser wrote: > + mac: partition@3b { > + reg = <0x3b 0x1>; > + label = "mac"; > +

[OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615 rev. E4

2019-11-03 Thread Paul Fertser
Support ported from ar71xx. Signed-off-by: Paul Fertser --- .../ath79/dts/ar7240_dlink_dir-600-a1.dtsi| 173 ++ .../ath79/dts/ar7240_dlink_dir-615-e4.dts | 19 ++ target/linux/ath79/image/tiny.mk | 16 ++ .../ath79/tiny/base-files/etc/board.d/01_leds | 7

Re: [OpenWrt-Devel] [PATCH v3] ramips: add support for Xiaomi Mi Wi-Fi Router 3G v2

2019-10-25 Thread Paul Fertser
Hi Roger, Thank you for the review! On Fri, Oct 11, 2019 at 07:14:25PM +0200, Roger Pueyo Centelles | Guifi.net wrote: > + xiaomi,mir3g-v2) > + wan_mac=$(mtd_get_mac_binary factory 0xe006) > + ;; > > You may want to add "label_mac=$wan_mac" there, if the

Re: [OpenWrt-Devel] [PATCH v3] ramips: add support for Xiaomi Mi Wi-Fi Router 3G v2

2019-10-25 Thread Paul Fertser
Hi, On Sat, Aug 31, 2019 at 11:32:33PM +0200, m...@adrianschmutzler.de wrote: > > + xiaomi,mir3g-v2) > > + ucidef_add_switch "switch0" \ > > + "2:lan:2" "3:lan:1" "4:wan" "6t@eth0" > > + ;; > > "6t@eth0" and "6@eth0" should be the same, so this can be

[OpenWrt-Devel] [PATCH v4] ramips: add support for Xiaomi Mi Wi-Fi Router 3G v2

2019-10-25 Thread Paul Fertser
). Forum thread [0] indicates that this device is identical to "Xiaomi Mi Router 4A Gigabit Edition". [0] https://forum.openwrt.org/t/xiaomi-mi-router-4a-gigabit-edition-r4ag-r4a-gigabit-fully-supported-but-requires-overwriting-spi-flash-with-programmer/36685 Signed-off-by: Paul Fertse

Re: [OpenWrt-Devel] [PATCH v3] ramips: add support for Xiaomi Mi Wi-Fi Router 3G v2

2019-10-21 Thread Paul Fertser
Dear maintainers, Do you request me to make all of the changes proposed by Roger (including adding u-boot data? But the env partition is marked read-only and most other targets do not do that)? Or the merging proposed by Adrian? Please clarify! -- Be free, use free

Re: [OpenWrt-Devel] [PATCH v3] ramips: add support for Xiaomi Mi Wi-Fi Router 3G v2

2019-09-01 Thread Paul Fertser
Hi, Thank you for the reviewing. On Sat, Aug 31, 2019 at 11:32:33PM +0200, m...@adrianschmutzler.de wrote: > > + xiaomi,mir3g-v2) > > + ucidef_add_switch "switch0" \ > > + "2:lan:2" "3:lan:1" "4:wan" "6t@eth0" > > + ;; > > "6t@eth0" and "6@eth0" should be

  1   2   >