[LEDE-DEV] [PATCH v2] mt7621: Fix LAN port order of WeVO W2914NS v2

[perillamint]

From: "Yong-hyu, Ban" 

Signed-off-by: Yong-hyu, Ban 
---

Changelog:
v2: Fix signed-off name to real name.

 target/linux/ramips/base-files/etc/board.d/02_network | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/target/linux/ramips/base-files/etc/board.d/02_network 
b/target/linux/ramips/base-files/etc/board.d/02_network
index e3e6550..9701b5a 100755
--- a/target/linux/ramips/base-files/etc/board.d/02_network
+++ b/target/linux/ramips/base-files/etc/board.d/02_network
@@ -87,7 +87,6 @@ ramips_setup_interfaces()
sap-g3200u3|\
sk-wb8|\
vr500|\
-   w2914nsv2|\
wf-2881|\
witi|\
wl-wn575a3|\
@@ -242,6 +241,10 @@ ramips_setup_interfaces()
ucidef_add_switch "switch0" \
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "5@eth0"
;;
+   w2914nsv2)
+   ucidef_add_switch "switch0" \
+   "0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "4:wan" "6@eth0"
+   ;;
wcr-150gn)
ucidef_add_switch "switch0" \
"0:lan" "6t@eth0"
-- 
2.10.2


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] mt7621: Fix LAN port order of WeVO W2914NS v2

[perillamint]

Signed-off-by: perillamint 
---
 target/linux/ramips/base-files/etc/board.d/02_network | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/target/linux/ramips/base-files/etc/board.d/02_network 
b/target/linux/ramips/base-files/etc/board.d/02_network
index e3e6550..9701b5a 100755
--- a/target/linux/ramips/base-files/etc/board.d/02_network
+++ b/target/linux/ramips/base-files/etc/board.d/02_network
@@ -87,7 +87,6 @@ ramips_setup_interfaces()
sap-g3200u3|\
sk-wb8|\
vr500|\
-   w2914nsv2|\
wf-2881|\
witi|\
wl-wn575a3|\
@@ -242,6 +241,10 @@ ramips_setup_interfaces()
ucidef_add_switch "switch0" \
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "5@eth0"
;;
+   w2914nsv2)
+   ucidef_add_switch "switch0" \
+   "0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "4:wan" "6@eth0"
+   ;;
wcr-150gn)
ucidef_add_switch "switch0" \
"0:lan" "6t@eth0"
-- 
2.10.2


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] ath10k firmware crashes in mesh mode on QCA9880

[Benjamin Morgan]

Just tried 10.2.4.70.58 firmware that you linked to and it still crashes:

[  131.568989] ath10k_pci :01:00.0: firmware crashed! (uuid 
1838347e-9380-4a26-ac9d-2963ee95968b)
[  131.578124] ath10k_pci :01:00.0: qca988x hw2.0 target 0x4100016c 
chip_id 0x043202ff sub :
[  131.587491] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 
tracing 0 dfs 1 testmode 1
[  131.600521] ath10k_pci :01:00.0: firmware ver 10.2.4.70.58 api 5 
features no-p2p,raw-mode,mfp crc32 e1af076f
[  131.610899] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A 
crc32 bebc7c08
[  131.618325] ath10k_pci :01:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 
cal file max-sta 128 raw 0 hwcrypto 1

[  131.629965] ath10k_pci :01:00.0: firmware register dump:
[  131.635728] ath10k_pci :01:00.0: [00]: 0x4100016C 0x15B3 
0x009A45AF 0x00955B31
[  131.643761] ath10k_pci :01:00.0: [04]: 0x009A45AF 0x00060130 
0x0002 0x00439E98
[  131.651806] ath10k_pci :01:00.0: [08]: 0x0044110C 0x00442074 
0x00407120 0x004436CC
[  131.659852] ath10k_pci :01:00.0: [12]: 0x0009 0x 
0x009A3550 0x009A355E
[  131.667892] ath10k_pci :01:00.0: [16]: 0x00958080 0x009A31D6 
0x 0x
[  131.675936] ath10k_pci :01:00.0: [20]: 0x409A45AF 0x0040AAC4 
0x0040AC60 0x0040AC09
[  131.683968] ath10k_pci :01:00.0: [24]: 0x809A44F2 0x0040AB24 
0x0040 0xC09A45AF
[  131.692013] ath10k_pci :01:00.0: [28]: 0x809A3A16 0x0040AB84 
0x0044110C 0x00442074
[  131.700056] ath10k_pci :01:00.0: [32]: 0x809A601A 0x0040ABB4 
0x0044110C 0x00407120
[  131.708100] ath10k_pci :01:00.0: [36]: 0x809A2EA4 0x0040ABF4 
0x0040AC14 0x1580
[  131.716143] ath10k_pci :01:00.0: [40]: 0x80990F63 0x0040AD04 
0x009C6458 0x004436CC
[  131.724175] ath10k_pci :01:00.0: [44]: 0x80998520 0x0040AD64 
0x004208FC 0x00439E4C
[  131.732220] ath10k_pci :01:00.0: [48]: 0x8099AEA5 0x0040AD84 
0x004208FC 0x00425874
[  131.740263] ath10k_pci :01:00.0: [52]: 0x809BFC39 0x0040AEE4 
0x00424FE8 0x0002
[  131.748306] ath10k_pci :01:00.0: [56]: 0x80940F18 0x0040AF14 
0x0004 0x004039D0

[  131.857076] ieee80211 phy0: Hardware restart was requested
[  131.862705] ath10k_pci :01:00.0: failed to synchronize monitor 
vdev 1 stop: -143

[  131.870594] ath10k_pci :01:00.0: failed to stop monitor vdev: -143

~Benjamin

On 11/30/2016 11:09 PM, Mohammed Shafi Shajakhan wrote:

Hi,

On Tue, Nov 29, 2016 at 11:22:12AM -0800, Benjamin Morgan wrote:

When we try to transmit traffic (ping) between two meshed ath10k
devices running latest lede we keep experiencing ath10k firmware
crashes. This seems to only happen when running in 802.11n/ac mode
but not in 802.11a/g mode. Also, from the station dumps it appears
that management traffic is flowing between the devices, however when
we try to send unicast data traffic the firmware crashes
immediately.

[shafi] Did you get a chance to try with the below firmware as well
https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/hw2.0/10.2.4.70/firmware-5.bin_10.2.4.70.58


Platform: Archer C7 AC1750 v2
Software Image: LEDE (HEAD, r2299) Commit: 
https://github.com/lede-project/source/commit/d596c21ebd5a3e6ce933eff3e51989031e4b1d58

Crypto: wpa_supplicant
wpa_supplicant-wlan0.conf
network={
ssid="bmorgan_lede_mesh"
key_mgmt=SAE
mode=5
frequency=5180
psk="meshpassword"
}

Backports Verstion:
[9.818007] Loading modules backported from Linux version
wt-2016-10-03-1-g6fcb1a6
[9.825736] Backport generated by backports.git
backports-20160324-9-g0e38f5c

​​Ath10k Initialization on Station A (dmesg)
[9.896715] PCI: Enabling device :01:00.0 ( -> 0002)
[9.902622] ath10k_pci :01:00.0: pci irq legacy oper_irq_mode
1 irq_mode 0 reset_mode 0
[   10.123734] ath10k_pci :01:00.0: Direct firmware load for
ath10k/pre-cal-pci-:01:00.0.bin failed with error -2
[   10.134620] ath10k_pci :01:00.0: Falling back to user helper
[   10.287680] firmware ath10k!pre-cal-pci-:01:00.0.bin:
firmware_loading_store: map pages failed
[   10.622789] ath10k_pci :01:00.0: qca988x hw2.0 target
0x4100016c chip_id 0x043202ff sub :
[   10.632184] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
tracing 0 dfs 1 testmode 1
[   10.645231] ath10k_pci :01:00.0: firmware ver 10.2.4.70.54
api 5 features no-p2p,raw-mode,mfp crc32 9d340dd9
[   10.655660] ath10k_pci :01:00.0: Direct firmware load for
ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[   10.666264] ath10k_pci :01:00.0: Falling back to user helper
[   10.747925] firmware ath10k!QCA988X!hw2.0!board-2.bin:
firmware_loading_store: map pages failed
[   11.011123] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A
crc32 bebc7c08
[   12.155224] ath10k_pci :01:00.0: htt-ver 2.1 wmi-op 5 htt-op
2 cal file max-sta 128 raw 0 hwcrypto 1

Station A (wlan0):
18:A6:F7:23:6E:66
10.230.5.41

Station B (wlan0):
18:a6:f7:26:0f:21
10.230.5.42

Station Dump on Station A before ping:
Station 

[LEDE-DEV] [PATCH] brcm63xx: fix BCM6368 switch hw LEDs

[Daniel Gonzalez Cabanelas]

Prevent from erasing the pinmux of HW ephy LEDs in BCM6368

In BCM6368 CFE configures the HW controled LEDs for the switch
by setting the required GPIO pinmux. But in OpenWrt when the 
peripherals are initialized, the code is erasing the pinmux previously
configured by CFE. 

Just don't erase those bits to let the LEDs blink with LAN activity.

Signed-off-by: Daniel Gonzalez Cabanelas 
diff --git 
a/target/linux/brcm63xx/patches-4.4/805-bcm6368-dont_erase_ephy_ledmux.patch 
b/target/linux/brcm63xx/patches-4.4/805-bcm6368-dont_erase_ephy_ledmux.patch
new file mode 100644
index 000..84208b6
--- /dev/null
+++ b/target/linux/brcm63xx/patches-4.4/805-bcm6368-dont_erase_ephy_ledmux.patch
@@ -0,0 +1,18 @@
+--- a/arch/mips/bcm63xx/boards/board_common.c
 b/arch/mips/bcm63xx/boards/board_common.c
+@@ -81,6 +81,15 @@
+* inside arch_initcall */
+   val = 0;
+ 
++  if (board.has_enetsw && BCMCPU_IS_6368()) {
++  /* Don't erase EPHY LEDmux! */
++  val |= bcm_gpio_readl(GPIO_MODE_REG) & (
++  GPIO_MODE_6368_EPHY0_LED |
++  GPIO_MODE_6368_EPHY1_LED |
++  GPIO_MODE_6368_EPHY2_LED |
++  GPIO_MODE_6368_EPHY3_LED);
++  }
++
+ #ifdef CONFIG_PCI
+   if (board.has_pci) {
+   bcm63xx_pci_enabled = 1;


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] enhanced 3G support

[Giuseppe Lippolis]

Dear Bjørn,
please join the discussion directly on the github code:

https://github.com/lede-project/source/pull/585

Bye.


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [source] procd: update to the latest version, fixes killing jailed processes

[Etienne Champetier]

Hi Felix,

2016-12-02 6:32 GMT-08:00 Felix Fietkau :
>
> Hi Etienne,
>
> what value would you suggest as a default? I should probably make it
> configurable on the command line as well.

For service handling data we might loose data, so maybe no default at
all unless it's configured.
I would also change the debug message to a warning or error so this
end up in system log for easier debugging

Regards
Etienne

>
> - Felix
>
> On 2016-12-02 15:25, Etienne Champetier wrote:
> > Hi Felix,
> >
> > Just had a look at the code and 1sec of timeout seems a bit low for me
> > for an hard coded value, and might break slow but well behaving application
> >
> > My 2 cents,
> > Regards,
> > Etienne
> >
> > Le 2 déc. 2016 4:55 AM, "LEDE Commits"  > > a écrit :
> >>
> >> nbd pushed a commit to source.git, branch master:
> >> https://git.lede-project.org/1947cf36ba7556c4678beca593ad334b13b870cd
> >>
> >> commit 1947cf36ba7556c4678beca593ad334b13b870cd
> >> Author: Felix Fietkau >
> >> AuthorDate: Fri Dec 2 13:55:12 2016 +0100
> >>
> >> procd: update to the latest version, fixes killing jailed processes
> >>
> >> Signed-off-by: Felix Fietkau >
> >> ---
> >>  package/system/procd/Makefile | 6 +++---
> >>  1 file changed, 3 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/package/system/procd/Makefile b/package/system/procd/Makefile
> >> index 3c6bfbd..8f3d578 100644
> >> --- a/package/system/procd/Makefile
> >> +++ b/package/system/procd/Makefile
> >> @@ -8,16 +8,16 @@
> >>  include $(TOPDIR)/rules.mk 
> >>
> >>  PKG_NAME:=procd
> >> -PKG_VERSION:=2016-10-19
> >> +PKG_VERSION:=2016-12-02
> >>
> >>  PKG_RELEASE=$(PKG_SOURCE_VERSION)
> >>
> >>  PKG_SOURCE_PROTO:=git
> >>  PKG_SOURCE_URL=$(LEDE_GIT)/project/procd.git
> >>  PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION)
> >> -PKG_SOURCE_VERSION:=d80aaf4dc5ab00d65c0ae40dd7d6006155caa33b
> >> +PKG_SOURCE_VERSION:=a07669704798cb0262485f69c5547033c64ade58
> >>  PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION)-$(PKG_SOURCE_VERSION).tar.xz
> >>
> > -PKG_MIRROR_MD5SUM:=0778e6673125e4190b5c22ff7fbc8afa1978ffe218f88ad66618cc1fca1f0234
> >>
> > +PKG_MIRROR_MD5SUM:=d6a6760133a8ceb78d717a851f426266a35e3957381876d91824e9877fa8c096
> >>  CMAKE_INSTALL:=1
> >>
> >>  PKG_LICENSE:=GPL-2.0
> >>
> >> ___
> >> lede-commits mailing list
> >> lede-comm...@lists.infradead.org 
> >> http://lists.infradead.org/mailman/listinfo/lede-commits
> >
>

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH] [kernel] fix XW ethernet lockup ar71xx-ag71xx-ar803x

[Felix Fietkau]

On 2016-12-02 18:54, Joe Ayers wrote:
> Felix,
> 
> + update to NBM5/16 in table below.
> 
> I am running your staging, usually takes a ~day to see a failure.   No
> news means no failure to current time.
> 
>  testing on NS Loco M5 XW:
>  [0.00] Linux version 4.4.35 (joe@AE6XE-PE) (gcc version 5.4.0
> (LEDE GCC 5.4.0 r2415) ) #0 Thu Dec 1 15:06:55 2016
>  [1.328452] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:01
> [uid=004dd023, driver=Atheros 8032 ethernet]
> 
>  Here are the AR8032 devices to validate coverage (pulled from CC
> release images, except otherwise noted):
> 
>NBE/PBE-M2-400 XW: [from AirOS] Forced AR8032 PHY hardware reset on
> PHY setup.
>NBE/PBE-M5-300 XW:  ag71xx ag71xx.0: connected to PHY at
> ag71xx-mdio.0:01 [uid=004dd023, driver=Generic PHY]
>NBE/PBE-M5-400 XW: ag71xx ag71xx.0: connected to PHY at
> ag71xx-mdio.0:04  [uid=004dd072, driver=Atheros 8035 ethernet]
>NBE/PBE-M5-620 XW:  ag71xx ag71xx.0: connected to PHY at
> ag71xx-mdio.0:04 [uid=004dd072, driver=Atheros 8035 ethernet]
> Rocket M5 XW: ag71xx ag71xx.0: connected to PHY at
> ag71xx-mdio.0:04 [uid=004dd072, driver=Atheros 8035 ethernet]
>  Rocket M5 Titanium XW:  ???  Same as Rocket M5 XW?
> NSM5-loco-XW:  ag71xx ag71xx.0: connected to PHY at
> ag71xx-mdio.0:01 [uid=004dd023, driver=Generic PHY]
>   Airgrid M5 XW:  ag71xx ag71xx.0: connected to PHY at
> ag71xx-mdio.0:01 [uid=004dd023, driver=Generic PHY]
> NBM5/16 XW:  ag71xx ag71xx.0: connected to PHY at
> ag71xx-mdio.0:01 [uid=004dd023, driver=Generic PHY]
> NBM5/19 XW: ag71xx ag71xx.0: connected to PHY at
> ag71xx-mdio.0:01 [uid=004dd023, driver=Generic PHY]
> NS M5 XW:  ag71xx ag71xx.0: connected to PHY at
> ag71xx-mdio.0:00 [uid=004dd043, driver=Atheros AR8216/AR8236/AR8316]
>   
>  Note, where beneficial to http://www.aredn.org
>  team, we could support early testing of LEDE
> changes.  We repackage for the ham radio community with extended
> channels in our licensed frequencies on UBNT and ome TP-LINK devices.
Hi Joe,

Thanks for that. What images are you using for the other XW images with
the 004dd023 PHY? It looks like we don't have device specific ones for
those in the tree yet.

- Felix

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [source] procd: update to the latest version, fixes killing jailed processes

[Felix Fietkau]

Hi Etienne,

what value would you suggest as a default? I should probably make it
configurable on the command line as well.

- Felix

On 2016-12-02 15:25, Etienne Champetier wrote:
> Hi Felix,
> 
> Just had a look at the code and 1sec of timeout seems a bit low for me
> for an hard coded value, and might break slow but well behaving application
> 
> My 2 cents,
> Regards,
> Etienne
> 
> Le 2 déc. 2016 4:55 AM, "LEDE Commits"  > a écrit :
>>
>> nbd pushed a commit to source.git, branch master:
>> https://git.lede-project.org/1947cf36ba7556c4678beca593ad334b13b870cd
>>
>> commit 1947cf36ba7556c4678beca593ad334b13b870cd
>> Author: Felix Fietkau >
>> AuthorDate: Fri Dec 2 13:55:12 2016 +0100
>>
>> procd: update to the latest version, fixes killing jailed processes
>>
>> Signed-off-by: Felix Fietkau >
>> ---
>>  package/system/procd/Makefile | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/package/system/procd/Makefile b/package/system/procd/Makefile
>> index 3c6bfbd..8f3d578 100644
>> --- a/package/system/procd/Makefile
>> +++ b/package/system/procd/Makefile
>> @@ -8,16 +8,16 @@
>>  include $(TOPDIR)/rules.mk 
>>
>>  PKG_NAME:=procd
>> -PKG_VERSION:=2016-10-19
>> +PKG_VERSION:=2016-12-02
>>
>>  PKG_RELEASE=$(PKG_SOURCE_VERSION)
>>
>>  PKG_SOURCE_PROTO:=git
>>  PKG_SOURCE_URL=$(LEDE_GIT)/project/procd.git
>>  PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION)
>> -PKG_SOURCE_VERSION:=d80aaf4dc5ab00d65c0ae40dd7d6006155caa33b
>> +PKG_SOURCE_VERSION:=a07669704798cb0262485f69c5547033c64ade58
>>  PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION)-$(PKG_SOURCE_VERSION).tar.xz
>>
> -PKG_MIRROR_MD5SUM:=0778e6673125e4190b5c22ff7fbc8afa1978ffe218f88ad66618cc1fca1f0234
>>
> +PKG_MIRROR_MD5SUM:=d6a6760133a8ceb78d717a851f426266a35e3957381876d91824e9877fa8c096
>>  CMAKE_INSTALL:=1
>>
>>  PKG_LICENSE:=GPL-2.0
>>
>> ___
>> lede-commits mailing list
>> lede-comm...@lists.infradead.org 
>> http://lists.infradead.org/mailman/listinfo/lede-commits
> 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] replacing files in base system from a package?

[Zefir Kurtisi]

On 12/01/2016 10:29 PM, Rafał Miłecki wrote:
> On 1 December 2016 at 12:48, Zefir Kurtisi  wrote:
>> On 12/01/2016 08:28 AM, Rafał Miłecki wrote:
>>> So you still may end up with base-files installed and /etc/banner
>>> being different. If you re-install that package, e.g.
>>> opkg install base-files*.ipk
>>> you'll get banner changed to package's version.
>>>
>> From how I understand the scripts ('prepare_rootfs' is called before 
>> packages are
>> installed), a /files/etc/banner initially copied into the 
>> rootfs
>> would be overwritten with base-files/files/etc/banner when base-files*.ipk is
>> installed at the image install step. With that, > dir>/files/etc/banner
>> should never make it into a firmware image.
>>
>> (This is from looking at the include files only, did not test, could be 
>> wrong.)
> 
> I was testing it multiple times, /files/etc/banner
> overwrites one from base-files.
> 
You're right. 'prepare_rootfs' is called from image.mk/target-dir-%: _after_
packages have been installed. Which makes /etc/banner overwritten in case you
re-install base-files*.pkg on target.

Then it would be a good idea to at least warn about the potential inconsistency
during build. Or maybe remove copying of $(TOPDIR)/files completely, since the
overlay mechanism is sufficient for any use-case.


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] VGV7510KW22: Image Problem ?

[Mathias Kresin]

2016-11-24 13:05 GMT+01:00 Dennis Schneck :
> Hello,
> i try to upgrade my Image on my VGV7510KW22
>
> Running: r2244
>
> root@router:/tmp# wget 
> http://downloads.lede-project.org/snapshots/targets/lantiq/xrx200/lede-lantiq-xrx200-VGV7510KW22NOR-squashfs-sys
> upgrade.bin
> Downloading 
> 'http://downloads.lede-project.org/snapshots/targets/lantiq/xrx200/lede-lantiq-xrx200-VGV7510KW22NOR-squashfs-sysupgrade.bin'
> Connecting to 148.251.78.235:80
> Writing to 'lede-lantiq-xrx200-VGV7510KW22NOR-squashfs-sysupgrade.bin'
> lede-lantiq-xrx200-V 100% |***|  5120k  0:00:00 
> ETA
> Download completed (5243047 bytes)
> root@router:/tmp# sysupgrade -v 
> lede-lantiq-xrx200-VGV7510KW22NOR-squashfs-sysupgrade.bin
> Device VGV7510KW22 not supported by this image
> Supported devices: VGV7510KW22NOR
> Image check 'fwtool_check_image' failed.
>
>
> What did i wrong ?

You have done nothing wrong. The error is just fallout of a new
feature introduced in LEDE.

A fix for this is already in my staging tree [0] and I will push it to
the main repo during the weekend.

Mathias

[0] https://git.lede-project.org/5dd9b4b43a5990099c05139462c2811f72c92df8

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] VGV7510KW22: Image Problem ?

[Eddi De Pieri]

https://github.com/lede-project/source/commit/929641fa1fb23942581f64e6fa75ba87ba6111af

Probably you should backup your configuration and then flash using mtd

On Thu, Nov 24, 2016 at 1:21 PM, Dennis Schneck  wrote:
>
> Hello,
> i try to upgrade my Image on my VGV7510KW22
>
> Running: r2244
>
> root@router:/tmp# wget 
> http://downloads.lede-project.org/snapshots/targets/lantiq/xrx200/lede-lantiq-xrx200-VGV7510KW22NOR-squashfs-sys
> upgrade.bin
> Downloading 
> 'http://downloads.lede-project.org/snapshots/targets/lantiq/xrx200/lede-lantiq-xrx200-VGV7510KW22NOR-squashfs-sysupgrade.bin'[http://downloads.lede-project.org/snapshots/targets/lantiq/xrx200/lede-lantiq-xrx200-VGV7510KW22NOR-squashfs-sysupgrade.bin']
> Connecting to 148.251.78.235:80
> Writing to 'lede-lantiq-xrx200-VGV7510KW22NOR-squashfs-sysupgrade.bin'
> lede-lantiq-xrx200-V 100% |***| 5120k 0:00:00 ETA
> Download completed (5243047 bytes)
> root@router:/tmp# sysupgrade -v 
> lede-lantiq-xrx200-VGV7510KW22NOR-squashfs-sysupgrade.bin
> Device VGV7510KW22 not supported by this image
> Supported devices: VGV7510KW22NOR
> Image check 'fwtool_check_image' failed.
>
>
> What did i wrong ?
>
> Thanks
> Dennis
>
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] "wifi disable" will delete wifi interface like wlan0 ?

[Xue Liu]

Hello,

I have a question about wifi command in LEDE. When a route boot with a
new LEDE image, the raido is disabled and interface "wlan0" is down.
When I type "wifi disable radio0 ". It will delete the interface. Is
it possible not to delete the interface but only bring down it when i
type "wifi disable radio0" ? Thanks.

Regards,

Xue Liu

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [RFC] build: adjust version number handling

[Hannu Nyman]

Hi Jow,

I tested your patch in my build and it seemd to work ok for the current 
master branch. Also LuCI showed version info sensibly.


But you might clarify a bit the config option explanation texts. Especially 
VERSION_CODE could be hard to understand If the reader does not know the 
intended use in advance. (maybe add an example of a possible value and of the 
typical default value.) The explanation also contains references to svn and 
git-svn, which may look odd in a pure-git build environment. Could the last 
sentence be something like "it defaults to the commit count since last 
branching/tag of the build tree", or something like that. (whatever is true 
with the new logic)



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [RFC] build: adjust version number handling

[Felix Fietkau]

On 2016-12-01 18:34, Jo-Philipp Wich wrote:
> Move the revision info to the VERSION_CODE variable and default VERSION_NUMBER
> to the release branch version or to CURRENT for master branch builds.
> 
> Also introduce a new menuconfig option CONFIG_VERSION_CODE which allows users
> to override the revision value put into VERSION_CODE and adjust the template
> files used by the base-files package to accomodate for the changed semantics.
> 
> After this commit, the relevent files will look like the examples given below:
> 
> # cat /etc/openwrt_version
> r2398+1
> 
> # cat /etc/openwrt_release
> DISTRIB_ID='LEDE'
> DISTRIB_RELEASE='CURRENT'
> DISTRIB_REVISION='r2398+1'
> DISTRIB_CODENAME='reboot'
> DISTRIB_TARGET='x86/64'
> DISTRIB_DESCRIPTION='LEDE Reboot CURRENT r2398+1'
> DISTRIB_TAINTS='no-all override
> 
> # cat /usr/lib/os-release
> NAME="LEDE"
> VERSION="CURRENT, Reboot"
> ID="lede"
> ID_LIKE="lede openwrt"
> PRETTY_NAME="LEDE Reboot CURRENT"
> VERSION_ID="current"
> HOME_URL="http://www.lede-project.org/;
> BUG_URL="https://www.lede-project.org/development.html;
> SUPPORT_URL="http://lists.infradead.org/mailman/listinfo/lede-dev;
> BUILD_ID="r2398+1"
> LEDE_BOARD="x86/64"
> LEDE_TAINTS="no-all override"
> LEDE_DEVICE_MANUFACTURER="LEDE"
> LEDE_DEVICE_MANUFACTURER_URL="http://www.lede-project.org/;
> LEDE_DEVICE_PRODUCT="Generic"
> LEDE_DEVICE_REVISION="v0"
> LEDE_RELEASE="LEDE Reboot CURRENT r2398+1"
> 
> On a release branch, those files would look like:
> 
> # cat /etc/openwrt_version
> r2399
> 
> # cat /etc/openwrt_release
> DISTRIB_ID='LEDE'
> DISTRIB_RELEASE='16.12-CURRENT'
> DISTRIB_REVISION='r2399'
> DISTRIB_CODENAME='test_release'
> DISTRIB_TARGET='x86/64'
> DISTRIB_DESCRIPTION='LEDE Test Release 16.12-CURRENT r2399'
> DISTRIB_TAINTS='no-all override
> 
> # cat /usr/lib/os-release
> NAME="LEDE"
> VERSION="16.12-CURRENT, Test Release"
> ID="lede"
> ID_LIKE="lede openwrt"
> PRETTY_NAME="LEDE Test Release 16.12-CURRENT"
> VERSION_ID="16.12-current"
> HOME_URL="http://www.lede-project.org/;
> BUG_URL="https://www.lede-project.org/development.html;
> SUPPORT_URL="http://lists.infradead.org/mailman/listinfo/lede-dev;
> BUILD_ID="r2399"
> LEDE_BOARD="x86/64"
> LEDE_TAINTS="no-all override"
> LEDE_DEVICE_MANUFACTURER="LEDE"
> LEDE_DEVICE_MANUFACTURER_URL="http://www.lede-project.org/;
> LEDE_DEVICE_PRODUCT="Generic"
> LEDE_DEVICE_REVISION="v0"
> LEDE_RELEASE="LEDE Test Release 16.12-CURRENT r2399"
> 
> On a release tag, those files would look like:
> 
> # cat /etc/openwrt_version
> r2500
> 
> # cat /etc/openwrt_release
> DISTRIB_ID='LEDE'
> DISTRIB_RELEASE='17.02.1'
> DISTRIB_REVISION='r2500'
> DISTRIB_CODENAME='mighty_unicorn'
> DISTRIB_TARGET='x86/64'
> DISTRIB_DESCRIPTION='LEDE Mighty Unicorn 17.02.1 r2500'
> DISTRIB_TAINTS='no-all override
> 
> # cat /usr/lib/os-release
> NAME="LEDE"
> VERSION="17.02.1, Mighty Unicorn"
> ID="lede"
> ID_LIKE="lede openwrt"
> PRETTY_NAME="LEDE Mighty Unicorn 17.02.1"
> VERSION_ID="17.02.1"
> HOME_URL="http://www.lede-project.org/;
> BUG_URL="https://www.lede-project.org/development.html;
> SUPPORT_URL="http://lists.infradead.org/mailman/listinfo/lede-dev;
> BUILD_ID="r2500"
> LEDE_BOARD="x86/64"
> LEDE_TAINTS="no-all override"
> LEDE_DEVICE_MANUFACTURER="LEDE"
> LEDE_DEVICE_MANUFACTURER_URL="http://www.lede-project.org/;
> LEDE_DEVICE_PRODUCT="Generic"
> LEDE_DEVICE_REVISION="v0"
> LEDE_RELEASE="LEDE Mighty Unicorn 17.02.1 r2500"
> 
> Signed-off-by: Jo-Philipp Wich 
Acked-by: Felix Fietkau 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [RFC] build: adjust version number handling

[Jo-Philipp Wich]

Hi Baptiste,

good point - will do.

~ Jo



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [RFC] build: adjust version number handling

[Baptiste Jonglez]

Hi jow,

On Thu, Dec 01, 2016 at 06:34:42PM +0100, Jo-Philipp Wich wrote:
> After this commit, the relevent files will look like the examples given below:
> # cat /usr/lib/os-release
> NAME="LEDE"
> VERSION="CURRENT, Reboot"
> ID="lede"
> ID_LIKE="lede openwrt"
> PRETTY_NAME="LEDE Reboot CURRENT"
> VERSION_ID="current"
> HOME_URL="http://www.lede-project.org/;
> BUG_URL="https://www.lede-project.org/development.html;

While you're at it, maybe you can update this variable to point to the
bugtracker?

Baptiste


signature.asc
Description: PGP signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] enhanced 3G support

[Bjørn Mork]

"Giuseppe Lippolis"  writes:

> Dear Bjørn, Matti,
>
>> I don't think it is relevant for you, though.  You should continue your 
>> initial
>> idea, creating a "proto" supporting the AT managed cdc_ether based
>> modem.
>
> I add a pull request here:
>
> https://github.com/lede-project/source/pull/585
>
> Please help me to fix some issue and review it.

I'm not a user of the LEDE 3G support, so I'm unable to actually test
this.  But FWIW (if anything given the above), the overall change looks
mostly good to me.

The implementation still needs some obvious cleanups before being ready
to pull, though, I didn't like the way the "connect" block was moved.
Moving it is fine if required, but commenting out the old code and
duplicating it creates a lot of cruft which just makes the review
difficult.  I prefer a clean move showing identical deleted and added
lines.

And you appear to have lost the first character of each line in the
process (json => son, eval => val, etc)?  This doesn't make it look like
tested



Bjørn

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] openssl build issue

[Stijn Segers]

On Fri, Dec 2, 2016 at 10:48 AM, Sudeepto Roy gmail.com> wrote:

Hi,

on my setup i am having trouble building openssl and the reason is a
creation if a file whose file name is bigger then 144 char.




make[5]: Leaving directory
`/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/apps'
make[4]: Leaving directory
`/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j'
rm -f 
/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_*
touch 
/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_nnynnnynnyy_shared_no-err_no-sse2_no-ssl2_no-ssl2-method_no-heartbeats_no-engines_no-ec2m_no-ssl3_no-ssl3-method_no-hw_no-dtls_no-comp_no-sse2

touch: cannot touch
'/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_nnynnnynnyy_shared_no-err_no-sse2_no-ssl2_no-ssl2-method_no-heartbeats_no-engines_no-ec2m_no-ssl3_no-ssl3-method_no-hw_no-dtls_no-comp_no-sse2':
File name too long
make[3]: *** 
[/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_nnynnnynnyy_shared_no-err_no-sse2_no-ssl2_no-ssl2-method_no-heartbeats_no-engines_no-ec2m_no-ssl3_no-ssl3-method_no-hw_no-dtls_no-comp_no-sse2]

Error 1
make[3]: Leaving directory
`/home/sudeepto/Documents/projects/lede/source/package/libs/openssl'
make[2]: *** [package/libs/openssl/compile] Error 2

<<<

I don't see the same issue on another machine running Ubuntu 14.04 and
i had to make code changes to satisfy touch command on my working
machine. diff below

Do you know the significance of STAMP_CONFIGURED variable and will it
be ok to change this variable to have camel-case syntax. This makes
the file name sorter and we will have scope for future flags in case.

any comments if i should submit a patch for this?

Diff:

sudeepto at ubuntu:source$ git diff
diff --git a/package/libs/openssl/Makefile 
b/package/libs/openssl/Makefile

index a09c148..0a10e30 100644
--- a/package/libs/openssl/Makefile
+++ b/package/libs/openssl/Makefile
@@ -168,7 +168,10 @@ else
   endif
 endif

-STAMP_CONFIGURED := $(STAMP_CONFIGURED)_$(subst 
$(space),_,$(OPENSSL_OPTIONS))

+S_DIR := $(shell dirname $(STAMP_CONFIGURED))
+S_BASE := $(shell basename $(STAMP_CONFIGURED) | cut -d_ -f1)
+S_OPTION := $(subst $(space),_,$(OPENSSL_OPTIONS))
+STAMP_CONFIGURED := $(S_DIR)/$(S_BASE)_$(shell echo $(S_OPTION) | sed
-r 's/(^|_|-)([a-z])/\U\2/g')

 define Build/Configure
[ -f $(STAMP_CONFIGURED) ] || { \
sudeepto at ubuntu:source$


Regards,
Sudeepto Roy

___
Lede-dev mailing list
Lede-dev at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Are you using an encrypted /home by any chance? I had similar errors, I 
have my code outside /home for exactly that reason - because ecryptfs 
doesn't like the long filenames.


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] openssl build issue

[Sudeepto Roy]

Hi,

on my setup i am having trouble building openssl and the reason is a
creation if a file whose file name is bigger then 144 char.

>>>
make[5]: Leaving directory
`/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/apps'
make[4]: Leaving directory
`/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j'
rm -f 
/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_*
touch 
/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_nnynnnynnyy_shared_no-err_no-sse2_no-ssl2_no-ssl2-method_no-heartbeats_no-engines_no-ec2m_no-ssl3_no-ssl3-method_no-hw_no-dtls_no-comp_no-sse2
touch: cannot touch
'/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_nnynnnynnyy_shared_no-err_no-sse2_no-ssl2_no-ssl2-method_no-heartbeats_no-engines_no-ec2m_no-ssl3_no-ssl3-method_no-hw_no-dtls_no-comp_no-sse2':
File name too long
make[3]: *** 
[/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_nnynnnynnyy_shared_no-err_no-sse2_no-ssl2_no-ssl2-method_no-heartbeats_no-engines_no-ec2m_no-ssl3_no-ssl3-method_no-hw_no-dtls_no-comp_no-sse2]
Error 1
make[3]: Leaving directory
`/home/sudeepto/Documents/projects/lede/source/package/libs/openssl'
make[2]: *** [package/libs/openssl/compile] Error 2

<<<

I don't see the same issue on another machine running Ubuntu 14.04 and
i had to make code changes to satisfy touch command on my working
machine. diff below

Do you know the significance of STAMP_CONFIGURED variable and will it
be ok to change this variable to have camel-case syntax. This makes
the file name sorter and we will have scope for future flags in case.

any comments if i should submit a patch for this?

Diff:

sudeepto@ubuntu:source$ git diff
diff --git a/package/libs/openssl/Makefile b/package/libs/openssl/Makefile
index a09c148..0a10e30 100644
--- a/package/libs/openssl/Makefile
+++ b/package/libs/openssl/Makefile
@@ -168,7 +168,10 @@ else
   endif
 endif

-STAMP_CONFIGURED := $(STAMP_CONFIGURED)_$(subst $(space),_,$(OPENSSL_OPTIONS))
+S_DIR := $(shell dirname $(STAMP_CONFIGURED))
+S_BASE := $(shell basename $(STAMP_CONFIGURED) | cut -d_ -f1)
+S_OPTION := $(subst $(space),_,$(OPENSSL_OPTIONS))
+STAMP_CONFIGURED := $(S_DIR)/$(S_BASE)_$(shell echo $(S_OPTION) | sed
-r 's/(^|_|-)([a-z])/\U\2/g')

 define Build/Configure
[ -f $(STAMP_CONFIGURED) ] || { \
sudeepto@ubuntu:source$


Regards,
Sudeepto Roy

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev