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 +
package/kernel/mac80211/files/lib/wif
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 dua
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
-
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
Hey Rafał,
Rafał Miłecki writes:
> + char ld_preload[64] = {}; /* Has to be big enough for all cases */
...
> + if (ld_preload[0])
> + strcat(ld_preload, ":");
> + strcat(ld_preload, "/lib/libpreload-seccomp.so");
I understand C is often like that
Hi,
ldy647 writes:
> recently, when we install our wireless router, we found when we run
> the reboot command, the board couldn't restart. We hope you could lend
> us a hand to solve this problem. We'll be quite grateful for what you
> do for us.
Apparently MT7620 can't handle 4 byte addressing
Hi John,
John Crispin writes:
> looks good to me but i will run this past linux-mtd and ask them for an
> opinion before merging it.
This patch was meant as a quick "hack" rather than a complete solution,
that's why I didn't bother adding proper commit message, S-o-b etc. But
since I'm the autho
Arjen de Korte writes:
> Citeren Paul Fertser :
>> Another is
>> that such a patch is mostly a bad substitute for proper hardware design.
>
> Not really. There may not be a hardware reset line if the flash is
> running in x4 data mode.
Imagine there's a bug in the
rsion they ship
with the device, damn them).
Signed-off-by: Paul Fertser
---
target/linux/ar71xx/base-files/etc/diag.sh | 3 +
.../ar71xx/base-files/etc/uci-defaults/01_leds | 6 +
target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 +
.../ar71xx/base-files/lib/upgrade/platfo
When a package links to a shared library that depends on libiconv or
libintl shared libraries, specifying directory pathes to them via -L
switches is not enough, see "man 1 ld" -rpath-link description.
Signed-off-by: Paul Fertser
---
include/nls.mk | 4 ++--
1 file changed, 2 insert
rsion they ship
with the device, damn them).
Signed-off-by: Paul Fertser
---
v2: register USB platform devices as there exists an unpopulated HS
USB header easily accessible on board
target/linux/ar71xx/base-files/etc/diag.sh | 3 +
.../ar71xx/base-files/etc/uci-defaults/01_leds
rsion they ship
with the device, damn them).
Signed-off-by: Paul Fertser
---
v3: refreshed kernel patches
v2: register USB platform devices as there exists an unpopulated HS
USB header easily accessible on board
target/linux/ar71xx/base-files/etc/diag.sh | 3 +
.../ar71xx/base-files/et
Hey folks,
Bastian Bittorf writes:
> * John Crispin [11.03.2016 06:27]:
>> depends on what you want to do. i dont really see anything that cannot
>> be handled using shell. what exactly do you want to write in python ?
>
> also in general i think it's a good idea to have
> less dependency than m
On Fri, Mar 11, 2016 at 08:37:31PM +1000, Jason Wu wrote:
> >>As a sidenote, POSIX shell doesn't support associative arrays (which
> >>were mentioned in this thread), so it's probably worth clarifying
> >>whether it's ok to require bash >= 4 for OpenWrt build scripts or not.
> >>
> >
> >what exactl
Hello Alexey,
Alexey Brodkin writes:
> In commit
> http://git.openwrt.org/?p=openwrt.git;a=commit;h=3990e15258808b145226d7e95332c4708f9f9463
> I got rid of older ath9k_htc firmware in favor of newer ones.
Please see
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e904c
Hi Alexey,
On Tue, Mar 15, 2016 at 06:05:29PM +, Alexey Brodkin wrote:
> Frankly I don't see Oleksij says v1.4 could be moved on top of v1.3
> file (I mean older file will be replaced).
Yes, he didn't mention it in his commit message but he clarified that
to me in private talk.
> (but first
Weedy writes:
> $ openssl dgst -sha256 ubcd535.iso | awk '/^SHA256/ {
> gsub(/^SHA256\(/,"",$1); gsub(/\)\=/,"",$1); print $2" "$1 }'
Or sed -E 's/.*\((.*)\)= (.*)/\2 \1/'
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com
__
FHS mandates presence of /var/tmp on compliant systems.
The lack of /var/tmp was discovered when using MIT Kerberos libraries
which default to that location for storing credentials cache.
Signed-off-by: Paul Fertser
---
package/base-files/files/etc/init.d/boot | 1 +
1 file changed, 1
Without this patch packages that use pkg-config to find libnl3 includes fail to
build because the path in the .pc file doesn't match actual install location.
Make it the way upstream proposes and let whomever depend on libnl use
pkg-config to find it.
Signed-off-by: Paul Fertser
---
pa
Bruno Randolf writes:
> Install header files into same location as pkgconfig/libnl-3.0.pc says:
> Cflags: -I${includedir}/libnl3
For the reference, I've sent a similar patch [1] but have forgotten to
modify the INSTALL_DIR line.
[1] http://patchwork.ozlabs.org/patch/524877/
--
Be free, use f
Hello,
Gustavo Azambuja writes:
> This adds full support for the COMFAST routers CF-WR600N, CF-E325N
> and CF-E316Nv2
Ahem,
http://git.openwrt.org/?p=openwrt.git;a=blob;f=target/linux/ar71xx/files/arch/mips/ath79/mach-cf-e316n-v2.c;h=cf3d33a55291b40d32203915237f4b27e7bdea53;hb=HEAD
And BTW, y
As a follow-up,
Gustavo Azambuja writes:
> target/linux/ar71xx/drivers.diff | 404 +
This can't be correct, right?
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com
__
Hannu Nyman writes:
> If you are really interested, check the test command from lines 39-40
> manually:
> echo 'int main(int argc, char **argv) { return 0; }' | gcc -x c -o $
> (TMP_DIR)/a.out -
Looking at "strace -f -s9 make" is often providing enough clues too.
--
Be free, use free (http:
On Tue, Nov 10, 2015 at 11:13:45AM +, Carlos Ferreira wrote:
> These lines seem to be suspicious to me. A lot of "No such file or directory".
> What can you tell from them?
Do you have a functional /bin/sh? I can't tell much from this
incomplete data you show.
--
Be free, use free (http://ww
On Tue, Nov 10, 2015 at 11:19:20AM +, Carlos Ferreira wrote:
> First of all, I fell the need to apologise for the 7MB attachment...
Yeah, that wasn't appropriate to be sent to the ML...
> I hope it can provide a little more info.
Looks like you have "hardening-wrapper" installed and it messe
Hello,
John Crispin writes:
> // is c++
>
> /* this is the c version */
Strictly speaking, // is a valid way to add one-line comments since C99.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com
__
Hey Etienne,
Etienne Champetier writes:
> i know that spawn_jail(void) is valid code, but then the clone call
> refuses to compile
That's type-safety for you. spawn_jail() is valid code too but it's not
type-safe, so AFAICT you're avoiding the errors by letting the compiler
ignore them, not by p
nment do not help as it's restricted in the same way.
With bootloader unlocked the easiest way would be to TFTP the
sysupgrade image or to sysupgrade after loading an initramfs one.
For porting the flash contents were changed externally with an SPI
programmer (after lifting Vcc flash IC pin away fr
Adrian, thank you for the review indeed.
The factory partition has a MAC that matches printed label at the
location you guessed, thanks for pointing that out.
From: Paul Fertser
Date: Tue, 13 Aug 2019 18:57:39 +0300
Subject: [PATCH v2] ramips: add support for Xiaomi Mi Wi-Fi Router 3G v2
On Tue, Aug 13, 2019 at 09:25:41PM +0300, Paul Fertser wrote:
> From: Paul Fertser
> Date: Tue, 13 Aug 2019 18:57:39 +0300
> Subject: [PATCH v2] ramips: add support for Xiaomi Mi Wi-Fi Router 3G v2
OK, I messed it up, and this is not picked up by patchwork
properly. Please excuse me
Hello Adrian,
New question surfaced, please see inline.
On Tue, Aug 13, 2019 at 07:20:57PM +0200, Adrian Schmutzler wrote:
> > +define Device/xiaomi_mir3gv2
> > + MTK_SOC := mt7621
> > + IMAGE_SIZE := 14848k
> > + DEVICE_VENDOR := Xiaomi
> > + DEVICE_MODEL := Mi router 3G v2
>
> Capitalize "
Hey Rafał!
On Thu, Aug 22, 2019 at 01:02:03PM +0200, Rafał Miłecki wrote:
> On Tue, 13 Aug 2019 at 20:25, Paul Fertser wrote:
> > diff --git a/target/linux/ramips/dts/mt7621_xiaomi_mir3g-v2.dts
> > b/target/linux/ramips/dts/mt7621_xiaomi_mir3g-v2.dts
> > new file
Thank you for the reply.
On Thu, Aug 22, 2019 at 11:18:01AM +0200, m...@adrianschmutzler.de wrote:
> to the existing configuration of the "Xiaomi Mi Router 4A Gigabit
> Edition (R4AG/R4A Gigabit)" (without adding a new device).
There's also an issue of R4AG not present in upstream and I can't see
from the PCB).
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-overwri
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
Hello Pavel,
Pavel Sayekat writes:
> My device is a rtl8676 (may be it has become old :( ) and I like to
> use openwrt firmwire on it if its possible :).
I think with some reasonable effort you should be able to get Wive-NG
running on it. It's not as great as OpenWrt but still should be on the
o
Hi,
Not strictly related to your patch, but I hope you know the answer and
that will spare me some hour(s) of digging and experimenting.
> + gpio1: gpio@660 {
> compatible = "ralink,rt5350-gpio", "ralink,rt2880-gpio";
...
> + ralink,gpio-base
Signed-off-by: Paul Fertser
---
target/linux/ramips/dts/MPRA1.dts | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/target/linux/ramips/dts/MPRA1.dts
b/target/linux/ramips/dts/MPRA1.dts
index 9b4ee34..60a23fe 100644
--- a/target/linux/ramips/dts/MPRA1.dts
+++ b/target/linux
These groups do not exist on RT5350.
Signed-off-by: Paul Fertser
---
target/linux/ramips/dts/MPRA1.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ramips/dts/MPRA1.dts
b/target/linux/ramips/dts/MPRA1.dts
index 60a23fe..08c0ab8 100644
--- a/target/linux
On Fri, Aug 08, 2014 at 06:32:15PM +0200, Álvaro Fernández Rojas wrote:
> If you also add "spi_cs1" GPIO#27 will be exposed.
> This was added on https://dev.openwrt.org/changeset/41938 for VoCore.
Yes, but it's not routed from under the SoC, unfortunately, so there's
no reason to do it.
--
Be fr
Due to TCP connections not working when VLAN is disabled, this is
needed to get failsafe functional.
Signed-off-by: Paul Fertser
---
.../lib/preinit/07_set_preinit_iface_ramips | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git
a/target/linux/ramips
On Fri, Aug 08, 2014 at 08:17:05PM +0400, Paul Fertser wrote:
> --- a/target/linux/ramips/dts/MPRA1.dts
> +++ b/target/linux/ramips/dts/MPRA1.dts
> @@ -41,12 +41,15 @@
> };
> };
> };
> +
On Sat, Aug 09, 2014 at 03:51:17PM +0200, Álvaro Fernández Rojas wrote:
> Since most RT5350 use those LEDs for ethernet and have
> them configured by the bootloader, there's no need in enabling and
> reconfiguring them on all boards.
Do you mean the current gpio driver will reconfigure them someho
Hi,
A couple of notes about your ugps NMEA daemon.
1. The usual common way to perform timezone conversion is to putenv()
TZ variable (empty if you want UTC) and call tzset(). Then it becomes
the current timezone for the process and you can do mktime() after
filling the struct with the UTC (hopefu
Hi,
Ernesto writes:
> I'd like to enter into the jtag world, and looking for a cheap usb
> adapter, like this ones:
>
> http://www.dx.com/p/avr-jtag-usb-debugging-emulator-downloader-deep-blue-312848#.U-y5hxpVHeQ
> http://www.dx.com/p/j-link-v8-arm-usb-jtag-adapter-emulator-black-149039#.U-y5jBpV
Hi,
Stefan Monnier writes:
> AFAICT OpenWRT comes with some support for the Hame MPR-A1 thingy
> (although its 16MB of RAM and 4MB of flash probably prevent it from
> being fully supported).
All the recent "2G/3G/4G WiFi routers" (both with and without batteries)
I and my friends were buying fro
Hey,
Thanks to everybody involved! Does this also solve the issue discussed
at [1] with TCP connections failing when VLAN is disabled?
[1] https://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg19870.html
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto
John Crispin writes:
> On 30/10/2014 08:49, Paul Fertser wrote:
>>
>> Thanks to everybody involved! Does this also solve the issue discussed
>> at [1] with TCP connections failing when VLAN is disabled?
>>
>> [1]
>> https://www.mail-archive.com/openwr
John Crispin writes:
>> I have RT5350 for testing (Hame MPR-A1), not MT7620/MT7530, I'm not
>> sure if the same codepath is used, but it looks like not? I will
>> probably be able to do whatever testing you need over the weekend.
>>
>
> ok, so on rt5350 tcp fails if vlans are disbaled ?
As far
Hello,
Few comments from a person that doesn't own this device (but owns an
MPR-A1 clone).
"Vittorio G (VittGam)" writes:
> - Remove unneeded VLAN now that the ethernet driver is fixed and TCP
> packets get passed correctly now. (This router only has one port.)
I've checked the OpenWrt wiki, th
Hello,
Jiri Slachta writes:
> See the statement about the transition to github:
> https://forum.openwrt.org/viewtopic.php?id=51078
What this doesn't explain is that it seems to me that every contributor
to the packages feed now needs to have an account on Github, needs to
use their proprie
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 (http://www.gnu.org/philosoph
from the PCB).
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-
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 merge
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 MAC
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
Hello dear reviewers,
On Sun, Nov 03, 2019 at 02:32:47PM +0300, Paul Fertser wrote:
> + mac: partition@3b {
> + reg = <0x3b 0x1>;
> + label = "mac";
> +
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
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 oth
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 additional c
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 inst
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
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
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; w
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 thi
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 power_a
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 be
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
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) software
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 Patchwor
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 prov
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
8.0.1 (the
old 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
lsafe" 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
ind
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 me
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
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
-December/020573.html
[1] https://github.com/openwrt/openwrt/pull/1077
[2] https://bugs.openwrt.org/index.php?do=details&task_id=2664
Signed-off-by: Paul Fertser
---
package/kernel/ath10k-ct/Makefile | 30 +++-
...0-0010-ath10k-limit-htt-rx-ring-size.patch | 22 ++
...60-
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)
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
> something
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
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, y
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
> > "01_le
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
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, or
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 co
com/freifunk-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-
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
com/freifunk-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
-
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/ima
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
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
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
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
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 not
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 th
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
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 s
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
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
> devices.
1 - 100 of 199 matches
Mail list logo
