[PATCH luci] translation: add Urdu to luci.mk

[Paul Blazejowski]

make menu(old)config currently throws a warning:

...
tmp/.config-package.in:59705:warning: leading whitespace ignored
#
# No change to .config
#
...

Define ﺍﺭﺩﻭ/(Urdu) language in luci.mk.

Fixes: 4081478 ("Added translation using Weblate (Urdu)"

Signed-off-by: Paul Blazejowski 
---
 luci.mk | 1 +
 1 file changed, 1 insertion(+)

diff --git a/luci.mk b/luci.mk
index 42264c07cc..1159a8755a 100644
--- a/luci.mk
+++ b/luci.mk
@@ -50,6 +50,7 @@ LUCI_LANG.sk=Slovenčina (Slovak)
 LUCI_LANG.sv=Svenska (Swedish)
 LUCI_LANG.tr=Türkçe (Turkish)
 LUCI_LANG.uk=Українська (Ukrainian)
+LUCI_LANG.ur=اردو (Urdu)
 LUCI_LANG.vi=Tiếng Việt (Vietnamese)
 LUCI_LANG.zh_Hans=简体中文 (Chinese Simplified)
 LUCI_LANG.zh_Hant=繁體中文 (Chinese Traditional)
-- 
2.37.1


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[PATCH] hostapd: apply patch to fix building openssl variant

[Paul Blazejowski]

Add patch from:
https://patchwork.ozlabs.org/project/hostap/patch/20220622121355.1337612-1-a.hei...@gmail.com/

Fixes: dab9103 ("hostapd: update to 2022-06-02")

Signed-off-by: Paul Blazejowski 
---
 .../patches/992-openssl-include-rsa.patch | 177 ++
 1 file changed, 177 insertions(+)
 create mode 100644 
package/network/services/hostapd/patches/992-openssl-include-rsa.patch

diff --git 
a/package/network/services/hostapd/patches/992-openssl-include-rsa.patch 
b/package/network/services/hostapd/patches/992-openssl-include-rsa.patch
new file mode 100644
index 00..dccf4fa639
--- /dev/null
+++ b/package/network/services/hostapd/patches/992-openssl-include-rsa.patch
@@ -0,0 +1,177 @@
+From patchwork Wed Jun 22 12:13:55 2022
+Content-Type: text/plain; charset="utf-8"
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+X-Patchwork-Submitter: Andre Heider 
+X-Patchwork-Id: 1650717
+Return-Path: 
+ 
+X-Original-To: incom...@patchwork.ozlabs.org
+Delivered-To: patchwork-incom...@bilbo.ozlabs.org
+Authentication-Results: bilbo.ozlabs.org;
+   dkim=pass (2048-bit key;
+ secure) header.d=lists.infradead.org header.i=@lists.infradead.org
+ header.a=rsa-sha256 header.s=bombadil.20210309 header.b=lGQ5d+3r;
+   dkim=fail reason="signature verification failed" (2048-bit key;
+ unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256
+ header.s=20210112 header.b=oZEzEVkh;
+   dkim-atps=neutral
+Authentication-Results: ozlabs.org;
+ spf=none (no SPF record) smtp.mailfrom=lists.infradead.org
+ (client-ip=2607:7c80:54:3::133; helo=bombadil.infradead.org;
+ 
envelope-from=hostap-bounces+incoming=patchwork.ozlabs@lists.infradead.org;
+ receiver=)
+Received: from bombadil.infradead.org (bombadil.infradead.org
+ [IPv6:2607:7c80:54:3::133])
+   (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
+key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest
+ SHA256)
+   (No client certificate requested)
+   by bilbo.ozlabs.org (Postfix) with ESMTPS id 4LYbtd5SsXz9s09
+   for ; Thu, 30 Jun 2022 21:38:17 +1000 
(AEST)
+DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
+   d=lists.infradead.org; s=bombadil.20210309; h=Sender:
+   
Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post:
+   
List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:To
+   
:From:Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From:
+   
Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:
+   List-Owner; bh=fJOJgONq7Ju4Q8DO2ZSGDAeBzziAezJxsd/RJ0evEYA=; 
b=lGQ5d+3rmD0HXm
+   
Ozg9mP9AIal1oNDzQnahgss+OBx60Vy6MJj/ih6ehdkfsuxDgEkhhXQGqhDvuSHzarGTTsKeYbT0I
+   
anoweLH1hr1gLGtymPyCE3lV+5fr0BZPQCF2X3scgHpr9GeLIdIJyjxVo7HVUTrAUfltU7emKR/Vh
+   
U6ecBu8S+MnDI4iLPycr2zDwvl7Ow6utk1855gESBkYXcVpa1AHlZWLB0rTCk8VVkJtjhin8X+ep+
+   
1n6wrdISdWoYQ4lyrr8ECG8MNl1Bh4dXxDZ2ZWxV2CQUv9FBmJp6EA78WFYbl8Qz4ASjcLofdjPOa
+   D3ff/lHW8y1xEnP9NusA==;
+Received: from localhost ([::1] helo=bombadil.infradead.org)
+   by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux))
+   id 1o6sTt-00GsCE-1f; Thu, 30 Jun 2022 11:37:09 +
+Received: from mail-ej1-x629.google.com ([2a00:1450:4864:20::629])
+   by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux))
+   id 1o3zFC-00AJUB-6C
+   for hos...@lists.infradead.org; Wed, 22 Jun 2022 12:14:03 +
+Received: by mail-ej1-x629.google.com with SMTP id pk21so10677564ejb.2
+for ;
+ Wed, 22 Jun 2022 05:14:01 -0700 (PDT)
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+d=gmail.com; s=20210112;
+h=from:to:subject:date:message-id:mime-version
+ :content-transfer-encoding;
+bh=AMNUmfKzCqd/kswglg673XVAd11meZfmFouCh8nGnos=;
+b=oZEzEVkh0EBcihV+npOUKXF8yX0QxuT+Sw3R97FtGdxrK1N8rLwQIIy42H5Ult+vZ4
+ CE+P1m1KCl+hNkLAUGGewovoWAsQQQqvBeyi7/7Icc6ElvLTTrixpVXDa0YnylesgCjZ
+ fkgSvjXztT7G3iJ0XmAqehtEFJp+0bz0Ax5UhmTSG1fhI9xxDH3Ttq/3u1DmPEi1s4Bs
+ N53J7MsclvD+7AngWfnTL6S4+AH0Ijxi/Owlcdg+TR4jiNetjJZSltXJwtTv5WLm/6BW
+ FhgrAiYk84/S1M5OC3UvV8djnyAqRUr8rTCx2cTrontLAADJdnu7d3GkfPvdRNdM0vhC
+ Q6ew==
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+d=1e100.net; s=20210112;
+h=x-gm-message-state:from:to:subject:date:message-id:mime-version
+ :content-transfer-encoding;
+bh=AMNUmfKzCqd/kswglg673XVAd11meZfmFouCh8nGnos=;
+b=czNmd80ZOdR+EiGdluvj4w2JrBDUWXIibUlJGhpzjeV+xl/YyUus+5Fj94mnU1rBmC
+ yZLABXjgjOwi/YVy8nWtXsEOdKVhflpC/FfXuRBruMUIacGnq/dzGfTE1cMi2iMCl5ld
+ p+tumWJaYe2oDs4UILL9xnAKi+RH0IVqJ898jcw9W8Y5J1iGlipqczp8OlqX3ZLgEODa
+ cNt6G90vYELnEHHARACMM1BtS9zi+BrfTwcHmFHT3y2QuOnhISrDVtz4+gEtHcma94iz
+ lI1CExnrbQjPsgQMoG6FvPiggr1QehqDAaOB6ZwbEU+xB0zSbS8Ezt2teCKY2stHSBc6
+ 

Re: convert mtd-mac-address to nvmem implementation

[Paul Blazejowski]

With Ansuel's help i have successfully tested the TP-Link Archer C6v2 
(EU version) using the mtd-mac-address to nvmem changes below, since 
they are missing in: ath79/dts/qca9563_tplink_archer-x6-v2.dtsi file

(https://github.com/openwrt/openwrt/pull/4041#issuecomment-882092102)


diff --git a/target/linux/ath79/dts/qca9563_tplink_archer-c6-v2-us.dts 
b/target/linux/ath79/dts/qca9563_tplink_archer-c6-v2-us.dts

index 892e87ebaf..ae525ff480 100644
--- a/target/linux/ath79/dts/qca9563_tplink_archer-c6-v2-us.dts
+++ b/target/linux/ath79/dts/qca9563_tplink_archer-c6-v2-us.dts
@@ -125,3 +125,13 @@
};
};
 };
+
+ {
+   compatible = "nvmem-cells";
+   #address-cells = <1>;
+   #size-cells = <1>;
+
+   macaddr_info_8: macaddr@8 {
+   reg = <0x8 0x6>;
+   };
+};
diff --git a/target/linux/ath79/dts/qca9563_tplink_archer-c6-v2.dts 
b/target/linux/ath79/dts/qca9563_tplink_archer-c6-v2.dts

index c64402bcfe..469b437585 100644
--- a/target/linux/ath79/dts/qca9563_tplink_archer-c6-v2.dts
+++ b/target/linux/ath79/dts/qca9563_tplink_archer-c6-v2.dts
@@ -119,3 +119,13 @@
};
};
 };
+
+ {
+   compatible = "nvmem-cells";
+   #address-cells = <1>;
+   #size-cells = <1>;
+
+   macaddr_info_8: macaddr@8 {
+   reg = <0x8 0x6>;
+   };
+};
diff --git a/target/linux/ath79/dts/qca9563_tplink_archer-x6-v2.dtsi 
b/target/linux/ath79/dts/qca9563_tplink_archer-x6-v2.dtsi

index 1a074e63a6..9e00113c1d 100644
--- a/target/linux/ath79/dts/qca9563_tplink_archer-x6-v2.dtsi
+++ b/target/linux/ath79/dts/qca9563_tplink_archer-x6-v2.dtsi
@@ -38,12 +38,14 @@
phy-mode = "sgmii";
phy-handle = <>;

-   mtd-mac-address = < 0x8>;
+   nvmem-cells = <_info_8>;
+   nvmem-cell-names = "mac-address";
 };

  {
status = "okay";

mtd-cal-data = < 0x1000>;
-   mtd-mac-address = < 0x8>;
+   nvmem-cells = <_info_8>;
+   nvmem-cell-names = "mac-address";
 };


> Mon Jul 19 07:41:12 PDT 2021
> The dts has been migrated with a script and we decided to remove the
> dtsi that caused some compilation problem.
> We still need to take a decision for the device that have dtsi that
> declare mtd-mac-address using partition tag declared in user dts
> (dtsi use partition declared in the dts)

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[PATCH] ath79: kernel: Add missing quote to drivers/mfd/Kconfig

[Paul Blazejowski]

A missing quote in target/linux/ath79/patches-5.x/920-mikrotik-rb4xx.patch
produces:

...
scripts/kconfig/conf  --syncconfig Kconfig
drivers/mfd/Kconfig:2016:warning: multi-line strings not supported
...

This patch adds missing closing quote, fixing the above warning.

Signed-off-by: Paul Blazejowski 
---
 target/linux/ath79/patches-5.10/920-mikrotik-rb4xx.patch | 2 +-
 target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/target/linux/ath79/patches-5.10/920-mikrotik-rb4xx.patch 
b/target/linux/ath79/patches-5.10/920-mikrotik-rb4xx.patch
index 7c3c91817f..3129fac3ab 100644
--- a/target/linux/ath79/patches-5.10/920-mikrotik-rb4xx.patch
+++ b/target/linux/ath79/patches-5.10/920-mikrotik-rb4xx.patch
@@ -5,7 +5,7 @@
  device found on several devices in RAVE line of hardware.
  
 +config MFD_RB4XX_CPLD
-+  tristate "CPLD driver for Mikrotik RB4xx series boards
++  tristate "CPLD driver for Mikrotik RB4xx series boards"
 +  select MFD_CORE
 +  depends on ATH79 || COMPILE_TEST
 +  help
diff --git a/target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch 
b/target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch
index 60f8bdff79..7f424bbfc6 100644
--- a/target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch
+++ b/target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch
@@ -5,7 +5,7 @@
  device found on several devices in RAVE line of hardware.
  
 +config MFD_RB4XX_CPLD
-+  tristate "CPLD driver for Mikrotik RB4xx series boards
++  tristate "CPLD driver for Mikrotik RB4xx series boards"
 +  select MFD_CORE
 +  depends on ATH79 || COMPILE_TEST
 +  help
-- 
2.32.0


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[PATCH 21.02] ath79: kernel: Add missing quote to drivers/mfd/Kconfig

[Paul Blazejowski]

A missing quote in target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch
produces:

...
scripts/kconfig/conf  --syncconfig Kconfig
drivers/mfd/Kconfig:2016:warning: multi-line strings not supported
...

This patch adds missing closing quote, fixing the above warning.

Signed-off-by: Paul Blazejowski 
---
 target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch 
b/target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch
index 60f8bdff79..7f424bbfc6 100644
--- a/target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch
+++ b/target/linux/ath79/patches-5.4/920-mikrotik-rb4xx.patch
@@ -5,7 +5,7 @@
  device found on several devices in RAVE line of hardware.
  
 +config MFD_RB4XX_CPLD
-+  tristate "CPLD driver for Mikrotik RB4xx series boards
++  tristate "CPLD driver for Mikrotik RB4xx series boards"
 +  select MFD_CORE
 +  depends on ATH79 || COMPILE_TEST
 +  help
-- 
2.32.0


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] ath79: switch to kernel 5.4

[Paul Blazejowski]

 Original Message 
Subject: Re: [OpenWrt-Devel] [PATCH] ath79: switch to kernel 5.4
From: David Bauer 
To: Paul Blazejowski 
Date: 6/27/2020, 4:17:41 PM

> Hi all,

Hi David

> 
> On 6/27/20 9:33 PM, Paul Blazejowski wrote:
>> What worked for me in the initial report to the mailing list was to use
>> this patch from Kevin's staging tree [1] (modified for kernel 5.4, and
>> building with any gcc version on a clean checkout).
> 
> Removing the 308-mips32r2_tune.patch patch is enough.
> What would be interesting to know is whether or not we run
> into a similar / more significant issue with that down the road.

I can confirm, dropping this patch and building the image using GCC
9.3.0 and kernel 5.4.48 produces working image and the router boots
properly, working properly for 14 hours now...on my end.

[0.00] Linux version 5.4.48 (diffie@blaze) (gcc version 9.3.0
(OpenWrt GCC 9.3.0 r13136+1-ad27c133eb)) #0 Sat Jun 27 21:07:58 2020
[0.00] printk: bootconsole [early0] enabled
[0.00] CPU0 revision is: 0001974c (MIPS 74Kc)
[0.00] MIPS: machine is Netgear WNDR3700 v4

> 
> If the issue is due to the optimization being flawed we might be okay
> with that. But i lack significant knowledge about the inner workings of GCC.
> So take that with a grain of salt.

I don't know {yet!) of any implications or pitfalls from removal of said
patch but for now compiled code is working, so optimization may be NOT
the right thing to *do in this case, just a test case on my part. What
you say?

> 
> Best wishes
> David
> 

Thank you,
-paul

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.infradead.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] ath79: switch to kernel 5.4

[Paul Blazejowski]

 Original Message 
Subject: Re: [OpenWrt-Devel] [PATCH] ath79: switch to kernel 5.4
From: 
To: 'Stefan Lippers-Hollmann' 
Date: 6/27/2020, 6:48:05 AM

 See here for some more details:
 https://bugs.openwrt.org/index.php?do=details_id=2928
 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94506
>>>
>>> What's the status on this issue? Is it still there, and do we
>>> still have a
>> blocker for 5.4 on ath79?
>>
>> This issue is still open as of yesterday's master/
>> r13611-3f27a6e640, tested on both tl-wdr3600 and tl-wdr4300 with
>> kernel v5.4.48. The device bootloops very early and in close
>> succession, requiring tftp recovery[0].
>
> I think we should find some way to go on here. ath79 is quite a big
> target, and even after having it switched to 5.4 one should give it
> some time for tests and possible other necessary fixes before
> thinking about branching a release. So far, I see three possible
> options:
>
> 1. Just use Hauke's hack

It does not work anymore (for me at least) see #2

> 2. Use a different GCC version for the target, since problems are
> limited to 8.4.0

GCC 9.3.0 works with kernels up to 5.4.32 anything after and up to
5.4.49 will bootloop so this leads me to believe that this issue lies
also in kernel.

> 3. Find out the real reason for the problem

That's the problem here, the issue is not easy to find but everyone
gets it with no real fix (other thank flipping gcc versions in the
build for a while until it caches up again producing bootloop).

>
> Am I getting this right? Any opinions or additional ideas?

What worked for me in the initial report to the mailing list was to use
this patch from Kevin's staging tree [1] (modified for kernel 5.4, and
building with any gcc version on a clean checkout).
>
> Best
>
> Adrian
>

Cheers,
-paul

[1]
https://git.openwrt.org/?p=openwrt/staging/ldir.git;a=commit;h=2327a4deb
2941f0b59c0f1a8affd109a3262c753

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.infradead.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH v2] exfat-nofuse: fix kernel 5.4 compilation issue

[Paul Blazejowski]

Make exfat-nofuse module depend on kernels 4.14 and 4.19

Signed-off-by: Paul Blazejowski 
---
v2:
  * removed 0003-5.0.patch
  * enabled build dependency for 4.14 and 4.19 kernels only
  
 kernel/exfat-nofuse/Makefile | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/kernel/exfat-nofuse/Makefile b/kernel/exfat-nofuse/Makefile
index 8354f5621..3931dbc34 100644
--- a/kernel/exfat-nofuse/Makefile
+++ b/kernel/exfat-nofuse/Makefile
@@ -10,7 +10,7 @@ include $(TOPDIR)/rules.mk
 include $(INCLUDE_DIR)/kernel.mk
 
 PKG_NAME:=exfat-nofuse
-PKG_RELEASE:=2
+PKG_RELEASE:=3
 
 PKG_SOURCE_URL:=https://github.com/dorimanx/exfat-nofuse.git
 PKG_SOURCE_PROTO:=git
@@ -29,7 +29,7 @@ define KernelPackage/fs-exfat
TITLE:=ExFAT Kernel driver
FILES:=$(PKG_BUILD_DIR)/exfat.ko
AUTOLOAD:=$(call AutoLoad,30,exfat,1)
-   DEPENDS:=+kmod-nls-base
+   DEPENDS:=+kmod-nls-base @(LINUX_4_14||LINUX_4_19)
 endef
 
 define KernelPackage/fs-exfat/description
-- 
2.25.1


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] exfat-nofuse: fix kernel 5.4 compilation issue

[Paul Blazejowski]

On 3/6/20 7:15 PM, Rosen Penev wrote:
> On Fri, Mar 6, 2020 at 11:38 AM Paul Blazejowski
>  wrote:
>>
>> Hi Rosen,
>>
>> Would this patch be more suitable while keeping older kernel compatibility?
>>
>> What's the best way to submit patches for packages without having
>> github.com account?
> Post here. I'll merge.

New patch will follow in next email.

>>
>> Thanks!

Thank you

>>
>> diff --git a/kernel/exfat-nofuse/Makefile b/kernel/exfat-nofuse/Makefile
>> index 8354f5621..3931dbc34 100644
>> --- a/kernel/exfat-nofuse/Makefile
>> +++ b/kernel/exfat-nofuse/Makefile
>> @@ -10,7 +10,7 @@ include $(TOPDIR)/rules.mk
>>  include $(INCLUDE_DIR)/kernel.mk
>>
>>  PKG_NAME:=exfat-nofuse
>> -PKG_RELEASE:=2
>> +PKG_RELEASE:=3
>>
>>  PKG_SOURCE_URL:=https://github.com/dorimanx/exfat-nofuse.git
>>  PKG_SOURCE_PROTO:=git
>> @@ -29,7 +29,7 @@ define KernelPackage/fs-exfat
>> TITLE:=ExFAT Kernel driver
>> FILES:=$(PKG_BUILD_DIR)/exfat.ko
>> AUTOLOAD:=$(call AutoLoad,30,exfat,1)
>> -   DEPENDS:=+kmod-nls-base
>> +   DEPENDS:=+kmod-nls-base @(LINUX_4_14||LINUX_4_19)
> I prefer @!LINUX_5_4

Based on the discussion we are going to keep compatibility with 4.x
kernels just for this package.

> 
> I also want an exfat package for 5.4. As it stands even though it is
> in the staging directory, I don't think a package is available.

Your wish has been answered ;-) we will have native module from staging
for 5.x kernels.

Thanks to all involved!

>>  endef
>>
>>  define KernelPackage/fs-exfat/description
>>
>>
>> On 3/6/20 1:10 AM, Rosen Penev wrote:
>>> On Thu, Mar 5, 2020 at 1:17 PM Paul Blazejowski
>>>  wrote:
>>>>
>>>> Patch taken from
>>>> https://github.com/barrybingo/exfat-nofuse/commit/8b59e1f338fdd87f1d5a9db2a119a3745bb467d5
>>>>
>>>> Signed-off-by: Paul Blazejowski 
>>> This is the wrong place to submit.
>>>
>>> Nevertheless, I'd rather restrict this driver to 4.19 and below.
>>>
>>> kernel 5.4 has an exfat driver available in the staging directory.
>>>> ---
>>>>  kernel/exfat-nofuse/Makefile   |  2 +-
>>>>  kernel/exfat-nofuse/patches/0003-5.0.patch | 88 ++
>>>>  2 files changed, 89 insertions(+), 1 deletion(-)
>>>>  create mode 100644 kernel/exfat-nofuse/patches/0003-5.0.patch
>>>>
>>>> diff --git a/kernel/exfat-nofuse/Makefile b/kernel/exfat-nofuse/Makefile
>>>> index 8354f5621..ebc101144 100644
>>>> --- a/kernel/exfat-nofuse/Makefile
>>>> +++ b/kernel/exfat-nofuse/Makefile
>>>> @@ -10,7 +10,7 @@ include $(TOPDIR)/rules.mk
>>>>  include $(INCLUDE_DIR)/kernel.mk
>>>>
>>>>  PKG_NAME:=exfat-nofuse
>>>> -PKG_RELEASE:=2
>>>> +PKG_RELEASE:=3
>>>>
>>>>  PKG_SOURCE_URL:=https://github.com/dorimanx/exfat-nofuse.git
>>>>  PKG_SOURCE_PROTO:=git
>>>> diff --git a/kernel/exfat-nofuse/patches/0003-5.0.patch 
>>>> b/kernel/exfat-nofuse/patches/0003-5.0.patch
>>>> new file mode 100644
>>>> index 0..da28fc03c
>>>> --- /dev/null
>>>> +++ b/kernel/exfat-nofuse/patches/0003-5.0.patch
>>>> @@ -0,0 +1,88 @@
>>>> +From 8b59e1f338fdd87f1d5a9db2a119a3745bb467d5 Mon Sep 17 00:00:00 2001
>>>> +From: Junde Yhi 
>>>> +Date: Thu, 10 Jan 2019 21:19:49 +0800
>>>> +Subject: [PATCH] exfat_{core,super}.c: fix build on 5.0-rc1, MS_* -> SB_*
>>>> +
>>>> +In torvalds/linux@e462ec50cb a new set of superblock flags was added
>>>> +to replace the original MS_* ones, and in torvalds/linux@e262e32d6b
>>>> +the MS_* flags are suppressed unless uapi/linux/mount.h is included.
>>>> +As is suggested, we should use the new API now.
>>>> +---
>>>> + exfat_core.c  |  6 +-
>>>> + exfat_core.h  |  6 ++
>>>> + exfat_super.c | 11 ++-
>>>> + 3 files changed, 21 insertions(+), 2 deletions(-)
>>>> +
>>>> +diff --git a/exfat_core.c b/exfat_core.c
>>>> +index 143b721..397afd6 100644
>>>> +--- a/exfat_core.c
>>>>  b/exfat_core.c
>>>> +@@ -1757,8 +1757,12 @@ void fs_error(struct super_block *sb)
>>>> +
>>>> +   if (opts->errors == EXFAT_ERRORS_PANIC)
>>>> +   panic("[EXFAT] Filesystem panic from previous error\n");
>>>

[OpenWrt-Devel] [PATCH] exfat-nofuse: fix kernel 5.4 compilation issue

[Paul Blazejowski]

OK, thanks for pointing this out.

On 3/6/20 1:10 AM, Rosen Penev wrote:
> On Thu, Mar 5, 2020 at 1:17 PM Paul Blazejowski
>  wrote:
>>
>> Patch taken from
>> https://github.com/barrybingo/exfat-nofuse/commit/8b59e1f338fdd87f1d5a9db2a119a3745bb467d5
>>
>> Signed-off-by: Paul Blazejowski 
> This is the wrong place to submit.
> 
> Nevertheless, I'd rather restrict this driver to 4.19 and below.
> 
> kernel 5.4 has an exfat driver available in the staging directory.
>> ---
>>  kernel/exfat-nofuse/Makefile   |  2 +-
>>  kernel/exfat-nofuse/patches/0003-5.0.patch | 88 ++
>>  2 files changed, 89 insertions(+), 1 deletion(-)
>>  create mode 100644 kernel/exfat-nofuse/patches/0003-5.0.patch
>>
>> diff --git a/kernel/exfat-nofuse/Makefile b/kernel/exfat-nofuse/Makefile
>> index 8354f5621..ebc101144 100644
>> --- a/kernel/exfat-nofuse/Makefile
>> +++ b/kernel/exfat-nofuse/Makefile
>> @@ -10,7 +10,7 @@ include $(TOPDIR)/rules.mk
>>  include $(INCLUDE_DIR)/kernel.mk
>>
>>  PKG_NAME:=exfat-nofuse
>> -PKG_RELEASE:=2
>> +PKG_RELEASE:=3
>>
>>  PKG_SOURCE_URL:=https://github.com/dorimanx/exfat-nofuse.git
>>  PKG_SOURCE_PROTO:=git
>> diff --git a/kernel/exfat-nofuse/patches/0003-5.0.patch 
>> b/kernel/exfat-nofuse/patches/0003-5.0.patch
>> new file mode 100644
>> index 0..da28fc03c
>> --- /dev/null
>> +++ b/kernel/exfat-nofuse/patches/0003-5.0.patch
>> @@ -0,0 +1,88 @@
>> +From 8b59e1f338fdd87f1d5a9db2a119a3745bb467d5 Mon Sep 17 00:00:00 2001
>> +From: Junde Yhi 
>> +Date: Thu, 10 Jan 2019 21:19:49 +0800
>> +Subject: [PATCH] exfat_{core,super}.c: fix build on 5.0-rc1, MS_* -> SB_*
>> +
>> +In torvalds/linux@e462ec50cb a new set of superblock flags was added
>> +to replace the original MS_* ones, and in torvalds/linux@e262e32d6b
>> +the MS_* flags are suppressed unless uapi/linux/mount.h is included.
>> +As is suggested, we should use the new API now.
>> +---
>> + exfat_core.c  |  6 +-
>> + exfat_core.h  |  6 ++
>> + exfat_super.c | 11 ++-
>> + 3 files changed, 21 insertions(+), 2 deletions(-)
>> +
>> +diff --git a/exfat_core.c b/exfat_core.c
>> +index 143b721..397afd6 100644
>> +--- a/exfat_core.c
>>  b/exfat_core.c
>> +@@ -1757,8 +1757,12 @@ void fs_error(struct super_block *sb)
>> +
>> +   if (opts->errors == EXFAT_ERRORS_PANIC)
>> +   panic("[EXFAT] Filesystem panic from previous error\n");
>> +-  else if ((opts->errors == EXFAT_ERRORS_RO) && !(sb->s_flags & 
>> MS_RDONLY)) {
>> ++  else if ((opts->errors == EXFAT_ERRORS_RO) && 
>> !EXFAT_IS_SB_RDONLY(sb)) {
>> ++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 0)
>> +   sb->s_flags |= MS_RDONLY;
>> ++#else
>> ++  sb->s_flags |= SB_RDONLY;
>> ++#endif
>> +   printk(KERN_ERR "[EXFAT] Filesystem has been set 
>> read-only\n");
>> +   }
>> + }
>> +diff --git a/exfat_core.h b/exfat_core.h
>> +index 52d05c7..3d023b7 100644
>> +--- a/exfat_core.h
>>  b/exfat_core.h
>> +@@ -45,6 +45,12 @@
>> + #include "exfat_api.h"
>> + #include "exfat_cache.h"
>> +
>> ++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 0)
>> ++#define EXFAT_IS_SB_RDONLY(sb) ((sb)->s_flags & MS_RDONLY)
>> ++#else
>> ++#define EXFAT_IS_SB_RDONLY(sb) ((sb)->s_flags & SB_RDONLY)
>> ++#endif
>> ++
>> + #ifdef CONFIG_EXFAT_KERNEL_DEBUG
>> +   /* For Debugging Purpose */
>> +   /* IOCTL code 'f' used by
>> +diff --git a/exfat_super.c b/exfat_super.c
>> +index 79ff5f9..6452b54 100644
>> +--- a/exfat_super.c
>>  b/exfat_super.c
>> +@@ -2086,7 +2086,7 @@ static void exfat_write_super(struct super_block *sb)
>> +
>> +   __set_sb_clean(sb);
>> +
>> +-  if (!(sb->s_flags & MS_RDONLY))
>> ++  if (!EXFAT_IS_SB_RDONLY(sb))
>> +   FsSyncVol(sb, 1);
>> +
>> +   __unlock_super(sb);
>> +@@ -2142,7 +2142,12 @@ static int exfat_statfs(struct dentry *dentry, 
>> struct kstatfs *buf)
>> +
>> + static int exfat_remount(struct super_block *sb, int *flags, char *data)
>> + {
>> ++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 0)
>> +   *flags |= MS_NODIRATIME;
>> ++#else
>> ++  *flags |= SB_NODIRATIME;
>> ++#endif
>> ++
>> +   return 0;
>> + }
>> +
>> +@@ -2495,7 +2500,11 @@ static int exfat_fill_super(struct super_block *sb, 
>> void *data, int silent)
>> +   mutex_init(>s_lock);
>> + #endif
>> +   sb->s_fs_info = sbi;
>> ++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 0)
>> +   sb->s_flags |= MS_NODIRATIME;
>> ++#else
>> ++  sb->s_flags |= SB_NODIRATIME;
>> ++#endif
>> +   sb->s_magic = EXFAT_SUPER_MAGIC;
>> +   sb->s_op = _sops;
>> +   sb->s_export_op = _export_ops;
>> --
>> 2.25.1
>>
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] ath79: nand: add missing symbols

[Paul Blazejowski]

Removed in 53ab9865c2b91bc6a239b2adee800dc52875b6bc

Fixes unable to find root fs

Signed-off-by: Paul Blazejowski 
---
 target/linux/ath79/nand/config-default | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/target/linux/ath79/nand/config-default 
b/target/linux/ath79/nand/config-default
index 50bc550794..97563d5781 100644
--- a/target/linux/ath79/nand/config-default
+++ b/target/linux/ath79/nand/config-default
@@ -5,7 +5,10 @@ CONFIG_CRYPTO_HASH_INFO=y
 CONFIG_CRYPTO_LZO=y
 CONFIG_LZO_COMPRESS=y
 CONFIG_LZO_DECOMPRESS=y
+CONFIG_MTD_NAND=y
+CONFIG_MTD_NAND_AR934X=y
 CONFIG_MTD_NAND_CORE=y
+CONFIG_MTD_NAND_ECC=y
 CONFIG_MTD_SPI_NAND=y
 CONFIG_MTD_SPLIT_MINOR_FW=y
 CONFIG_MTD_UBI=y
-- 
2.25.1


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] exfat-nofuse: fix kernel 5.4 compilation issue

[Paul Blazejowski]

Patch taken from
https://github.com/barrybingo/exfat-nofuse/commit/8b59e1f338fdd87f1d5a9db2a119a3745bb467d5

Signed-off-by: Paul Blazejowski 
---
 kernel/exfat-nofuse/Makefile   |  2 +-
 kernel/exfat-nofuse/patches/0003-5.0.patch | 88 ++
 2 files changed, 89 insertions(+), 1 deletion(-)
 create mode 100644 kernel/exfat-nofuse/patches/0003-5.0.patch

diff --git a/kernel/exfat-nofuse/Makefile b/kernel/exfat-nofuse/Makefile
index 8354f5621..ebc101144 100644
--- a/kernel/exfat-nofuse/Makefile
+++ b/kernel/exfat-nofuse/Makefile
@@ -10,7 +10,7 @@ include $(TOPDIR)/rules.mk
 include $(INCLUDE_DIR)/kernel.mk
 
 PKG_NAME:=exfat-nofuse
-PKG_RELEASE:=2
+PKG_RELEASE:=3
 
 PKG_SOURCE_URL:=https://github.com/dorimanx/exfat-nofuse.git
 PKG_SOURCE_PROTO:=git
diff --git a/kernel/exfat-nofuse/patches/0003-5.0.patch 
b/kernel/exfat-nofuse/patches/0003-5.0.patch
new file mode 100644
index 0..da28fc03c
--- /dev/null
+++ b/kernel/exfat-nofuse/patches/0003-5.0.patch
@@ -0,0 +1,88 @@
+From 8b59e1f338fdd87f1d5a9db2a119a3745bb467d5 Mon Sep 17 00:00:00 2001
+From: Junde Yhi 
+Date: Thu, 10 Jan 2019 21:19:49 +0800
+Subject: [PATCH] exfat_{core,super}.c: fix build on 5.0-rc1, MS_* -> SB_*
+
+In torvalds/linux@e462ec50cb a new set of superblock flags was added
+to replace the original MS_* ones, and in torvalds/linux@e262e32d6b
+the MS_* flags are suppressed unless uapi/linux/mount.h is included.
+As is suggested, we should use the new API now.
+---
+ exfat_core.c  |  6 +-
+ exfat_core.h  |  6 ++
+ exfat_super.c | 11 ++-
+ 3 files changed, 21 insertions(+), 2 deletions(-)
+
+diff --git a/exfat_core.c b/exfat_core.c
+index 143b721..397afd6 100644
+--- a/exfat_core.c
 b/exfat_core.c
+@@ -1757,8 +1757,12 @@ void fs_error(struct super_block *sb)
+ 
+   if (opts->errors == EXFAT_ERRORS_PANIC)
+   panic("[EXFAT] Filesystem panic from previous error\n");
+-  else if ((opts->errors == EXFAT_ERRORS_RO) && !(sb->s_flags & 
MS_RDONLY)) {
++  else if ((opts->errors == EXFAT_ERRORS_RO) && !EXFAT_IS_SB_RDONLY(sb)) {
++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 0)
+   sb->s_flags |= MS_RDONLY;
++#else
++  sb->s_flags |= SB_RDONLY;
++#endif
+   printk(KERN_ERR "[EXFAT] Filesystem has been set read-only\n");
+   }
+ }
+diff --git a/exfat_core.h b/exfat_core.h
+index 52d05c7..3d023b7 100644
+--- a/exfat_core.h
 b/exfat_core.h
+@@ -45,6 +45,12 @@
+ #include "exfat_api.h"
+ #include "exfat_cache.h"
+ 
++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 0)
++#define EXFAT_IS_SB_RDONLY(sb) ((sb)->s_flags & MS_RDONLY)
++#else
++#define EXFAT_IS_SB_RDONLY(sb) ((sb)->s_flags & SB_RDONLY)
++#endif
++
+ #ifdef CONFIG_EXFAT_KERNEL_DEBUG
+   /* For Debugging Purpose */
+   /* IOCTL code 'f' used by
+diff --git a/exfat_super.c b/exfat_super.c
+index 79ff5f9..6452b54 100644
+--- a/exfat_super.c
 b/exfat_super.c
+@@ -2086,7 +2086,7 @@ static void exfat_write_super(struct super_block *sb)
+ 
+   __set_sb_clean(sb);
+ 
+-  if (!(sb->s_flags & MS_RDONLY))
++  if (!EXFAT_IS_SB_RDONLY(sb))
+   FsSyncVol(sb, 1);
+ 
+   __unlock_super(sb);
+@@ -2142,7 +2142,12 @@ static int exfat_statfs(struct dentry *dentry, struct 
kstatfs *buf)
+ 
+ static int exfat_remount(struct super_block *sb, int *flags, char *data)
+ {
++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 0)
+   *flags |= MS_NODIRATIME;
++#else
++  *flags |= SB_NODIRATIME;
++#endif
++
+   return 0;
+ }
+ 
+@@ -2495,7 +2500,11 @@ static int exfat_fill_super(struct super_block *sb, 
void *data, int silent)
+   mutex_init(>s_lock);
+ #endif
+   sb->s_fs_info = sbi;
++#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 0)
+   sb->s_flags |= MS_NODIRATIME;
++#else
++  sb->s_flags |= SB_NODIRATIME;
++#endif
+   sb->s_magic = EXFAT_SUPER_MAGIC;
+   sb->s_op = _sops;
+   sb->s_export_op = _export_ops;
-- 
2.25.1


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 2/2] ath79: add support for Netgear WNDR3700v4

[Paul Blazejowski]

This patch adds ath79 support for Netgear WNDR3700v4.
Router was previously supported by ar71xx target only.
Note: device requires 'ar934x-nand' driver in kernel.

Specification
=
  * Description: Netgear WNDR3700v4
  * Loader: U-boot
  * SOC: Atheros AR9344 (560 MHz)
  * RAM: 128 MiB
  * Flash: 128 MiB (NAND)
- U-boot binary: 256 KiB
- U-boot environment: 256 KiB
- ART: 256 KiB
- POT: 512 KiB
- Language: 2 MiB
- Config: 512 KiB
- Traffic Meter: 3 MiB
- Firmware: 25 MiB
- ART Backup: 256 KiB
- Reserved: 96 MiB
  * Ethernet: 5 x 10/100/1000 (4 x LAN, 1 x WAN) (AR8327)
  * Wireless:
- 2.4 GHz b/g/n (internal)
- 5 GHz a/n (AR9580)
  * USB: yes, 1 x USB 2.0
  * Buttons:
- Reset
- WiFi (rfkill)
- WPS
  * LEDs:
- Power (amber/green)
- WAN (amber/green)
- WLAN 2G (green)
- WLAN 5G (blue)
- 4 x LAN (amber/green)
- USB (green)
- WPS (amber/green)
  * UART: 4-pin connector JP1, 3.3V (Vcc, TX, RX, GND), 115200 8N1
  * Power supply: DC 12V 2.5A
  * MAC addresses: LAN=WLAN2G on case label, WAN +1, WLAN5G +2

Installation

  * TFTP recovery
  * TFTP via U-boot prompt
  * sysupgrade
  * Web interface

Note about partitioning: firmware partition offset (0x6c) is
hardcoded into vendor's u-boot, so this partition cannot be moved
and resized to include Netgear-specific flash areas (pot, language,
config, traffic_meter) not used by OpenWrt.

Test build configuration

CONFIG_TARGET_ath79=y
CONFIG_TARGET_ath79_nand=y
CONFIG_TARGET_ath79_nand_DEVICE_netgear_wndr3700-v4=y
CONFIG_ALL_KMODS=y
CONFIG_DEVEL=y
CONFIG_CCACHE=y
CONFIG_COLLECT_KERNEL_DEBUG=y
CONFIG_IMAGEOPT=y

Signed-off-by: Paul Blazejowski 
---
 package/boot/uboot-envtools/files/ath79  |  1 +
 .../linux/ath79/dts/ar9344_netgear_wndr3700-v4.dts   |  9 +
 target/linux/ath79/image/nand.mk | 12 
 .../linux/ath79/nand/base-files/etc/board.d/01_leds  |  1 +
 .../ath79/nand/base-files/etc/board.d/02_network |  2 ++
 .../etc/hotplug.d/firmware/10-ath9k-eeprom   |  2 ++
 6 files changed, 27 insertions(+)
 create mode 100644 target/linux/ath79/dts/ar9344_netgear_wndr3700-v4.dts

diff --git a/package/boot/uboot-envtools/files/ath79 
b/package/boot/uboot-envtools/files/ath79
index fefbb48801..c5c2a6b11e 100644
--- a/package/boot/uboot-envtools/files/ath79
+++ b/package/boot/uboot-envtools/files/ath79
@@ -39,6 +39,7 @@ buffalo,wzr-hp-ag300h)
 netgear,wndr3700)
ubootenv_add_uci_config "/dev/mtd1" "0x0" "0x2" "0x1"
;;
+netgear,wndr3700-v4|\
 netgear,wndr4300)
ubootenv_add_uci_config "/dev/mtd1" "0x0" "0x4" "0x2"
;;
diff --git a/target/linux/ath79/dts/ar9344_netgear_wndr3700-v4.dts 
b/target/linux/ath79/dts/ar9344_netgear_wndr3700-v4.dts
new file mode 100644
index 00..8a38aeab59
--- /dev/null
+++ b/target/linux/ath79/dts/ar9344_netgear_wndr3700-v4.dts
@@ -0,0 +1,9 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/dts-v1/;
+
+#include "ar9344_netgear_wndr.dtsi"
+
+/ {
+   compatible = "netgear,wndr3700-v4", "qca,ar9344";
+   model = "Netgear WNDR3700 v4";
+};
diff --git a/target/linux/ath79/image/nand.mk b/target/linux/ath79/image/nand.mk
index ef6b607002..75808dcbfb 100644
--- a/target/linux/ath79/image/nand.mk
+++ b/target/linux/ath79/image/nand.mk
@@ -80,6 +80,18 @@ define Device/netgear_ath79_nand
   UBINIZE_OPTS := -E 5
 endef
 
+define Device/netgear_wndr3700-v4
+  ATH_SOC := ar9344
+  DEVICE_MODEL := WNDR3700
+  DEVICE_VARIANT := v4
+  NETGEAR_KERNEL_MAGIC := 0x33373033
+  NETGEAR_BOARD_ID := WNDR3700v4
+  NETGEAR_HW_ID := 29763948+128+128
+  SUPPORTED_DEVICES += wndr3700v4
+  $(Device/netgear_ath79_nand)
+endef
+TARGET_DEVICES += netgear_wndr3700-v4
+
 define Device/netgear_wndr4300
   ATH_SOC := ar9344
   DEVICE_MODEL := WNDR4300
diff --git a/target/linux/ath79/nand/base-files/etc/board.d/01_leds 
b/target/linux/ath79/nand/base-files/etc/board.d/01_leds
index f851b3d886..d95958dc88 100755
--- a/target/linux/ath79/nand/base-files/etc/board.d/01_leds
+++ b/target/linux/ath79/nand/base-files/etc/board.d/01_leds
@@ -11,6 +11,7 @@ case "$board" in
 glinet,gl-ar300m-nand)
ucidef_set_led_netdev "lan" "LAN" "gl-ar300m:green:lan" "eth0"
;;
+netgear,wndr3700-v4|\
 netgear,wndr4300)
ucidef_set_led_switch "wan-amber" "WAN (amber)" "netgear:amber:wan" 
"switch0" "0x20"
;;
diff --git a/target/linux/ath79/nand/base-files/etc/board.d/02_network 
b/target/linux/ath79/nand/base-files/etc/board.d/02_network
index 9d7a19c2eb..0edba29e2b 100755
--- a/target/linux/ath79/nand/base-files/etc/board.d/02_network
+++ b/target/linux/ath79/nand/base-files/etc/board.d/02_network
@@ -11,6

[OpenWrt-Devel] [PATCH 1/2] ath79: split dts file for Netgear WNDR4300

[Paul Blazejowski]

From: Michal Cieslakiewicz 

Move board configuration to dtsi file in preparation for WNDR3700v4
router support.

Signed-off-by: Michal Cieslakiewicz 
---
 .../linux/ath79/dts/ar9344_netgear_wndr.dtsi  | 290 ++
 .../ath79/dts/ar9344_netgear_wndr4300.dts | 286 +
 2 files changed, 291 insertions(+), 285 deletions(-)
 create mode 100644 target/linux/ath79/dts/ar9344_netgear_wndr.dtsi

diff --git a/target/linux/ath79/dts/ar9344_netgear_wndr.dtsi 
b/target/linux/ath79/dts/ar9344_netgear_wndr.dtsi
new file mode 100644
index 00..16a4e3f6e8
--- /dev/null
+++ b/target/linux/ath79/dts/ar9344_netgear_wndr.dtsi
@@ -0,0 +1,290 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/dts-v1/;
+
+#include 
+#include 
+
+#include "ar9344.dtsi"
+
+/ {
+   chosen {
+   bootargs = "console=ttyS0,115200n8";
+   };
+
+   aliases {
+   led-boot = _power_amber;
+   led-failsafe = _power_amber;
+   led-running = _power_green;
+   led-upgrade = _power_amber;
+   label-mac-device = 
+   };
+
+   keys {
+   compatible = "gpio-keys";
+
+   wps {
+   label = "wps";
+   linux,code = ;
+   gpios = < 12 GPIO_ACTIVE_LOW>;
+   };
+
+   reset {
+   label = "reset";
+   linux,code = ;
+   gpios = < 21 GPIO_ACTIVE_LOW>;
+   };
+
+   rfkill {
+   label = "rfkill";
+   linux,code = ;
+   gpios = < 15 GPIO_ACTIVE_LOW>;
+   };
+   };
+
+   leds {
+   compatible = "gpio-leds";
+
+   pinctrl-names = "default";
+   pinctrl-0 = <_gpio_11>;
+
+   led_power_green: power_green {
+   label = "netgear:green:power";
+   gpios = < 0 GPIO_ACTIVE_LOW>;
+   };
+
+   led_power_amber: power_amber {
+   label = "netgear:amber:power";
+   gpios = < 2 GPIO_ACTIVE_LOW>;
+   default-state = "keep";
+   };
+
+   wan_green {
+   label = "netgear:green:wan";
+   gpios = < 1 GPIO_ACTIVE_LOW>;
+   };
+
+   wan_amber {
+   label = "netgear:amber:wan";
+   gpios = < 3 GPIO_ACTIVE_LOW>;
+   };
+
+   wlan2g_green {
+   label = "netgear:green:wlan2g";
+   gpios = < 11 GPIO_ACTIVE_LOW>;
+   linux,default-trigger = "phy0tpt";
+   };
+
+   wlan5g_blue {
+   label = "netgear:blue:wlan5g";
+   gpios = < 14 GPIO_ACTIVE_LOW>;
+   linux,default-trigger = "phy1tpt";
+   };
+
+   wps_green {
+   label = "netgear:green:wps";
+   gpios = < 16 GPIO_ACTIVE_LOW>;
+   };
+
+   wps_amber {
+   label = "netgear:amber:wps";
+   gpios = < 17 GPIO_ACTIVE_LOW>;
+   };
+
+   usb_green {
+   label = "netgear:green:usb";
+   gpios = < 13 GPIO_ACTIVE_LOW>;
+   trigger-sources = <_port>;
+   linux,default-trigger = "usbport";
+   };
+   };
+};
+
+ {
+   enable_gpio_11: pinmux_enable_gpio_11 {
+   pinctrl-single,bits = <0x8 0x0 0xff00>;
+   };
+};
+
+ {
+   status = "okay";
+
+   partitions {
+   compatible = "fixed-partitions";
+   #address-cells = <1>;
+   #size-cells = <1>;
+
+   partition@0 {
+   label = "u-boot";
+   reg = <0x0 0x4>;
+   read-only;
+   };
+
+   partition@4 {
+   label = "u-boot-env";
+   reg = <0x4 0x4>;
+   };
+
+   art: partition@8 {
+   label = "caldata";
+   reg = <0x8 0x4>;
+   read-only;
+   };
+
+   partition@c {
+   label = "pot";
+   reg = <0xc 0x8>;
+   };
+
+   partition@14 {
+   label = "language";
+   reg = <0x14 0x20>;
+   };
+
+   partition@34 {
+   label = "config";
+   reg = <0x34 0x8>;
+   };
+
+   partition@3c {
+   label = "traffic_meter";
+   reg = <0x3c 

Re: [OpenWrt-Devel] FW: [PATCH 2/2] ath79: add support for Netgear WNDR3700v4

[Paul Blazejowski]

On 11/13/19 12:42 PM, Schmutzler, Adrian wrote:
>  
> 
>  
> 
> *From:*Adrian Schmutzler [mailto:m...@adrianschmutzler.de]
> *Sent:* Mittwoch, 13. November 2019 18:39
> *To:* 'Paul Blazejowski' ;
> 'openwrt-devel@lists.openwrt.org' 
> *Subject:* RE: [PATCH 2/2] ath79: add support for Netgear WNDR3700v4
> 
>  
Hi Adrian,

> 
> Hi,
> 
>> diff --git a/target/linux/ath79/dts/ar9344_netgear_wndr3700-v4.dts
>> b/target/linux/ath79/dts/ar9344_netgear_wndr3700-v4.dts
>> new file mode 100644
>> index 00..eb1ad731c3
>> --- /dev/null
>> +++ b/target/linux/ath79/dts/ar9344_netgear_wndr3700-v4.dts
>> @@ -0,0 +1,9 @@
>> +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
>> +/dts-v1/;
>> +
>> +#include "ar9344_netgear_wndr.dtsi"
>> +
>> +/ {
>> +    compatible = "netgear,wndr3700-v4", "qca,ar9344";
>> +    model = "Netgear WNDR3700 v4";
>> +};
> 
> Indent should be fixed here (-> tab).

Ok, noted!

> 
> One could also copy the flashing instructions to the commit message, so
> you do not have to search for them.

OK

> 
> Both could also be done by a willing dev during merge, unless there is
> more to fix.

Thanks for your help!

> 
> Best
> 
> Adrian
> 

Cheerios!
-paul

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Fwd: RFT: ar71xx/mac80211 update

[Paul Blazejowski]

Hi Koen,

I must've missed the git log entry when i pulled...correct rebuilding
with the 4.14 kernel was a success. No issues thus far. Everything is
working on my WNDR3700v4.

Thank you,
-paul

On 10/4/18 1:56 AM, Koen Vandeputte wrote:
> 
> 
> 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 rebuild/retest please?
> 
> Thanks,
> 
> Koen
> 
> [1]
> https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=42f158314e011293ffdaeab5870b19110f4e2e9d
> 

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Fwd: RFT: ar71xx/mac80211 update

[Paul Blazejowski]

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


 Forwarded Message 
Subject: Re: [OpenWrt-Devel] RFT: ar71xx/mac80211 update
Date: Mon, 17 Sep 2018 11:15:38 -0400
From: Paul Blazejowski 
To: John Crispin 
CC: lede-...@lists.infradead.org.

Hi John,

Just got around to attaching serial console to my WNDR3700v4 router.
I've noticed this from dmesg on the 4.14 kernel:

[2.508670] switch0: Atheros AR8327 rev. 4 switch registered on
ag71xx-mdio.0
[2.516001] Atheros AR8216/AR8236/AR8316: probe of ag71xx-mdio.0:00
failed with error -22
[2.536550] libphy: ag71xx_mdio: probed
[3.164846] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00
[uid=004dd034, driver=Generic PHY]

where on 4.9 kernel dmesg shows:

[2.496323] switch0: Atheros AR8327 rev. 4 switch registered on
ag71xx-mdio.0
[3.161242] libphy: ag71xx_mdio: probed
[3.789973] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00
[uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]

Looks like the 4.14 kernel is picking wrong driver? Rendering
ethernet/wireless ports not working.

Hope this helps narrowing down the culrpit of this problem.

Thanks,
-paul

On 8/14/18 2:25 AM, John Crispin wrote:
> 
> 
> On 13/08/18 21:47, Paul Blazejowski wrote:
>> John,
>>
>> Thanks for your work, trying to compile your -staging tree for netgear
>> WNDR3700v4 produces this error from kernel (yeah i went ahead and pulled
>> 4.14.62 kernel)
>>
>>    CC  arch/mips/ath79/mach-c60.o
>> arch/mips/ath79/mach-c60.c:18:10: fatal error: linux/mtd/nand.h: No such
>> file or directory
>>   #include 
>>    ^~
>> compilation terminated.
>>
>> Thanks,
>>
>> -paul
> thanks for testing, just pushed an updated tree with a fix
>     John

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ar71xx update to v3.18

[Paul Blazejowski]

On Tue, 2015-02-17 at 15:36 +0100, John Crispin wrote:
 
 On 16/02/2015 21:47, Paul Blazejowski wrote:
  On Mon, 2015-02-16 at 08:10 +0100, John Crispin wrote:
 
  On 16/02/2015 00:15, Paul Blazejowski wrote:
  00 KHz AUTO), (N/A, 2000 mBm), (0 s)
  [   21.73] cfg80211:   (549 KHz - 573 KHz @ 16 KHz),
  (N/A, 2000 mBm), (0 s)
  [   21.74] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz),
  (N/A, 2000 mBm), (N/A)
  [   21.75] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz),
  (N/A, 0 mBm), (N/A)
  [   22.17] ath9k ar934x_wmac: Direct firmware load for
  soc_wmac.eeprom failed with error -2
  [   22.18] ath: phy0: Unable to load EEPROM file soc_wmac.eeprom
  [   22.19] ath9k ar934x_wmac: failed to initialize device
  [   22.19] ath9k: probe of ar934x_wmac failed with error -22
  [   22.20] PCI: Enabling device :00:00.0 ( - 0002)
  [   22.22] ath9k :00:00.0: Direct firmware load for
  pci_wmac0.eeprom failed with error -2
  [   22.23] ath: phy1: Unable to load EEPROM file pci_wmac0.eeprom
  [   22.23] ath9k :00:00.0: Failed to initialize device
  [   22.24] ath9k: probe of :00:00.0 failed with error -22
  [   29.76] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 
  probably related to this - https://dev.openwrt.org/ticket/18992
 
  do a cat /tmp/sysinfo/* please
  
  nope sir, just replied to your other mail...but here it is again:
  
  root@router:~# cat /tmp/sysinfo/*
  wndr3700v4
  NETGEAR WNDR3700v4
  
 
 the firmware loader was not enabled in 3.18 and 3.19. r44481 fixes this.
 it is now working as expected on my wndr4300
 
 i also decided to set 3.18 as the default as this was the only issue
 that was reported.
 
 thanks for testing,
   John


Hi John,

the router has been up for over 2 hours and all is working OK here as
well.

Thank you for resolving this issue,

-paul
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ar71xx update to v3.18

[Paul Blazejowski]

On Mon, 2015-02-16 at 08:10 +0100, John Crispin wrote:
 
 On 16/02/2015 00:15, Paul Blazejowski wrote:
  00 KHz AUTO), (N/A, 2000 mBm), (0 s)
  [   21.73] cfg80211:   (549 KHz - 573 KHz @ 16 KHz),
  (N/A, 2000 mBm), (0 s)
  [   21.74] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz),
  (N/A, 2000 mBm), (N/A)
  [   21.75] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz),
  (N/A, 0 mBm), (N/A)
  [   22.17] ath9k ar934x_wmac: Direct firmware load for
  soc_wmac.eeprom failed with error -2
  [   22.18] ath: phy0: Unable to load EEPROM file soc_wmac.eeprom
  [   22.19] ath9k ar934x_wmac: failed to initialize device
  [   22.19] ath9k: probe of ar934x_wmac failed with error -22
  [   22.20] PCI: Enabling device :00:00.0 ( - 0002)
  [   22.22] ath9k :00:00.0: Direct firmware load for
  pci_wmac0.eeprom failed with error -2
  [   22.23] ath: phy1: Unable to load EEPROM file pci_wmac0.eeprom
  [   22.23] ath9k :00:00.0: Failed to initialize device
  [   22.24] ath9k: probe of :00:00.0 failed with error -22
  [   29.76] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 
 probably related to this - https://dev.openwrt.org/ticket/18992
 
 do a cat /tmp/sysinfo/* please

nope sir, just replied to your other mail...but here it is again:

root@router:~# cat /tmp/sysinfo/*
wndr3700v4
NETGEAR WNDR3700v4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] ar71xx update to v3.18

[Paul Blazejowski]

On Sun, 2015-02-15 at 20:49 +0100, John Crispin wrote:
 Hi,
 
 i just pushed the v3.18 support for ar71xx. i have tested this on
 carambola2, unifi and wndr4300. the default is still at 3.14. please
 start testing on more hardware.
 
 to do so you need to set the kernel to 3.18 in
 target/linux/ar71xx/Makefile as the default is still at 3.14.
 
 902-unaligned_access_hacks.patch was rebased, however there might be new
 places in the stack that need the hack applied. testing for this is also
 welcome.
 
   John
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Compiled just fine here on wndr3700v4. Sysupgraded my router via LuCI
and immediately noticed two things:

1. no wifi

[   21.67] cfg80211: Calling CRDA to update world regulatory domain
[   21.67] cfg80211: World regulatory domain updated:
[   21.68] cfg80211:  DFS Master region: unset
[   21.68] cfg80211:   (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[   21.69] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz),
(N/A, 2000 mBm), (N/A)
[   21.70] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz),
(N/A, 2000 mBm), (N/A)
[   21.71] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz),
(N/A, 2000 mBm), (N/A)
[   21.72] cfg80211:   (517 KHz - 525 KHz @ 8 KHz),
(N/A, 2000 mBm), (N/A)
[   21.73] cfg80211:   (525 KHz - 533 KHz @ 8 KHz,
16 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   21.73] cfg80211:   (549 KHz - 573 KHz @ 16 KHz),
(N/A, 2000 mBm), (0 s)
[   21.74] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz),
(N/A, 2000 mBm), (N/A)
[   21.75] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz),
(N/A, 0 mBm), (N/A)
[   22.17] ath9k ar934x_wmac: Direct firmware load for
soc_wmac.eeprom failed with error -2
[   22.18] ath: phy0: Unable to load EEPROM file soc_wmac.eeprom
[   22.19] ath9k ar934x_wmac: failed to initialize device
[   22.19] ath9k: probe of ar934x_wmac failed with error -22
[   22.20] PCI: Enabling device :00:00.0 ( - 0002)
[   22.22] ath9k :00:00.0: Direct firmware load for
pci_wmac0.eeprom failed with error -2
[   22.23] ath: phy1: Unable to load EEPROM file pci_wmac0.eeprom
[   22.23] ath9k :00:00.0: Failed to initialize device
[   22.24] ath9k: probe of :00:00.0 failed with error -22
[   29.76] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready


2. bridge warning

bridge: automatic filtering via arp/ip/ip6tables has been deprecated.
Update your scripts to load br_netfilter if you need this.

regular ethX ports (lan side) work fine over wire.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] MTD mounting problem on ar71xx and kernel 3.14.x.

[Paul Blazejowski]

Hello all,

A while back i have created a ticket
(https://dev.openwrt.org/ticket/17609) detailing kernel 3.14.x failure
to boot on ar71xx (wndr3700v4 router) platform. Today i have
successfully used serial console attached to the router and got a boot
log which shows a wrong checksum of kernel image when trying to attach
it from UBI to MTD, please see output below ... i hope this helps in
identifying and narrows the issue for a possible fix.

Cheers!
-paul

U-Boot 1.1.4 (Jun 21 2012 - 11:09:33)

DNI HW ID: 29763948 flash 128MB RAM 128MB U-boot dni29 V1.8


DRAM:  128 MB
Atheros on-chip NAND FLash Controller Driver, Version 0.1 (c) 2010
Atheros Communications, Ltd.
Ath Nand ID[87ff0178]: 2c:f1:80:95:02
ONFI MICRON  MT29F1G08ABADAWP
Micron NAND 128MiB 3,3V 8-bit [128MB]
== NAND Parameters ==
sc = 0x87ff0158 bbt = 0x87f68008 bbt_size = 0x100 nf_ctrl = 0x344
page = 0x800 block = 0x2 oob = 0x40
size = 128MB
Setting 0xb8116290 to 0x4a942d0f
Using default environment

In:serial
Out:   serial
Err:   serial
Net:   ag934x_enet_initialize...
 4096 bytes read: OK
Fetching MAC Address from 0x87fe7928
 wasp  reset mask:c02300
WASP   S17 PHY *
: cfg1 0x8000 cfg2 0x7114
eth0: 44:94:fc:73:9a:fc
athrs17_reg_init: complete
eth0 up
eth0
Hit any key to stop autoboot:  0
dup 1 speed 1000

 Client starts...[Listening] for ADVERTISE...checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
Tchecksum bad
checksum bad
TT
Retry count exceeded; boot the image as usual

 nmrp server is stopped or failed !

Loading from device 0: ath-nand (offset 0x6c)

** check kernel image **
   Verifying Checksum ... OK

** check rootfs image **
   Verifying Checksum ... OK
## Booting image at 8100 ...
   Image Name:   MIPS OpenWrt Linux-3.10.55
   Created:  2014-09-30  15:48:31 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:1965951 Bytes =  1.9 MB
   Load Address: 8006
   Entry Point:  8006
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

[0.00] Linux version 3.10.55 (diffie@blaze) (gcc version 4.8.3
(OpenWrt/Linaro GCC 4.8-2014.04 r42682) ) #1 Tue Sep 30 11:48:14 EDT
2014
[0.00] bootconsole [early0] enabled
[0.00] CPU revision is: 0001974c (MIPS 74Kc)
[0.00] SoC: Atheros AR9344 rev 2
[0.00] Clocks: CPU:560.000MHz, DDR:400.000MHz, AHB:200.000MHz,
Ref:40.000MHz
[0.00] Determined physical RAM map:
[0.00]  memory: 0800 @  (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Zone ranges:
[0.00]   Normal   [mem 0x-0x07ff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x07ff]
[0.00] Primary instruction cache 64kB, VIPT, 4-way, linesize 32
bytes.
[0.00] Primary data cache 32kB, 4-way, VIPT, cache aliases,
linesize 32 bytes
[0.00] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 32512
[0.00] Kernel command line:  board=WNDR3700_V4
console=ttyS0,115200
mtdparts=ar934x-nfc:256k(u-boot)ro,256k(u-boot-env)ro,256k(caldata),512k(pot),2048k(language),512k(config),3072k(traffic_meter),2048k(kernel),121856k(ubi),123904k@0x6c(firmware),256k(caldata_backup),-(reserved)
 rootfstype=squashfs noinitrd
[0.00] PID hash table entries: 512 (order: -1, 2048 bytes)
[0.00] Dentry cache hash table entries: 16384 (order: 4, 65536
bytes)
[0.00] Inode-cache hash table entries: 8192 (order: 3, 32768
bytes)
[0.00] Writing ErrCtl register=
[0.00] Readback ErrCtl register=
[0.00] Memory: 125868k/131072k available (2570k kernel code,
5204k reserved, 653k data, 228k init, 0k highmem)
[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1,
Nodes=1
[0.00] NR_IRQS:51
[0.00] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
[0.07] pid_max: default: 32768 minimum: 301
[0.07] Mount-cache hash table entries: 512
[0.08] NET: Registered protocol family 16
[0.08] MIPS: machine is NETGEAR WNDR3700v4
[0.30] bio: create slab bio-0 at 0
[0.31] Switching to clocksource MIPS
[0.31] NET: Registered protocol family 2
[0.32] TCP established hash table entries: 1024 (order: 1, 8192
bytes)
[0.32] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[0.33] TCP: Hash tables configured (established 1024 bind 1024)
[0.33] TCP: reno registered
[0.34] UDP hash table entries: 256 (order: 0, 4096 bytes)
[0.34] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[0.35] NET: Registered protocol family 1
[0.37] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[0.37] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME)
(CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[0.38] msgmni has been set to 245
[ 

Re: [OpenWrt-Devel] MTD mounting problem on ar71xx and kernel 3.14.x.

[Paul Blazejowski]

¢¢êserial8250.0: ttyS0 at MMIO 0x1802 (irq = 11, base_baud =
250) is a 16550A
[0.45] console [ttyS0] enabled
[0.45] console [ttyS0] enabled
[0.45] bootconsole [early0] disabled
[0.45] bootconsole [early0] disabled
[0.46] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xf1
[0.47] nand: Micron NAND 128MiB 3,3V 8-bit
[0.47] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[0.48] Scanning device for bad blocks
[0.57] mtd: ar934x-nfc: skipping zero sized partition
[0.57] 11 cmdlinepart partitions found on MTD device ar934x-nfc
[0.58] Creating 11 MTD partitions on ar934x-nfc:
[0.58] 0x-0x0004 : u-boot
[0.59] 0x0004-0x0008 : u-boot-env
[0.60] 0x0008-0x000c : caldata
[0.60] 0x000c-0x0014 : pot
[0.61] 0x0014-0x0034 : language
[0.62] 0x0034-0x003c : config
[0.62] 0x003c-0x006c : traffic_meter
[0.63] 0x006c-0x008c : kernel
[0.64] 0x008c-0x07fc : ubi
[0.64] 0x006c-0x07fc : firmware
[1.24] random: nonblocking pool is initialized
[1.80] 0x07fc-0x0800 : caldata_backup
[1.83] switch0: Atheros AR8327 rev. 4 switch registered on
ag71xx-mdio.0
[3.04] libphy: ag71xx_mdio: probed
[3.67] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00
[uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]
[3.68] eth0: Atheros AG71xx at 0xb900, irq 4, mode:RGMII
[3.69] TCP: cubic registered
[3.69] NET: Registered protocol family 17
[3.70] 8021q: 802.1Q VLAN Support v1.8
[3.70] UBI: auto-attach mtd8
[3.71] UBI: attaching mtd8 to ubi0
[3.83] UBI error: scan_peb: bad image sequence number 1122340664
in PEB 97, expected 345540212
[3.84] Erase counter header dump:
[3.84]  magic  0x55424923
[3.85]  version1
[3.85]  ec 1
[3.85]  vid_hdr_offset 2048
[3.85]  data_offset4096
[3.86]  image_seq  1122340664
[3.86]  hdr_crc0xb8e2faee
[3.87] erase counter header hexdump:
[3.87] UBI error: ubi_attach_mtd_dev: failed to attach mtd8,
error -22
[3.88] UBI error: ubi_auto_attach: cannot attach mtd8
[3.88] UBIFS error (pid 1): ubifs_mount: cannot open
ubi0:rootfs, error -19
[3.89] VFS: Cannot open root device (null) or
unknown-block(0,0): error -6
[3.90] Please append a correct root= boot option; here are the
available partitions:
[3.91] 1f00 256 mtdblock0  (driver?)
[3.91] 1f01 256 mtdblock1  (driver?)
[3.92] 1f02 256 mtdblock2  (driver?)
[3.92] 1f03 512 mtdblock3  (driver?)
[3.93] 1f042048 mtdblock4  (driver?)
[3.93] 1f05 512 mtdblock5  (driver?)
[3.94] 1f063072 mtdblock6  (driver?)
[3.94] 1f072048 mtdblock7  (driver?)
[3.95] 1f08  121856 mtdblock8  (driver?)
[3.95] 1f09  123904 mtdblock9  (driver?)
[3.96] 1f0a 256 mtdblock10  (driver?)
[3.96] Kernel panic - not syncing: VFS: Unable to mount root fs
on unknown-block(0,0)



On Thu, 2014-10-02 at 12:45 -0400, Paul Blazejowski wrote:
 Hello all,
 
 A while back i have created a ticket
 (https://dev.openwrt.org/ticket/17609) detailing kernel 3.14.x failure
 to boot on ar71xx (wndr3700v4 router) platform. Today i have
 successfully used serial console attached to the router and got a boot
 log which shows a wrong checksum of kernel image when trying to attach
 it from UBI to MTD, please see output below ... i hope this helps in
 identifying and narrows the issue for a possible fix.
 
 Cheers!
 -paul
 
 U-Boot 1.1.4 (Jun 21 2012 - 11:09:33)
 
 DNI HW ID: 29763948 flash 128MB RAM 128MB U-boot dni29 V1.8
 
 
 DRAM:  128 MB
 Atheros on-chip NAND FLash Controller Driver, Version 0.1 (c) 2010
 Atheros Communications, Ltd.
 Ath Nand ID[87ff0178]: 2c:f1:80:95:02
 ONFI MICRON  MT29F1G08ABADAWP
 Micron NAND 128MiB 3,3V 8-bit [128MB]
 == NAND Parameters ==
 sc = 0x87ff0158 bbt = 0x87f68008 bbt_size = 0x100 nf_ctrl = 0x344
 page = 0x800 block = 0x2 oob = 0x40
 size = 128MB
 Setting 0xb8116290 to 0x4a942d0f
 Using default environment
 
 In:serial
 Out:   serial
 Err:   serial
 Net:   ag934x_enet_initialize...
  4096 bytes read: OK
 Fetching MAC Address from 0x87fe7928
  wasp  reset mask:c02300
 WASP   S17 PHY *
 : cfg1 0x8000 cfg2 0x7114
 eth0: 44:94:fc:73:9a:fc
 athrs17_reg_init: complete
 eth0 up
 eth0
 Hit any key to stop autoboot:  0
 dup 1 speed 1000
 
  Client starts...[Listening] for ADVERTISE...checksum bad
 checksum bad
 checksum bad
 checksum bad
 checksum bad
 Tchecksum bad

[OpenWrt-Devel] [Fwd: Re: [OpenWrt] #14076: layer7 netfilter module is not created in recent trunk]

[Paul Blazejowski]

Hi all,

Please have a look at this ticket, any comments would be welcome from
devs :-)

Hope to see this merged in...

thanks!
---BeginMessage---
#14076: layer7 netfilter module is not created in recent trunk
-+--
  Reporter:  duvi|  Owner:  developers
  Type:  defect  | Status:  new
  Priority:  normal  |  Milestone:  Chaos Calmer (trunk)
 Component:  kernel  |Version:  Trunk
Resolution:  |   Keywords:
-+--

Comment (by Diffie):

 I wanted to say that the patch in this ticket applies cleanly (with some
 offset) to 3.10.54 kernel, compiles and runs fine on ar71xx platform
 (netgear wndr3700v4). The system log does not show any more layer7 errors.

 This has been compile and run tested, hope this will go into BB final.

--
Ticket URL: https://dev.openwrt.org/ticket/14076#comment:30
OpenWrt http://openwrt.org
Opensource Wireless Router Technology
---End Message---


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 00/23] add 3.14 kernel support for ar71xx

[Paul Blazejowski]

no sir! after applying this one liner to my 3.14.13 (instead of the
3.14.12 kernel that Zhao used in his patches) and quick rebuild, my
wndr3700v4 will not boot; it shows 2 steady amber lights...

so this test fails as well ...next one please! ;P

On Sat, 2014-07-26 at 19:49 +0200, Rafał Miłecki wrote:
 On 26 July 2014 16:50, Zhao, Gang gang.zhao...@gmail.com wrote:
  On Sat, 2014-07-26 at 22:17:36 +0800, Zhao, Gang wrote:
  On Sat, 2014-07-26 at 12:00:21 +0800, Zhao, Gang wrote:
  On Sat, 2014-07-26 at 10:48:35 +0800, Zhao, Gang wrote:
  Tested on a tp-link wr703n, all seem okay.
 
  Oh, it seems there are some problems about the phy, all network cards
  are unusable :-( Will investigate it later. At least this patch set made
  a bootable kernel...
 
  The problem is it always says no carrier even if i plug the cable
  between router and my computer.
 
  [...]
  [ 2653.64] br-lan: port 1(eth0) entered disabled state
 
  The problem is about bridge. br-lan didn't bring the interface to
  forwarding mode. Keep going...
 
 Just guessing (really guessing!): maybe it's similar to the
 http://git.openwrt.org/?p=openwrt.git;a=commitdiff;h=6214350733ad29939ec827d242dbe2e9570ecb87
 ?
 


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

Hi John,

strange i did not receive your email, yet others from ml show up in my
inbox just fine...(case of forgotten cc: or reply to all?) anyways ...

just flashed the factory image i've built from r41792 and the changes
you've made in r41788 by spitting the 2 routers work just fine for me.

The router now correctly identifies as wndr3700v4 as reported in LuCI
and kernel dmesg as well as in sysinfo:

root@router:/tmp# cat sysinfo/*
wndr3700v4
NETGEAR WNDR3700v4

As for sysupgrade, it shows the checksum now and flashes OK.

It is nice to just upload the image into web interface and flash away
instead of cables,pins and other gadgets to get the firmware loaded ...

I thank you for your help in fixing this issue. case closed ;-)


Best Regards,
-paul


 hi,

 i pushed a patch in the hope that it will work. please test current
 trunk and tell if the problem is solved.

On Sun, 2014-07-20 at 11:56 -0400, Paul Blazejowski wrote:
 Hi,
 
 sorry your email got lost somehow on my end... And the machine hosting
 mailing list is down at the moment it seems.
 
 here is the info:
 
 root@router:~# cat /tmp/sysinfo/*
 wndr4300
 NETGEAR WNDR3700v4/WNDR4300
 
 
 thanks,
 -paul
 
 On Sat, 2014-07-19 at 14:52 -0400, Paul Blazejowski wrote:
  John,
  
  any update on this issue? i strongly believe that the hard-coded
  wndr4300 string somewhere in the source is the culprit of the problem
  since the wndr3700v4 board_detection is identified as wndr4300 thus the
  sysupgrade works for 4300 but not for 3700v4.
  
  Regards,
  -paul
  
  On Tue, 2014-06-24 at 23:15 +0200, John Crispin wrote:
   
   On 24/06/2014 22:43, Paul Blazejowski wrote:
i get The uploaded image file does not contain a supported format.
Make sure that you choose the generic image format for your
platform. from web interface.

this is what i have:

-rw-r--r-- 1 diffie diffie 8919040 2014-06-24 15:58 
bin/ar71xx/openwrt-ar71xx-nand-wndr3700v4-squashfs-sysupgrade.tar

should i push it from shell using sysupgrade script?

   
   it will work from shell, i will look into why it fails via webui.
   
   
   
   
   
thanks!


On Tue, 2014-06-24 at 22:32 +0200, John Crispin wrote:

On 24/06/2014 22:25, Paul Blazejowski wrote:
Hi again,

thanks for the tftp fix, flushing just became so much faster
and easier.

Tested trunk r41336 after your jffs2 fix and the image boots
fine, restored my configuration changes, rebooted the router
and all changes are saved now. I will post the working dmesg to
the ticket at https://dev.openwrt.org/ticket/16840 but it is
safe to say that you can close it ;-) now.

Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess
this is next on the list...


i tested 4300 and it works. you need to use the
*-ubi-sysupgrade.tar file.




Thank you, -paul

On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote:

On 24/06/2014 19:05, Paul Blazejowski wrote:
John,

Yes i use the reset with pin and from there i tftp the 
original firmware from netgear after that i go to the gui
and upload the open-wrt image because the router will not
accept the wndr3700v4 image (there's a cosmetic fix for
that, i created a patch that someone from the forums has
sent months ago to this list but it was never accepted...) 
https://dev.openwrt.org/ticket/16840

With that patch tftp'ing the 
openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works
without need to flash the original firmware.

If there's another method that can be used to flash the 
image(s) please let me know i would want to try any
alternative ways of flashing and could learn a thing or two
in the process as well ;-)

Thank you, -paul


Hi,

i just pushed the V vs v fix and another fix that removes
the jffs2 magic. i think this might have been the cause of
the problems. please retry with current trunk and let me know
if the problem is gone or still there

John ___ 
openwrt-devel mailing list openwrt-devel@lists.openwrt.org 
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
   
   
   

   ___ openwrt-devel
mailing list openwrt-devel@lists.openwrt.org 
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
   

   ___
openwrt-devel mailing list openwrt-devel@lists.openwrt.org 
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

Hi,

sorry your email got lost somehow on my end... And the machine hosting
mailing list is down at the moment it seems.

here is the info:

root@router:~# cat /tmp/sysinfo/*
wndr4300
NETGEAR WNDR3700v4/WNDR4300


thanks,
-paul

On Sat, 2014-07-19 at 14:52 -0400, Paul Blazejowski wrote:
 John,
 
 any update on this issue? i strongly believe that the hard-coded
 wndr4300 string somewhere in the source is the culprit of the problem
 since the wndr3700v4 board_detection is identified as wndr4300 thus the
 sysupgrade works for 4300 but not for 3700v4.
 
 Regards,
 -paul
 
 On Tue, 2014-06-24 at 23:15 +0200, John Crispin wrote:
  
  On 24/06/2014 22:43, Paul Blazejowski wrote:
   i get The uploaded image file does not contain a supported format.
   Make sure that you choose the generic image format for your
   platform. from web interface.
   
   this is what i have:
   
   -rw-r--r-- 1 diffie diffie 8919040 2014-06-24 15:58 
   bin/ar71xx/openwrt-ar71xx-nand-wndr3700v4-squashfs-sysupgrade.tar
   
   should i push it from shell using sysupgrade script?
   
  
  it will work from shell, i will look into why it fails via webui.
  
  
  
  
  
   thanks!
   
   
   On Tue, 2014-06-24 at 22:32 +0200, John Crispin wrote:
   
   On 24/06/2014 22:25, Paul Blazejowski wrote:
   Hi again,
   
   thanks for the tftp fix, flushing just became so much faster
   and easier.
   
   Tested trunk r41336 after your jffs2 fix and the image boots
   fine, restored my configuration changes, rebooted the router
   and all changes are saved now. I will post the working dmesg to
   the ticket at https://dev.openwrt.org/ticket/16840 but it is
   safe to say that you can close it ;-) now.
   
   Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess
   this is next on the list...
   
   
   i tested 4300 and it works. you need to use the
   *-ubi-sysupgrade.tar file.
   
   
   
   
   Thank you, -paul
   
   On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote:
   
   On 24/06/2014 19:05, Paul Blazejowski wrote:
   John,
   
   Yes i use the reset with pin and from there i tftp the 
   original firmware from netgear after that i go to the gui
   and upload the open-wrt image because the router will not
   accept the wndr3700v4 image (there's a cosmetic fix for
   that, i created a patch that someone from the forums has
   sent months ago to this list but it was never accepted...) 
   https://dev.openwrt.org/ticket/16840
   
   With that patch tftp'ing the 
   openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works
   without need to flash the original firmware.
   
   If there's another method that can be used to flash the 
   image(s) please let me know i would want to try any
   alternative ways of flashing and could learn a thing or two
   in the process as well ;-)
   
   Thank you, -paul
   
   
   Hi,
   
   i just pushed the V vs v fix and another fix that removes
   the jffs2 magic. i think this might have been the cause of
   the problems. please retry with current trunk and let me know
   if the problem is gone or still there
   
   John ___ 
   openwrt-devel mailing list openwrt-devel@lists.openwrt.org 
   https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
  
  
  
   
  ___ openwrt-devel
   mailing list openwrt-devel@lists.openwrt.org 
   https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
  
   
  ___
   openwrt-devel mailing list openwrt-devel@lists.openwrt.org 
   https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

John,

any update on this issue? i strongly believe that the hard-coded
wndr4300 string somewhere in the source is the culprit of the problem
since the wndr3700v4 board_detection is identified as wndr4300 thus the
sysupgrade works for 4300 but not for 3700v4.

Regards,
-paul

On Tue, 2014-06-24 at 23:15 +0200, John Crispin wrote:
 
 On 24/06/2014 22:43, Paul Blazejowski wrote:
  i get The uploaded image file does not contain a supported format.
  Make sure that you choose the generic image format for your
  platform. from web interface.
  
  this is what i have:
  
  -rw-r--r-- 1 diffie diffie 8919040 2014-06-24 15:58 
  bin/ar71xx/openwrt-ar71xx-nand-wndr3700v4-squashfs-sysupgrade.tar
  
  should i push it from shell using sysupgrade script?
  
 
 it will work from shell, i will look into why it fails via webui.
 
 
 
 
 
  thanks!
  
  
  On Tue, 2014-06-24 at 22:32 +0200, John Crispin wrote:
  
  On 24/06/2014 22:25, Paul Blazejowski wrote:
  Hi again,
  
  thanks for the tftp fix, flushing just became so much faster
  and easier.
  
  Tested trunk r41336 after your jffs2 fix and the image boots
  fine, restored my configuration changes, rebooted the router
  and all changes are saved now. I will post the working dmesg to
  the ticket at https://dev.openwrt.org/ticket/16840 but it is
  safe to say that you can close it ;-) now.
  
  Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess
  this is next on the list...
  
  
  i tested 4300 and it works. you need to use the
  *-ubi-sysupgrade.tar file.
  
  
  
  
  Thank you, -paul
  
  On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote:
  
  On 24/06/2014 19:05, Paul Blazejowski wrote:
  John,
  
  Yes i use the reset with pin and from there i tftp the 
  original firmware from netgear after that i go to the gui
  and upload the open-wrt image because the router will not
  accept the wndr3700v4 image (there's a cosmetic fix for
  that, i created a patch that someone from the forums has
  sent months ago to this list but it was never accepted...) 
  https://dev.openwrt.org/ticket/16840
  
  With that patch tftp'ing the 
  openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works
  without need to flash the original firmware.
  
  If there's another method that can be used to flash the 
  image(s) please let me know i would want to try any
  alternative ways of flashing and could learn a thing or two
  in the process as well ;-)
  
  Thank you, -paul
  
  
  Hi,
  
  i just pushed the V vs v fix and another fix that removes
  the jffs2 magic. i think this might have been the cause of
  the problems. please retry with current trunk and let me know
  if the problem is gone or still there
  
  John ___ 
  openwrt-devel mailing list openwrt-devel@lists.openwrt.org 
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 
 
 
  
 ___ openwrt-devel
  mailing list openwrt-devel@lists.openwrt.org 
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 
  
 ___
  openwrt-devel mailing list openwrt-devel@lists.openwrt.org 
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

On Wed, 2014-06-25 at 08:09 +0200, John Crispin wrote:
 
 On 25/06/2014 08:02, Paul Blazejowski wrote:
  On Wed, 2014-06-25 at 07:57 +0200, John Crispin wrote:
  Hi,
  
  can someone with a 3700v4 run cat /tmp/sysinfo/* on a 3700 ?
  
  the sysupgrade fails because the board id is not added yet in
  the upgrade script. however i fail to figure out what id it gets
  from the ar71xx.sh script
  
  John
  
  
  Good morning John
  
  on my 3700v4 i get this:
  
  root@router:~# cat /tmp/sysinfo/* wndr4300 NETGEAR
  WNDR3700v4/WNDR4300
  
  hope this helps!
  
  -paul
  
  
 
 and which sysupgrade file fails in luci ? if the id is 4300 then you
 should simply use the 4300 tar file for luci sysupgrade
 
   John
 

i am building new image before going to sleep but both of them failed
when i tried earlier (r41336)

Adam confirmed that the 4300 sysupgrade worked great  on his wndr4300
router so i guess this is isolated to 3700v4 now (although the images
are the same in length)...

 
 
  
  On 25/06/2014 06:27, Adam Kuklycz wrote:
  Hi all,
  
  I've flashed my Netgear WNDR4300 with trunk r41336 and have run
  a series of tests.
  
  Everything looks great!  I can restore backed up settings, I
  can configure it from scratch too should I desire.
  
  Sysupgrade works fine on my WNDR4300 via the web UI.  Paul if 
  you're still having issues with this on your WNDR3700v4 it may
  be specific to that model; I do not have one of these to test
  on unfortunately. But sysupgrade on the WNDR4300 works and
  works well. All settings are kept when sysupgrading too.
  
  If it helps Paul out I can email him my config file, write me 
  directly for it; that should eliminate any mistakes that have
  been overlooked. Easy to do.
  
  Will run the router for a few hours on the test bench and do
  some traffic through it, should that play nice then it's
  problems resolved on my end :)
  
  Cheers Adam
  
  
  On 25/06/14 13:14, Paul Blazejowski wrote:
  Adam,
  
  what do you know? hehehe when one sleeps another fixes
  things ;-)
  
  so far so good, my router has been up for few hours without 
  problems... there's still issue with the sysupgrade image
  that John is already aware of ... and may have a fix for us
  to test ... one fix at a time they say.
  
  glad we made much progress today!
  
  thank you all!
  
  
  On Wed, 2014-06-25 at 00:07 +, Adam Kuklycz wrote:
  Geez, it must be true that you should only sleep when
  you're dead...damn Aussie time zones...
  
  I'll test with latest trunk as well  will confirm.  But
  looks promising!
  
  
  
  -Original Message- From: openwrt-devel 
  [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf
  Of Paul Blazejowski Sent: Wednesday, 25 June 2014 6:27 AM
  To: John Crispin Cc: openwrt-devel@lists.openwrt.org
  Subject: Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke
  ubifs on Netgear WNDR3700v4/4300.
  
  sorry i meant https://dev.openwrt.org/ticket/16803 the
  previous one is closed for good ;-)
  
  
  On Tue, 2014-06-24 at 16:25 -0400, Paul Blazejowski wrote:
  Hi again,
  
  thanks for the tftp fix, flushing just became so much
  faster and easier.
  
  Tested trunk r41336 after your jffs2 fix and the image
  boots fine, restored my configuration changes, rebooted
  the router and all changes are saved now. I will post the
  working dmesg to the ticket at
  https://dev.openwrt.org/ticket/16840 but it is safe to
  say that you can close it ;-) now.
  
  Sysupgrade image(s) for 3700v4 and 4300 do not work now, 
  guess this is next on the list...
  
  Thank you, -paul
  
  On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote:
  On 24/06/2014 19:05, Paul Blazejowski wrote:
  John,
  
  Yes i use the reset with pin and from there i tftp
  the original firmware from netgear after that i go to
  the gui and upload the open-wrt image because the
  router will not accept the wndr3700v4 image (there's
  a cosmetic fix for that, i created a patch that
  someone from the forums has sent months ago to this
  list but it was never accepted...)
  https://dev.openwrt.org/ticket/16840
  
  With that patch tftp'ing the 
  openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works 
  without need to flash the original firmware.
  
  If there's another method that can be used to flash
  the image(s) please let me know i would want to try
  any alternative ways of flashing and could learn a
  thing or two in the process as well ;-)
  
  Thank you, -paul
  
  Hi,
  
  i just pushed the V vs v fix and another fix that
  removes the jffs2 magic. i think this might have been
  the cause of the problems. please retry with current
  trunk and let me know if the problem is gone or still
  there
  
  John ___ 
  openwrt-devel mailing list
  openwrt-devel@lists.openwrt.org 
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 
 
 
  
 ___
  openwrt-devel mailing list
  openwrt

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

Hi John,

yes i know my way around ;-)  so please do share the patch so i can
test...

Thank you,
-paul


On Tue, 2014-06-24 at 09:36 +0200, John Crispin wrote:
 
 On 23/06/2014 20:22, Paul Blazejowski wrote:
  Hello list,
  
  Have found bug in the ubifs component when mounting images on 
  wndr3700v4/4300 routers. This happens in trunk builds after r41130
  but does not happen before r41118.
  
  Please take a look at bug https://dev.openwrt.org/ticket/16803 i
  have filed on this issue.
  
  Unfortunately i do not have any fixes for this but i am willing to
  test patches and debug in hopes of getting this fixed.
  
  On a side note, sysupgrade image for wndr4300 does work from the
  web interface on my 3700v4 router but the wndr3700v4 image does
  not. Guess one bugat a time ;-).
  
  cheerios, -paulb
  
  
 
 Hi,
 
 do you know how to build your own image and could you test a patch if
 i send one ?
 
   John
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

John,

Yes i use the reset with pin and from there i tftp the original firmware
from netgear after that i go to the gui and upload the open-wrt image
because the router will not accept the wndr3700v4 image (there's a
cosmetic fix for that, i created a patch that someone from the forums
has sent months ago to this list but it was never accepted...)
https://dev.openwrt.org/ticket/16840

With that patch tftp'ing the
openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works without need to
flash the original firmware.

If there's another method that can be used to flash the image(s) please
let me know i would want to try any alternative ways of flashing and
could learn a thing or two in the process as well ;-)

Thank you,
-paul

On Tue, 2014-06-24 at 18:48 +0200, John Crispin wrote:
 Hi,
 
 On 23/06/2014 20:22, Paul Blazejowski wrote:
  Hello list,
  
  Have found bug in the ubifs component when mounting images on 
  wndr3700v4/4300 routers. This happens in trunk builds after r41130
  but does not happen before r41118.
  
  Please take a look at bug https://dev.openwrt.org/ticket/16803 i
  have filed on this issue.
  
  Unfortunately i do not have any fixes for this but i am willing to
  test patches and debug in hopes of getting this fixed.
 
 looking at that log it looks like you flashed different to me :) do
 you perhaps use the recovery method ?
 
 i am currently using an initramfs which i boot and then i sysupgrade
 from there. because of this i dont see the 0xdeadc0de that you see as
 it is only in the ubi file --
 
 echo -ne '\xde\xad\xc0\xde'  $(KDIR_TMP)/jffs2.eof
 $(call
 ubinize,ubinize-$(9).ini,$(KDIR_TMP),$(KDIR_TMP)/$(2)-root.ubi,128KiB,2048,-E
 5)
 
 however to test further i need to know how you flashed :)
 
   John
 
  
  On a side note, sysupgrade image for wndr4300 does work from the
  web interface on my 3700v4 router but the wndr3700v4 image does
  not. Guess one bugat a time ;-).
  
  cheerios, -paulb
  
  
 
 
 
 
  
  ___ openwrt-devel
  mailing list openwrt-devel@lists.openwrt.org 
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
  
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

Hi again,

thanks for the tftp fix, flushing just became so much faster and easier.

Tested trunk r41336 after your jffs2 fix and the image boots fine,
restored my configuration changes, rebooted the router and all changes
are saved now. I will post the working dmesg to the ticket at
https://dev.openwrt.org/ticket/16840 but it is safe to say that you can
close it ;-) now.

Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess this is
next on the list...

Thank you,
-paul

On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote:
 
 On 24/06/2014 19:05, Paul Blazejowski wrote:
  John,
  
  Yes i use the reset with pin and from there i tftp the original
  firmware from netgear after that i go to the gui and upload the
  open-wrt image because the router will not accept the wndr3700v4
  image (there's a cosmetic fix for that, i created a patch that
  someone from the forums has sent months ago to this list but it was
  never accepted...) https://dev.openwrt.org/ticket/16840
  
  With that patch tftp'ing the 
  openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works without need
  to flash the original firmware.
  
  If there's another method that can be used to flash the image(s)
  please let me know i would want to try any alternative ways of
  flashing and could learn a thing or two in the process as well ;-)
  
  Thank you, -paul
 
 
 Hi,
 
 i just pushed the V vs v fix and another fix that removes the jffs2
 magic. i think this might have been the cause of the problems. please
 retry with current trunk and let me know if the problem is gone or
 still there
 
   John
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

sorry i meant https://dev.openwrt.org/ticket/16803 the previous one is
closed for good ;-)


On Tue, 2014-06-24 at 16:25 -0400, Paul Blazejowski wrote:
 Hi again,
 
 thanks for the tftp fix, flushing just became so much faster and easier.
 
 Tested trunk r41336 after your jffs2 fix and the image boots fine,
 restored my configuration changes, rebooted the router and all changes
 are saved now. I will post the working dmesg to the ticket at
 https://dev.openwrt.org/ticket/16840 but it is safe to say that you can
 close it ;-) now.
 
 Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess this is
 next on the list...
 
 Thank you,
 -paul
 
 On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote:
  
  On 24/06/2014 19:05, Paul Blazejowski wrote:
   John,
   
   Yes i use the reset with pin and from there i tftp the original
   firmware from netgear after that i go to the gui and upload the
   open-wrt image because the router will not accept the wndr3700v4
   image (there's a cosmetic fix for that, i created a patch that
   someone from the forums has sent months ago to this list but it was
   never accepted...) https://dev.openwrt.org/ticket/16840
   
   With that patch tftp'ing the 
   openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works without need
   to flash the original firmware.
   
   If there's another method that can be used to flash the image(s)
   please let me know i would want to try any alternative ways of
   flashing and could learn a thing or two in the process as well ;-)
   
   Thank you, -paul
  
  
  Hi,
  
  i just pushed the V vs v fix and another fix that removes the jffs2
  magic. i think this might have been the cause of the problems. please
  retry with current trunk and let me know if the problem is gone or
  still there
  
  John
  ___
  openwrt-devel mailing list
  openwrt-devel@lists.openwrt.org
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

i get The uploaded image file does not contain a supported format. Make
sure that you choose the generic image format for your platform. from
web interface.

this is what i have:

-rw-r--r-- 1 diffie diffie 8919040 2014-06-24 15:58
bin/ar71xx/openwrt-ar71xx-nand-wndr3700v4-squashfs-sysupgrade.tar

should i push it from shell using sysupgrade script?

thanks!


On Tue, 2014-06-24 at 22:32 +0200, John Crispin wrote:
 
 On 24/06/2014 22:25, Paul Blazejowski wrote:
  Hi again,
  
  thanks for the tftp fix, flushing just became so much faster and
  easier.
  
  Tested trunk r41336 after your jffs2 fix and the image boots fine, 
  restored my configuration changes, rebooted the router and all
  changes are saved now. I will post the working dmesg to the ticket
  at https://dev.openwrt.org/ticket/16840 but it is safe to say that
  you can close it ;-) now.
  
  Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess this
  is next on the list...
  
 
 i tested 4300 and it works. you need to use the *-ubi-sysupgrade.tar file.
 
 
 
 
  Thank you, -paul
  
  On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote:
  
  On 24/06/2014 19:05, Paul Blazejowski wrote:
  John,
  
  Yes i use the reset with pin and from there i tftp the
  original firmware from netgear after that i go to the gui and
  upload the open-wrt image because the router will not accept
  the wndr3700v4 image (there's a cosmetic fix for that, i
  created a patch that someone from the forums has sent months
  ago to this list but it was never accepted...)
  https://dev.openwrt.org/ticket/16840
  
  With that patch tftp'ing the 
  openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works without
  need to flash the original firmware.
  
  If there's another method that can be used to flash the
  image(s) please let me know i would want to try any alternative
  ways of flashing and could learn a thing or two in the process
  as well ;-)
  
  Thank you, -paul
  
  
  Hi,
  
  i just pushed the V vs v fix and another fix that removes the
  jffs2 magic. i think this might have been the cause of the
  problems. please retry with current trunk and let me know if the
  problem is gone or still there
  
  John ___ 
  openwrt-devel mailing list openwrt-devel@lists.openwrt.org 
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
  
  
  ___ openwrt-devel
  mailing list openwrt-devel@lists.openwrt.org 
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

On Tue, 2014-06-24 at 23:15 +0200, John Crispin wrote:
 
 On 24/06/2014 22:43, Paul Blazejowski wrote:
  i get The uploaded image file does not contain a supported format.
  Make sure that you choose the generic image format for your
  platform. from web interface.
  
  this is what i have:
  
  -rw-r--r-- 1 diffie diffie 8919040 2014-06-24 15:58 
  bin/ar71xx/openwrt-ar71xx-nand-wndr3700v4-squashfs-sysupgrade.tar
  
  should i push it from shell using sysupgrade script?
  
 
 it will work from shell, i will look into why it fails via webui.

guess not ;-(


root@router:/tmp# sysupgrade -v -T
openwrt-ar71xx-nand-wndr3700v4-squashfs-sysupgrade.tar 
Invalid sysupgrade file.
Image check 'platform_check_image' failed.

 
 
 
 
 
  thanks!
  
  
  On Tue, 2014-06-24 at 22:32 +0200, John Crispin wrote:
  
  On 24/06/2014 22:25, Paul Blazejowski wrote:
  Hi again,
  
  thanks for the tftp fix, flushing just became so much faster
  and easier.
  
  Tested trunk r41336 after your jffs2 fix and the image boots
  fine, restored my configuration changes, rebooted the router
  and all changes are saved now. I will post the working dmesg to
  the ticket at https://dev.openwrt.org/ticket/16840 but it is
  safe to say that you can close it ;-) now.
  
  Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess
  this is next on the list...
  
  
  i tested 4300 and it works. you need to use the
  *-ubi-sysupgrade.tar file.
  
  
  
  
  Thank you, -paul
  
  On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote:
  
  On 24/06/2014 19:05, Paul Blazejowski wrote:
  John,
  
  Yes i use the reset with pin and from there i tftp the 
  original firmware from netgear after that i go to the gui
  and upload the open-wrt image because the router will not
  accept the wndr3700v4 image (there's a cosmetic fix for
  that, i created a patch that someone from the forums has
  sent months ago to this list but it was never accepted...) 
  https://dev.openwrt.org/ticket/16840
  
  With that patch tftp'ing the 
  openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works
  without need to flash the original firmware.
  
  If there's another method that can be used to flash the 
  image(s) please let me know i would want to try any
  alternative ways of flashing and could learn a thing or two
  in the process as well ;-)
  
  Thank you, -paul
  
  
  Hi,
  
  i just pushed the V vs v fix and another fix that removes
  the jffs2 magic. i think this might have been the cause of
  the problems. please retry with current trunk and let me know
  if the problem is gone or still there
  
  John ___ 
  openwrt-devel mailing list openwrt-devel@lists.openwrt.org 
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 
 
 
  
 ___ openwrt-devel
  mailing list openwrt-devel@lists.openwrt.org 
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 
  
 ___
  openwrt-devel mailing list openwrt-devel@lists.openwrt.org 
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

Adam,

what do you know? hehehe when one sleeps another fixes things ;-)

so far so good, my router has been up for few hours without problems...
there's still issue with the sysupgrade image that John is already aware
of ... and may have a fix for us to test ... one fix at a time they say.

glad we made much progress today!

thank you all!


On Wed, 2014-06-25 at 00:07 +, Adam Kuklycz wrote:
 Geez, it must be true that you should only sleep when you're dead...damn 
 Aussie time zones...
 
 I'll test with latest trunk as well  will confirm.  But looks promising!
 
 
 
 -Original Message-
 From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On 
 Behalf Of Paul Blazejowski
 Sent: Wednesday, 25 June 2014 6:27 AM
 To: John Crispin
 Cc: openwrt-devel@lists.openwrt.org
 Subject: Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear 
 WNDR3700v4/4300.
 
 sorry i meant https://dev.openwrt.org/ticket/16803 the previous one is closed 
 for good ;-)
 
 
 On Tue, 2014-06-24 at 16:25 -0400, Paul Blazejowski wrote:
  Hi again,
  
  thanks for the tftp fix, flushing just became so much faster and easier.
  
  Tested trunk r41336 after your jffs2 fix and the image boots fine, 
  restored my configuration changes, rebooted the router and all changes 
  are saved now. I will post the working dmesg to the ticket at
  https://dev.openwrt.org/ticket/16840 but it is safe to say that you 
  can close it ;-) now.
  
  Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess this is 
  next on the list...
  
  Thank you,
  -paul
  
  On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote:
   
   On 24/06/2014 19:05, Paul Blazejowski wrote:
John,

Yes i use the reset with pin and from there i tftp the original 
firmware from netgear after that i go to the gui and upload the 
open-wrt image because the router will not accept the wndr3700v4 
image (there's a cosmetic fix for that, i created a patch that 
someone from the forums has sent months ago to this list but it 
was never accepted...) https://dev.openwrt.org/ticket/16840

With that patch tftp'ing the
openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works without need 
to flash the original firmware.

If there's another method that can be used to flash the image(s) 
please let me know i would want to try any alternative ways of 
flashing and could learn a thing or two in the process as well ;-)

Thank you, -paul
   
   
   Hi,
   
   i just pushed the V vs v fix and another fix that removes the jffs2 
   magic. i think this might have been the cause of the problems. 
   please retry with current trunk and let me know if the problem is 
   gone or still there
   
 John
   ___
   openwrt-devel mailing list
   openwrt-devel@lists.openwrt.org
   https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
  ___
  openwrt-devel mailing list
  openwrt-devel@lists.openwrt.org
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.

[Paul Blazejowski]

Hello list,

Have found bug in the ubifs component when mounting images on
wndr3700v4/4300 routers. This happens in trunk builds after r41130 but
does not happen before r41118.

Please take a look at bug https://dev.openwrt.org/ticket/16803 i have
filed on this issue.

Unfortunately i do not have any fixes for this but i am willing to test
patches and debug in hopes of getting this fixed.

On a side note, sysupgrade image for wndr4300 does work from the web
interface on my 3700v4 router but the wndr3700v4 image does not. Guess
one bugat a time ;-).

cheerios,
-paulb


signature.asc
Description: This is a digitally signed message part
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel