Re: [LEDE-DEV] LEDE Wiki Teambuilding

[Raylynn Knight]

NameFunction
==
Martin Tippmann  (m...@i3o.de ),
Jan-Tarek Butt t...@ring0.de Infrastructure / 
I could take
care of nginx, caching, let's encrypt, mysql, php, memcache whatever.

Thomas Endt, wiki admin / enabler / maintenance
   ToH maintainer, Gardener, Editor

N.N.wiki admin / enabler / maintenance
   ToH maintainer

Alberto Bursi   (alberto.bu...@outlook.it ),   
Editor, Gardener

Rich Brown   (richb.hano...@gmail.com ),   
Editor, Gardener, and maybe maintenance
——
Ray Knight   (ray.knight@m e.com 
),   Editor, Gardener

N.N.,   Optimizing, pluging inplementation, organization


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Martin Blumenstingl]

On Sat, Sep 24, 2016 at 12:14 AM, Dennis Schneck  wrote:
> Hello Martin,
> sorry all is fine! Wireless works now!
> Thanks a lot!
great, have fun with your freed VGV7510KW22 :-)

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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Dennis Schneck]

 
Hello Martin,
sorry all is fine! Wireless works now!
Thanks a lot!
 
Have a nice weekend!
 
 
 
 

Gesendet: Samstag, 24. September 2016 um 00:09 Uhr
Von: "Dennis Schneck" 
An: "Martin Blumenstingl" 
Cc: lede-dev@lists.infradead.org
Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

Hi Martin,
sorry but no wifi device there
 

[   10.415927] PCI: Enabling device :00:0e.0 ( -> 0002)

[   10.420379] rt2800pci :00:0e.0: failed to load eeprom property
[   10.426368] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading 
EEPROM data from 'RT3062.eeprom'.
[   10.452504] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 
detected
[   10.458867] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0008 detected
[   10.466433] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   12.908283] random: jshn: uninitialized urandom read (4 bytes read, 53 bits 
of entropy available)
 
 
 

Gesendet: Samstag, 24. September 2016 um 00:07 Uhr
Von: "Martin Blumenstingl" 
An: "Dennis Schneck" 
Cc: lede-dev@lists.infradead.org
Betreff: Re: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work
On Sat, Sep 24, 2016 at 12:04 AM, Dennis Schneck  wrote:
> Hi Martin,
>
> i fixed the file: /etc/hotplug.d/firmware/10-rt2x00-eeprom like you told
>
> root@lede:~# FIRMWARE="RT3062.eeprom" sh 
> /etc/hotplug.d/firmware/10-rt2x00-eeprom
> 256+0 records in
> 256+0 records out
>
> whats next ?
reboot and enjoy wifi I guess :-)

___
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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Dennis Schneck]

Hi Martin,
sorry but no wifi device there
 

[   10.415927] PCI: Enabling device :00:0e.0 ( -> 0002)

[   10.420379] rt2800pci :00:0e.0: failed to load eeprom property
[   10.426368] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading 
EEPROM data from 'RT3062.eeprom'.
[   10.452504] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 
detected
[   10.458867] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0008 detected
[   10.466433] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   12.908283] random: jshn: uninitialized urandom read (4 bytes read, 53 bits 
of entropy available)
 
 
 

Gesendet: Samstag, 24. September 2016 um 00:07 Uhr
Von: "Martin Blumenstingl" 
An: "Dennis Schneck" 
Cc: lede-dev@lists.infradead.org
Betreff: Re: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work
On Sat, Sep 24, 2016 at 12:04 AM, Dennis Schneck  wrote:
> Hi Martin,
>
> i fixed the file: /etc/hotplug.d/firmware/10-rt2x00-eeprom like you told
>
> root@lede:~# FIRMWARE="RT3062.eeprom" sh 
> /etc/hotplug.d/firmware/10-rt2x00-eeprom
> 256+0 records in
> 256+0 records out
>
> whats next ?
reboot and enjoy wifi I guess :-)

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

[LEDE-DEV] [PATCH 1/2] ramips: do not "local" variables outside of a function

[Martin Blumenstingl]

Older busybox versions allowed using the local keyword outside of
functions, whereas 1.25.0 (which was introduced in 06fa1c46fc32) do not
allow this anymore (leading to the following error when executing the
script: "file: local: line nn: not in a function").

Signed-off-by: Martin Blumenstingl 
---
 target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom 
b/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
index 0e02177..4c8beac 100644
--- a/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
+++ b/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
@@ -58,7 +58,7 @@ case "$FIRMWARE" in
rt2x00_eeprom_extract "factory" 32768 512
;;
tiny-ac)
-   local wifi_mac=$(mtd_get_mac_ascii u-boot-env INIC_MAC_ADDR)
+   wifi_mac=$(mtd_get_mac_ascii u-boot-env INIC_MAC_ADDR)
rt2x00_eeprom_extract "factory" 0 512
rt2x00_eeprom_set_macaddr $wifi_mac
;;
-- 
2.10.0


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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Martin Blumenstingl]

On Sat, Sep 24, 2016 at 12:04 AM, Dennis Schneck  wrote:
> Hi Martin,
>
> i fixed the file: /etc/hotplug.d/firmware/10-rt2x00-eeprom like you told
>
> root@lede:~# FIRMWARE="RT3062.eeprom" sh 
> /etc/hotplug.d/firmware/10-rt2x00-eeprom
> 256+0 records in
> 256+0 records out
>
> whats next ?
reboot and enjoy wifi I guess :-)

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

[LEDE-DEV] [PATCH 0/2] fix "local" keywords in firmware hotplug scripts

[Martin Blumenstingl]

Currently the initialization of the RT3062F wifi chip fails on
VGV7510KW22 because the updated busybox shell does not like the usage
of the "local" keyword outside of functions.
This was reported by Dennis Schneck (see [0]):
> root@lede:~# FIRMWARE="RT3062.eeprom" sh 
> /etc/hotplug.d/firmware/10-rt2x00-eeprom
> /etc/hotplug.d/firmware/10-rt2x00-eeprom: local: line 60: not in a function

This series removes the usage of the "local" keyword outside of
functions in the firmware hotplug scripts of the ramips and lantiq
targets. Other targets don't seem to be affected.


[0] http://lists.infradead.org/pipermail/lede-dev/2016-September/002921.html

Martin Blumenstingl (2):
  ramips: do not "local" variables outside of a function
  lantiq: do not "local" variables outside of a function

 .../linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom | 4 ++--
 .../lantiq/base-files/etc/hotplug.d/firmware/11-ath10k-caldata  | 6 +++---
 .../linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom | 2 +-
 3 files changed, 6 insertions(+), 6 deletions(-)

-- 
2.10.0


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

[LEDE-DEV] [PATCH 2/2] lantiq: do not "local" variables outside of a function

[Martin Blumenstingl]

Older busybox versions allowed using the local keyword outside of
functions, whereas 1.25.0 (which was introduced in 06fa1c46fc32) do not
allow this anymore (leading to the following error when executing the
script: "file: local: line nn: not in a function").

Signed-off-by: Martin Blumenstingl 
---
 .../linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom | 4 ++--
 .../lantiq/base-files/etc/hotplug.d/firmware/11-ath10k-caldata  | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git 
a/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom 
b/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
index da10797..3aa5de4 100644
--- a/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
+++ b/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
@@ -33,7 +33,7 @@ rt2x00_eeprom_extract() {
 
 case "$FIRMWARE" in
 "RT2860.eeprom" )
-   local board=$(lantiq_board_name)
+   board=$(lantiq_board_name)
case $board in
ARV7506PW11|ARV7510PW22|ARV7519PW|ARV752DPW|ARV752DPW22|VGV7519)
rt2x00_eeprom_extract "board_config" 520 256 1
@@ -47,7 +47,7 @@ case "$FIRMWARE" in
esac
;;
 "RT3062.eeprom" )
-   local board=$(lantiq_board_name)
+   board=$(lantiq_board_name)
case $board in
VGV7510KW22)
rt2x00_eeprom_extract "board_config" 520 256 1
diff --git 
a/target/linux/lantiq/base-files/etc/hotplug.d/firmware/11-ath10k-caldata 
b/target/linux/lantiq/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 0d8084f..dc95da7 100644
--- a/target/linux/lantiq/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/lantiq/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -35,11 +35,11 @@ ath10k_caldata_set_macaddr() {
 
 case "$FIRMWARE" in
 "ath10k/cal-pci-:02:00.0.bin")
-   local board=$(lantiq_board_name)
+   board=$(lantiq_board_name)
case $board in
BTHOMEHUBV5A)
-   local lan_mac=$(mtd_get_mac_binary caldata 4364)
-   local wifi_mac=$(macaddr_add "$lan_mac" 3)
+   lan_mac=$(mtd_get_mac_binary caldata 4364)
+   wifi_mac=$(macaddr_add "$lan_mac" 3)
ath10k_caldata_extract "caldata" 20480
ath10k_caldata_set_macaddr $wifi_mac
;;
-- 
2.10.0


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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Dennis Schneck]

Hi Martin,

i fixed the file: /etc/hotplug.d/firmware/10-rt2x00-eeprom like you told

root@lede:~# FIRMWARE="RT3062.eeprom" sh 
/etc/hotplug.d/firmware/10-rt2x00-eeprom
256+0 records in
256+0 records out

whats next ?
 
Thanks


Gesendet: Freitag, 23. September 2016 um 23:33 Uhr
Von: "Martin Blumenstingl" 
An: "Dennis Schneck" 
Cc: lede-dev@lists.infradead.org
Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work
On Fri, Sep 23, 2016 at 11:28 PM, Dennis Schneck  wrote:
>> ah, could you please try that again with:
>> FIRMWARE="RT3062.eeprom" sh /etc/hotplug.d/firmware/10-rt2x00-eeprom
>
> root@lede:~# FIRMWARE="RT3062.eeprom" sh 
> /etc/hotplug.d/firmware/10-rt2x00-eeprom
> /etc/hotplug.d/firmware/10-rt2x00-eeprom: local: line 60: not in a function
> rt2x00 eeprom: board is not supported yet
Could you please try the attached patch?
I guess this is due to the busybox update (the new version seems to be
more strict regarding usage of "local" outside of functions)

if you don't know how to build an image then you could also replace
the affected lines directly in
/etc/hotplug.d/firmware/10-rt2x00-eeprom:
just replace "local board" with "board" (= remove "local").
___
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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Martin Blumenstingl]

On Fri, Sep 23, 2016 at 11:28 PM, Dennis Schneck  wrote:
>> ah, could you please try that again with:
>> FIRMWARE="RT3062.eeprom" sh /etc/hotplug.d/firmware/10-rt2x00-eeprom
>
> root@lede:~# FIRMWARE="RT3062.eeprom" sh 
> /etc/hotplug.d/firmware/10-rt2x00-eeprom
> /etc/hotplug.d/firmware/10-rt2x00-eeprom: local: line 60: not in a function
> rt2x00 eeprom:  board  is not supported yet
Could you please try the attached patch?
I guess this is due to the busybox update (the new version seems to be
more strict regarding usage of "local" outside of functions)

if you don't know how to build an image then you could also replace
the affected lines directly in
/etc/hotplug.d/firmware/10-rt2x00-eeprom:
just replace "local board" with "board" (= remove "local").
diff --git a/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom b/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
index da10797..3aa5de4 100644
--- a/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
+++ b/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
@@ -33,7 +33,7 @@ rt2x00_eeprom_extract() {
 
 case "$FIRMWARE" in
 "RT2860.eeprom" )
-	local board=$(lantiq_board_name)
+	board=$(lantiq_board_name)
 	case $board in
 	ARV7506PW11|ARV7510PW22|ARV7519PW|ARV752DPW|ARV752DPW22|VGV7519)
 		rt2x00_eeprom_extract "board_config" 520 256 1
@@ -47,7 +47,7 @@ case "$FIRMWARE" in
 	esac
 	;;
 "RT3062.eeprom" )
-	local board=$(lantiq_board_name)
+	board=$(lantiq_board_name)
 	case $board in
 	VGV7510KW22)
 		rt2x00_eeprom_extract "board_config" 520 256 1
diff --git a/target/linux/lantiq/base-files/etc/hotplug.d/firmware/11-ath10k-caldata b/target/linux/lantiq/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 0d8084f..dc95da7 100644
--- a/target/linux/lantiq/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/lantiq/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -35,11 +35,11 @@ ath10k_caldata_set_macaddr() {
 
 case "$FIRMWARE" in
 "ath10k/cal-pci-:02:00.0.bin")
-	local board=$(lantiq_board_name)
+	board=$(lantiq_board_name)
 	case $board in
 		BTHOMEHUBV5A)
-			local lan_mac=$(mtd_get_mac_binary caldata 4364)
-			local wifi_mac=$(macaddr_add "$lan_mac" 3)
+			lan_mac=$(mtd_get_mac_binary caldata 4364)
+			wifi_mac=$(macaddr_add "$lan_mac" 3)
 			ath10k_caldata_extract "caldata" 20480
 			ath10k_caldata_set_macaddr $wifi_mac
 			;;
diff --git a/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom b/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
index 0e02177..4c8beac 100644
--- a/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
+++ b/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
@@ -58,7 +58,7 @@ case "$FIRMWARE" in
 		rt2x00_eeprom_extract "factory" 32768 512
 		;;
 	tiny-ac)
-		local wifi_mac=$(mtd_get_mac_ascii u-boot-env INIC_MAC_ADDR)
+		wifi_mac=$(mtd_get_mac_ascii u-boot-env INIC_MAC_ADDR)
 		rt2x00_eeprom_extract "factory" 0 512
 		rt2x00_eeprom_set_macaddr $wifi_mac
 		;;
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Dennis Schneck]

> ah, could you please try that again with:
> FIRMWARE="RT3062.eeprom" sh /etc/hotplug.d/firmware/10-rt2x00-eeprom

root@lede:~# FIRMWARE="RT3062.eeprom" sh 
/etc/hotplug.d/firmware/10-rt2x00-eeprom
/etc/hotplug.d/firmware/10-rt2x00-eeprom: local: line 60: not in a function
rt2x00 eeprom:  board  is not supported yet

 
 
 

Gesendet: Freitag, 23. September 2016 um 23:25 Uhr
Von: "Martin Blumenstingl" 
An: "Dennis Schneck" 
Betreff: Re: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work
Hello Dennis,

On Fri, Sep 23, 2016 at 11:23 PM, Dennis Schneck  wrote:
>>what do you get when you run:
>>FIRMWARE="RT3062.eeprom" /etc/hotplug.d/firmware/10-rt2x00-eeprom
>
>
> root@lede:~# FIRMWARE="RT3062.eeprom" /etc/hotplug.d/firmware/10-rt2x00-eeprom
> -ash: /etc/hotplug.d/firmware/10-rt2x00-eeprom: Permission denied
ah, could you please try that again with:
FIRMWARE="RT3062.eeprom" sh /etc/hotplug.d/firmware/10-rt2x00-eeprom

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

Re: [LEDE-DEV] O2 Box 6431 Install LEDE without open the Device ?

[Martin Blumenstingl]

On Wed, Sep 21, 2016 at 8:26 PM, Dennis Schneck  wrote:
> Hi,
> is i right that the Image: 
> lede-lantiq-xrx200-VGV7510KW22BRN-squashfs-factory.bin
>  is the right to Flash it on a O2 6431.
>
> Is there another way to Flash the Firmware
> without open the Device an solder PINs for Serial Console ?
> ( hidden Link/URL to Flash Images ? )
you should be able to flash the mentioned image through the brnboot
recovery menu, see [0]
just follow the steps to start the recovery menu, then use the
firmware update function from there.


[0] https://wiki.openwrt.org/toh/arcadyan/vgv7510kw22#brnboot

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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

[Martin Blumenstingl]

On Fri, Sep 23, 2016 at 10:24 PM, Daniel Golle  wrote:
> Hi again,
>
> On Fri, Sep 23, 2016 at 10:06:36PM +0200, Dennis Schneck wrote:
>>
>>
>> Sorry :  mean asterisk-13.x instead of asterisk-1.8.x
>> Hi Daniel,
>> sorry about my poor english.
>>
>> Do I understand right, that it can be work with asterisk-1.8.x
>
> it can work with asterisk-1.8.x, because we got a channel driver for
> lantiq's reference TAPI stuff.
afaik we have a channel driver but unfortunately no kernel driver for
ARX100 and VRX200 (only danube is supported)
so this might not work without fixing the kernel drivers

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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Martin Blumenstingl]

On Fri, Sep 23, 2016 at 9:57 PM, Dennis Schneck  wrote:
>
> Hi Daniel,
> please see the attached files.
what do you get when you run:
FIRMWARE="RT3062.eeprom" /etc/hotplug.d/firmware/10-rt2x00-eeprom

Last time I used my VGV7510KW22 I was using brnboot (according to your
log your are using u-boot).
But this should be unrelated, since the "board_config" partition is
always at the same location (offset 0xfe).
Additionally I had it working with u-boot before.

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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

[Dennis Schneck]

 
Hi Daniel,
 
i can send you the hardware if it helps
 
 
 

Gesendet: Freitag, 23. September 2016 um 22:24 Uhr
Von: "Daniel Golle" 
An: "Dennis Schneck" 
Cc: lede-dev@lists.infradead.org
Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | 
owsip or alternative ?
Hi again,

On Fri, Sep 23, 2016 at 10:06:36PM +0200, Dennis Schneck wrote:
>
>
> Sorry :  mean asterisk-13.x instead of asterisk-1.8.x
> Hi Daniel,
> sorry about my poor english.
>  
> Do I understand right, that it can be work with asterisk-1.8.x

it can work with asterisk-1.8.x, because we got a channel driver for
lantiq's reference TAPI stuff. unfortunately it has never been adapted
to build against newer versions of asterisk, supposedly because nobody
had hardware to test or resources to put into that...

> but need a additional package that is not yet available  ?

kinda. asterisk-chan-lantiq needs to be ported to newer versions of
asterisk in order for it to work with asterisk-13.x or asterisk-11.x.
this has already been done with other 3rd-party channel drivers like
asterisk-chan-dongle or asterisk-chan-sccp-b


Cheers

Daniel

>  
> Thanks
> Dennis
>  
>
> Gesendet: Freitag, 23. September 2016 um 21:02 Uhr
> Von: "Daniel Golle" 
> An: "Dennis Schneck" 
> Cc: lede-dev@lists.infradead.org
> Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | 
> owsip or alternative ?
> On Fri, Sep 23, 2016 at 08:14:24PM +0200, Dennis Schneck wrote:
> >
> >
> >  
> > Hello,
> > i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
> > Like to use my SIP Accout with the 3x FXS Ports (Analog Phone / TAE Ports)
> >  
> > I read about owsip but can not find a package.
> > Is there a simular package for lede ?
>
> No. owsip disappeared a while ago, asterisk-chan-lantiq was dropped
> with asterisk-1.8.x being moved to packages-abandoned, but it may
> possible to still build it. If you want to give asterisk-1.8.x with
> chan-lantiq a shot, I'd be happy to assist and maybe even forward-
> port things to asterisk-13.x -- on this box having plenty of RAM
> and flash, this might actually be a quite nice option.
>
> Cheers
>
> Daniel
>
>
>
>
> > Thanks
> >  
> >  
> > 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[http://lists.infradead.org/mailman/listinfo/lede-dev][http://lists.infradead.org/mailman/listinfo/lede-dev[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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

[Daniel Golle]

Hi again,

On Fri, Sep 23, 2016 at 10:06:36PM +0200, Dennis Schneck wrote:
> 
> 
> Sorry :  mean asterisk-13.x instead of asterisk-1.8.x
> Hi Daniel,
> sorry about my poor english.
>  
> Do I understand right, that it can be work with asterisk-1.8.x

it can work with asterisk-1.8.x, because we got a channel driver for
lantiq's reference TAPI stuff. unfortunately it has never been adapted
to build against newer versions of asterisk, supposedly because nobody
had hardware to test or resources to put into that...

> but need a additional package that is not yet available  ?

kinda. asterisk-chan-lantiq needs to be ported to newer versions of
asterisk in order for it to work with asterisk-13.x or asterisk-11.x.
this has already been done with other 3rd-party channel drivers like
asterisk-chan-dongle or asterisk-chan-sccp-b


Cheers

Daniel

>  
> Thanks
> Dennis
>  
> 
> Gesendet: Freitag, 23. September 2016 um 21:02 Uhr
> Von: "Daniel Golle" 
> An: "Dennis Schneck" 
> Cc: lede-dev@lists.infradead.org
> Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | 
> owsip or alternative ?
> On Fri, Sep 23, 2016 at 08:14:24PM +0200, Dennis Schneck wrote:
> >
> >
> >  
> > Hello,
> > i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
> > Like to use my SIP Accout with the 3x FXS Ports (Analog Phone / TAE Ports)
> >  
> > I read about owsip but can not find a package.
> > Is there a simular package for lede ?
> 
> No. owsip disappeared a while ago, asterisk-chan-lantiq was dropped
> with asterisk-1.8.x being moved to packages-abandoned, but it may
> possible to still build it. If you want to give asterisk-1.8.x with
> chan-lantiq a shot, I'd be happy to assist and maybe even forward-
> port things to asterisk-13.x -- on this box having plenty of RAM
> and flash, this might actually be a quite nice option.
> 
> Cheers
> 
> Daniel
> 
> 
> 
> 
> > Thanks
> >  
> >  
> > 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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Daniel Golle]

Hi Dennis,

[   10.350649] rt2800pci :00:0e.0: Direct firmware load for RT3062.eeprom 
failed with error -2
you are lacking the EEPROM which is supposedly stored in some awkward
place (like the stock-firmware's rootfs).
it might also be an *actual* eerpom on the wifi-module, i saw that
before after hexdump-walking through the stock firmware for ages...
easiest thing you can to: try removing these line
ralink_eep {
compatible = "ralink,eeprom";
ralink,eeprom = "RT3062.eeprom";
};

from target/linux/ramips/dts/VGV7510KW22.dtsi and see what happends.
if the wifi interface comes up, probably you got a 'real' eeprom rather
than software emulation.
if that doesn't help, try extracting some other device's eeprom -- but
be warned: the callibration data stored then doesn't match the
properties of the device you got! (ie. test it briefly inside your
home's basement or something like that, do NOT use an eeprom belonging
to some other device, you may break laws and fry your brains when doing
so!)
the best would be to recovert the eeprom from the stock firmware...
(feel free to share a full flash dump, i'll try my best then)

Cheers

Daniel

PS: please do not send attachments or HTML formatted emails to the
mailing list in future! use plain text only!


On Fri, Sep 23, 2016 at 09:57:07PM +0200, Dennis Schneck wrote:
> 
> Hi Daniel,
> please see the attached files.
> 
> Thanks
> Dennis
>  
>  
> 
> Gesendet: Freitag, 23. September 2016 um 21:49 Uhr
> Von: "Daniel Golle" 
> An: "Dennis Schneck" 
> Cc: lede-dev@lists.infradead.org
> Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work
> On Fri, Sep 23, 2016 at 08:14:03PM +0200, Dennis Schneck wrote:
> >
> >
> > Hello,
> > i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
> > But the wireless did not work.
> >  
> > The Kernel Module: rt2800 is loaded
> > but there is no wlan interface.
> 
> weird. please post your kernel log and the output of
> cat /proc/bus/pci/devices
> it should actually work and i got a similar device here
> working well with rt2800pci... maybe the eeprom is missing or we
> haven't found a method to extract it from the original fw...?
> 
> >  
> > How to fix this ?
> >  
> > Thanks
> > Dennis
> >
> > ___
> > Lede-dev mailing list
> > Lede-dev@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/lede-dev

> root@lede:~# cat /proc/bus/pci/devices
> 0070  181435921e  1800   0
>0   0   0  
>  0   0   10001
>0   0   0   0  
>  0   0

> root@lede:~# dmesg 
> [0.00] Linux version 4.4.21 (buildbot@builds) (gcc version 5.4.0 
> (LEDE GCC 5.4.0 r1422) ) #0 Wed Sep 21 12:20:20 2016
> [0.00] SoC: xRX200 rev 1.2
> [0.00] bootconsole [early0] enabled
> [0.00] CPU0 revision is: 00019556 (MIPS 34Kc)
> [0.00] MIPS: machine is VGV7510KW22 - o2 Box 6431
> [0.00] Determined physical RAM map:
> [0.00]  memory: 0400 @  (usable)
> [0.00] Initrd not found or empty - disabling initrd
> [0.00] Zone ranges:
> [0.00]   Normal   [mem 0x-0x03ff]
> [0.00] Movable zone start for each node
> [0.00] Early memory node ranges
> [0.00]   node   0: [mem 0x-0x03ff]
> [0.00] Initmem setup node 0 [mem 
> 0x-0x03ff]
> [0.00] On node 0 totalpages: 16384
> [0.00] free_area_init_node: node 0, pgdat 805144b0, node_mem_map 
> 810089e0
> [0.00]   Normal zone: 128 pages used for memmap
> [0.00]   Normal zone: 0 pages reserved
> [0.00]   Normal zone: 16384 pages, LIFO batch:3
> [0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
> [0.00] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 
> 32 bytes
> [0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
> [0.00] pcpu-alloc: [0] 0 
> [0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
> pages: 16256
> [0.00] Kernel command line: console=ttyLTQ0,115200 init=/etc/preinit
> [0.00] PID hash table entries: 256 (order: -2, 1024 bytes)
> [0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
> [0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
> [0.00] Writing ErrCtl register=00075940
> [0.00] Readback ErrCtl register=00075940
> [0.00] Memory: 58136K/65536K available (3901K kernel code, 170K 
> rwdata, 1252K rodata, 1188K init, 212K bss, 7400K reserved, 0K cma-reserved)
> [0.00] SLUB: HWalign=32, Order=0-3, MinOb

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

[Dennis Schneck]

Sorry :  mean asterisk-13.x instead of asterisk-1.8.x
Hi Daniel,
sorry about my poor english.
 
Do I understand right, that it can be work with asterisk-1.8.x
but need a additional package that is not yet available  ?
 
Thanks
Dennis
 

Gesendet: Freitag, 23. September 2016 um 21:02 Uhr
Von: "Daniel Golle" 
An: "Dennis Schneck" 
Cc: lede-dev@lists.infradead.org
Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | 
owsip or alternative ?
On Fri, Sep 23, 2016 at 08:14:24PM +0200, Dennis Schneck wrote:
>
>
>  
> Hello,
> i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
> Like to use my SIP Accout with the 3x FXS Ports (Analog Phone / TAE Ports)
>  
> I read about owsip but can not find a package.
> Is there a simular package for lede ?

No. owsip disappeared a while ago, asterisk-chan-lantiq was dropped
with asterisk-1.8.x being moved to packages-abandoned, but it may
possible to still build it. If you want to give asterisk-1.8.x with
chan-lantiq a shot, I'd be happy to assist and maybe even forward-
port things to asterisk-13.x -- on this box having plenty of RAM
and flash, this might actually be a quite nice option.

Cheers

Daniel




> Thanks
>  
>  
> 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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Dennis Schneck]

Hi Daniel,
please see the attached files.

Thanks
Dennis
 
 

Gesendet: Freitag, 23. September 2016 um 21:49 Uhr
Von: "Daniel Golle" 
An: "Dennis Schneck" 
Cc: lede-dev@lists.infradead.org
Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work
On Fri, Sep 23, 2016 at 08:14:03PM +0200, Dennis Schneck wrote:
>
>
> Hello,
> i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
> But the wireless did not work.
>  
> The Kernel Module: rt2800 is loaded
> but there is no wlan interface.

weird. please post your kernel log and the output of
cat /proc/bus/pci/devices
it should actually work and i got a similar device here
working well with rt2800pci... maybe the eeprom is missing or we
haven't found a method to extract it from the original fw...?

>  
> How to fix this ?
>  
> Thanks
> Dennis
>
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-devroot@lede:~# cat /proc/bus/pci/devices
0070181435921e  1800   0
   0   0   0
   0   0   10001   
0   0   0   0   
0   0
root@lede:~# dmesg 
[0.00] Linux version 4.4.21 (buildbot@builds) (gcc version 5.4.0 (LEDE 
GCC 5.4.0 r1422) ) #0 Wed Sep 21 12:20:20 2016
[0.00] SoC: xRX200 rev 1.2
[0.00] bootconsole [early0] enabled
[0.00] CPU0 revision is: 00019556 (MIPS 34Kc)
[0.00] MIPS: machine is VGV7510KW22 - o2 Box 6431
[0.00] Determined physical RAM map:
[0.00]  memory: 0400 @  (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Zone ranges:
[0.00]   Normal   [mem 0x-0x03ff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x03ff]
[0.00] Initmem setup node 0 [mem 0x-0x03ff]
[0.00] On node 0 totalpages: 16384
[0.00] free_area_init_node: node 0, pgdat 805144b0, node_mem_map 
810089e0
[0.00]   Normal zone: 128 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 16384 pages, LIFO batch:3
[0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[0.00] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 
bytes
[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0 
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 16256
[0.00] Kernel command line: console=ttyLTQ0,115200 init=/etc/preinit
[0.00] PID hash table entries: 256 (order: -2, 1024 bytes)
[0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Writing ErrCtl register=00075940
[0.00] Readback ErrCtl register=00075940
[0.00] Memory: 58136K/65536K available (3901K kernel code, 170K rwdata, 
1252K rodata, 1188K init, 212K bss, 7400K reserved, 0K cma-reserved)
[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] NR_IRQS:256
[0.00] CPU Clock: 500MHz
[0.00] clocksource: MIPS: mask: 0x max_cycles: 0x, 
max_idle_ns: 7645041786 ns
[0.10] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps every 
8589934590ns
[0.007854] Calibrating delay loop... 332.54 BogoMIPS (lpj=665088)
[0.042317] pid_max: default: 32768 minimum: 301
[0.047155] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.053726] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.066783] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
[0.076601] pinctrl core: initialized pinctrl subsystem
[0.083088] NET: Registered protocol family 16
[0.092239] pinctrl-xway 1e100b10.pinmux: Init done
[0.097774] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, 
channels: 28
[0.207853] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[0.222964] PCI host bridge /fpi@1000/pci@E105400 ranges:
[0.228608]  MEM 0x1800..0x19ff
[0.233863]   IO 0x1ae0..0x1aff
[0.254700] usbcore: registered new interface driver usbfs
[0.260190] usbcore: registered new interface driver hub
[0.265549] usbcore: registered new device driver usb
[0.271062] PCI host bridge to bus :00
[0.275058] pci_bus :00: root bus resource [mem 0x1800-0x19ff]
[0.281966] pci_bus :00: root bus resource [io  0x1ae0-0x1aff]
[

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

[Dennis Schneck]

 
Hi Daniel,
sorry about my poor english.
 
Do I understand right, that it can be work with asterisk-1.8.x
but need a additional package that is not yet available  ?
 
Thanks
Dennis
 

Gesendet: Freitag, 23. September 2016 um 21:02 Uhr
Von: "Daniel Golle" 
An: "Dennis Schneck" 
Cc: lede-dev@lists.infradead.org
Betreff: Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | 
owsip or alternative ?
On Fri, Sep 23, 2016 at 08:14:24PM +0200, Dennis Schneck wrote:
>
>
>  
> Hello,
> i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
> Like to use my SIP Accout with the 3x FXS Ports (Analog Phone / TAE Ports)
>  
> I read about owsip but can not find a package.
> Is there a simular package for lede ?

No. owsip disappeared a while ago, asterisk-chan-lantiq was dropped
with asterisk-1.8.x being moved to packages-abandoned, but it may
possible to still build it. If you want to give asterisk-1.8.x with
chan-lantiq a shot, I'd be happy to assist and maybe even forward-
port things to asterisk-13.x -- on this box having plenty of RAM
and flash, this might actually be a quite nice option.

Cheers

Daniel




> Thanks
>  
>  
> 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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Daniel Golle]

On Fri, Sep 23, 2016 at 08:14:03PM +0200, Dennis Schneck wrote:
> 
> 
> Hello,
> i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
> But the wireless did not work.
>  
> The Kernel Module: rt2800 is loaded
> but there is no wlan interface.

weird. please post your kernel log and the output of
cat /proc/bus/pci/devices
it should actually work and i got a similar device here
working well with rt2800pci... maybe the eeprom is missing or we
haven't found a method to extract it from the original fw...?

>  
> How to fix this ?
>  
> 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

Re: [LEDE-DEV] persistent /var (or /data)?

[Alberto Bursi]

On 09/23/2016 07:52 PM, Daniel Golle wrote:
> On Fri, Sep 23, 2016 at 07:43:59PM +0200, Bastian Bittorf wrote:
>> * Daniel Golle  [23.09.2016 19:19]:
>>
>> [...]
>>
>>> On Android and other embedded systems, this whole issue is solved by
>>> having a designated volume mounted on /data, usually backed by a
>>> partition on an sdcard or the like.
>>>
>>> Similarly, on systems with block or large (SLC!) NAND storage we
>>> could introduce an additional partition/volume mounted on /data and
>>> just not have that directory on systems without any storage options.
>> [...]
>>
>> in our systems we introduced 2 new global varnames:
>>
>> $TMPDIR (like 'temp')
>> $PERMDIR (like 'permanent')
> That's kinda the idea. How do you know during runtime if $PERMDIR was
> successfully mounted, ie. if a service which requires permanent storage
> should be started?

AFAIK Only sane way is adding these options in the packaging, so you 
will know on install time what packages will have files (and what files) 
that should always stay in /tmp, what have files that can stay in /tmp 
but would be cooler to keep them on /data, or what packages MUST keep 
their files in /data.

-Alberto

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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

[Daniel Golle]

On Fri, Sep 23, 2016 at 08:14:24PM +0200, Dennis Schneck wrote:
> 
> 
>  
> Hello,
> i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
> Like to use my SIP Accout with the 3x FXS Ports (Analog Phone / TAE Ports)
>  
> I read about owsip but can not find a package.
> Is there a simular package for lede ?

No. owsip disappeared a while ago, asterisk-chan-lantiq was dropped
with asterisk-1.8.x being moved to packages-abandoned, but it may
possible to still build it. If you want to give asterisk-1.8.x with
chan-lantiq a shot, I'd be happy to assist and maybe even forward-
port things to asterisk-13.x -- on this box having plenty of RAM
and flash, this might actually be a quite nice option.

Cheers

Daniel




> Thanks
>  
>  
> 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] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

[Dennis Schneck]

 
Hello,
i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
Like to use my SIP Accout with the 3x FXS Ports (Analog Phone / TAE Ports)
 
I read about owsip but can not find a package.
Is there a simular package for lede ?
Thanks
 
 
Thanks
Dennis
 

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

[LEDE-DEV] o2 box 6431 / VGV7510KW22 - WLAN did not work

[Dennis Schneck]

Hello,
i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
But the wireless did not work.
 
The Kernel Module: rt2800 is loaded
but there is no wlan interface.
 
How to fix this ?
 
Thanks
Dennis

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

Re: [LEDE-DEV] persistent /var (or /data)?

[Daniel Golle]

On Fri, Sep 23, 2016 at 07:43:59PM +0200, Bastian Bittorf wrote:
> * Daniel Golle  [23.09.2016 19:19]:
> 
> [...]
> 
> > On Android and other embedded systems, this whole issue is solved by
> > having a designated volume mounted on /data, usually backed by a
> > partition on an sdcard or the like.
> > 
> > Similarly, on systems with block or large (SLC!) NAND storage we
> > could introduce an additional partition/volume mounted on /data and
> > just not have that directory on systems without any storage options.
> 
> [...]
> 
> in our systems we introduced 2 new global varnames:
> 
> $TMPDIR (like 'temp')
> $PERMDIR (like 'permanent')

That's kinda the idea. How do you know during runtime if $PERMDIR was
successfully mounted, ie. if a service which requires permanent storage
should be started?

> 
> this makes it clearer in the code and we are "future-safe".
> 
> bye, bastian

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

Re: [LEDE-DEV] persistent /var (or /data)?

[Bastian Bittorf]

* Daniel Golle  [23.09.2016 19:19]:

[...]

> On Android and other embedded systems, this whole issue is solved by
> having a designated volume mounted on /data, usually backed by a
> partition on an sdcard or the like.
> 
> Similarly, on systems with block or large (SLC!) NAND storage we
> could introduce an additional partition/volume mounted on /data and
> just not have that directory on systems without any storage options.

[...]

in our systems we introduced 2 new global varnames:

$TMPDIR (like 'temp')
$PERMDIR (like 'permanent')

this makes it clearer in the code and we are "future-safe".

bye, bastian

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

[LEDE-DEV] persistent /var (or /data)?

[Daniel Golle]

Hi!

Please share your thoughts on a rather trivial but yet important
issue I'm currently facing:
/var happends to be a symlink to /tmp which makes sense on small
flash-based systems. For some applications it may be feasible to also
offer some convention on where to mount a persistent storage volume.
Think of collectd, postgresql or even syslog data surviving reboot if
a suitable storage option exists.
At first I thought it could be as easy as removing the /var symlink
and mounting something else where instead -- however, it seems that
the assumption that /var == /tmp held true for too long to allow that
kind of change to be trouble-free.

On Android and other embedded systems, this whole issue is solved by
having a designated volume mounted on /data, usually backed by a
partition on an sdcard or the like.

Similarly, on systems with block or large (SLC!) NAND storage we
could introduce an additional partition/volume mounted on /data and
just not have that directory on systems without any storage options.

Any ideas? Objections?


Cheers


Daniel

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

[LEDE-DEV] [PATCH netifd 6/7] vlandev: Rework 8021ad/8021q detection based on vlandevice type

[Hans Dedecker]

Signed-off-by: Hans Dedecker 
---
 vlandev.c | 13 -
 1 file changed, 4 insertions(+), 9 deletions(-)

diff --git a/vlandev.c b/vlandev.c
index b065c27..7e46251 100644
--- a/vlandev.c
+++ b/vlandev.c
@@ -20,14 +20,12 @@
 #include "system.h"
 
 enum {
-   VLANDEV_ATTR_TYPE,
VLANDEV_ATTR_IFNAME,
VLANDEV_ATTR_VID,
__VLANDEV_ATTR_MAX
 };
 
 static const struct blobmsg_policy vlandev_attrs[__VLANDEV_ATTR_MAX] = {
-   [VLANDEV_ATTR_TYPE] = { "type", BLOBMSG_TYPE_STRING },
[VLANDEV_ATTR_IFNAME] = { "ifname", BLOBMSG_TYPE_STRING },
[VLANDEV_ATTR_VID] = { "vid", BLOBMSG_TYPE_INT32 },
 };
@@ -40,6 +38,8 @@ static const struct uci_blob_param_list vlandev_attr_list = {
.next = { &device_attr_list },
 };
 
+static struct device_type vlan8021q_device_type;
+
 struct vlandev_device {
struct device dev;
struct device_user parent;
@@ -158,15 +158,10 @@ vlandev_apply_settings(struct vlandev_device *mvdev, 
struct blob_attr **tb)
struct vlandev_config *cfg = &mvdev->config;
struct blob_attr *cur;
 
-   cfg->proto = VLAN_PROTO_8021Q;
+   cfg->proto = (mvdev->dev.type == &vlan8021q_device_type) ?
+   VLAN_PROTO_8021Q : VLAN_PROTO_8021AD;
cfg->vid = 1;
 
-   if ((cur = tb[VLANDEV_ATTR_TYPE]))
-   {
-   if(!strcmp(blobmsg_data(cur), "8021ad"))
-   cfg->proto = VLAN_PROTO_8021AD;
-   }
-
if ((cur = tb[VLANDEV_ATTR_VID]))
cfg->vid = (uint16_t) blobmsg_get_u32(cur);
 }
-- 
1.9.1


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

[LEDE-DEV] [PATCH netifd 1/7] device: Move the different device type registrations to the device type file

[Hans Dedecker]

While at it; make device_types static if only used in the device type file

Signed-off-by: Hans Dedecker 
---
 alias.c   |  2 --
 bridge.c  |  5 +
 device.c  | 15 +--
 device.h  |  2 --
 macvlan.c |  7 ++-
 tunnel.c  |  5 -
 vlandev.c |  7 ++-
 7 files changed, 26 insertions(+), 17 deletions(-)

diff --git a/alias.c b/alias.c
index f95c9f5..649f2d1 100644
--- a/alias.c
+++ b/alias.c
@@ -30,8 +30,6 @@ struct alias_device {
char name[];
 };
 
-static struct device_type alias_device_type;
-
 static void alias_set_device(struct alias_device *alias, struct device *dev)
 {
if (dev == alias->dep.dev) {
diff --git a/bridge.c b/bridge.c
index bcece52..98e237b 100644
--- a/bridge.c
+++ b/bridge.c
@@ -729,3 +729,8 @@ bridge_create(const char *name, struct device_type *devtype,
 
return dev;
 }
+
+static void __init bridge_device_type_init(void)
+{
+   device_type_add(&bridge_device_type);
+}
diff --git a/device.c b/device.c
index a7d18af..e17df13 100644
--- a/device.c
+++ b/device.c
@@ -82,16 +82,6 @@ int device_type_add(struct device_type *devtype)
return 0;
 }
 
-/* initialize device type list and add known types */
-static void __init devtypes_init(void)
-{
-   device_type_add(&simple_device_type);
-   device_type_add(&bridge_device_type);
-   device_type_add(&tunnel_device_type);
-   device_type_add(&macvlan_device_type);
-   device_type_add(&vlandev_device_type);
-}
-
 /* Retrieve the device type for the given name. If 'bridge' is true, the type
  * must have bridge capabilities
  */
@@ -1065,3 +1055,8 @@ device_dump_status(struct blob_buf *b, struct device *dev)
system_if_dump_stats(dev, b);
blobmsg_close_table(b, s);
 }
+
+static void __init simple_device_type_init(void)
+{
+   device_type_add(&simple_device_type);
+}
diff --git a/device.h b/device.h
index c669beb..f3ca957 100644
--- a/device.h
+++ b/device.h
@@ -228,8 +228,6 @@ extern const struct uci_blob_param_list device_attr_list;
 extern struct device_type simple_device_type;
 extern struct device_type bridge_device_type;
 extern struct device_type tunnel_device_type;
-extern struct device_type macvlan_device_type;
-extern struct device_type vlandev_device_type;
 
 void device_lock(void);
 void device_unlock(void);
diff --git a/macvlan.c b/macvlan.c
index ffadfd4..01a48cd 100644
--- a/macvlan.c
+++ b/macvlan.c
@@ -253,7 +253,7 @@ macvlan_create(const char *name, struct device_type 
*devtype,
return dev;
 }
 
-struct device_type macvlan_device_type = {
+static struct device_type macvlan_device_type = {
.name = "MAC VLAN",
.config_params = &macvlan_attr_list,
.create = macvlan_create,
@@ -262,3 +262,8 @@ struct device_type macvlan_device_type = {
.free = macvlan_free,
.dump_info = macvlan_dump_info,
 };
+
+static void __init macvlan_device_type_init(void)
+{
+   device_type_add(&macvlan_device_type);
+}
diff --git a/tunnel.c b/tunnel.c
index ec622d8..32f3613 100644
--- a/tunnel.c
+++ b/tunnel.c
@@ -97,4 +97,7 @@ struct device_type tunnel_device_type = {
.free = tunnel_free,
 };
 
-
+static void __init tunnel_device_type_init(void)
+{
+   device_type_add(&tunnel_device_type);
+}
diff --git a/vlandev.c b/vlandev.c
index b8f7a25..becaed8 100644
--- a/vlandev.c
+++ b/vlandev.c
@@ -241,7 +241,7 @@ vlandev_create(const char *name, struct device_type 
*devtype,
return dev;
 }
 
-struct device_type vlandev_device_type = {
+static struct device_type vlandev_device_type = {
.name = "VLANDEV",
.config_params = &vlandev_attr_list,
.create = vlandev_create,
@@ -250,3 +250,8 @@ struct device_type vlandev_device_type = {
.free = vlandev_free,
.dump_info = vlandev_dump_info,
 };
+
+static void __init vlandev_device_type_init(void)
+{
+   device_type_add(&vlandev_device_type);
+}
-- 
1.9.1


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

[LEDE-DEV] [PATCH netifd 5/7] vlandev: Register 8021ad and 8021q s device types

[Hans Dedecker]

Fixes creation of vlan 8021ad/8021q devices by UCI due to device handlers rework

Signed-off-by: Hans Dedecker 
---
 vlandev.c | 17 ++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/vlandev.c b/vlandev.c
index becaed8..b065c27 100644
--- a/vlandev.c
+++ b/vlandev.c
@@ -241,8 +241,18 @@ vlandev_create(const char *name, struct device_type 
*devtype,
return dev;
 }
 
-static struct device_type vlandev_device_type = {
-   .name = "VLANDEV",
+static struct device_type vlan8021ad_device_type = {
+   .name = "8021ad",
+   .config_params = &vlandev_attr_list,
+   .create = vlandev_create,
+   .config_init = vlandev_config_init,
+   .reload = vlandev_reload,
+   .free = vlandev_free,
+   .dump_info = vlandev_dump_info,
+};
+
+static struct device_type vlan8021q_device_type = {
+   .name = "8021q",
.config_params = &vlandev_attr_list,
.create = vlandev_create,
.config_init = vlandev_config_init,
@@ -253,5 +263,6 @@ static struct device_type vlandev_device_type = {
 
 static void __init vlandev_device_type_init(void)
 {
-   device_type_add(&vlandev_device_type);
+   device_type_add(&vlan8021ad_device_type);
+   device_type_add(&vlan8021q_device_type);
 }
-- 
1.9.1


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

[LEDE-DEV] [PATCH netifd 7/7] device: Drop device down event during device release if device gets active again

[Hans Dedecker]

Fixes a race condition as the device can be active again; due to a 
device_claim; by the logic
behind the set_state device type function. In this case the down event cannot 
be sent anymore
as it would bring down the interface(s) referencing the device.
This can be the case for an aliased device when the underlying device is 
switched during a reload;
the alias_set_device function can add a new dependency on the new active device 
which will put the
aliased device in active mode again as the aliased device is already claimed by 
the interface
using it.

Signed-off-by: Hans Dedecker 
---
 device.c | 4 
 1 file changed, 4 insertions(+)

diff --git a/device.c b/device.c
index e17df13..996ffab 100644
--- a/device.c
+++ b/device.c
@@ -450,6 +450,10 @@ void device_release(struct device_user *dep)
device_broadcast_event(dev, DEV_EVENT_TEARDOWN);
if (!dev->external)
dev->set_state(dev, false);
+
+   if (dev->active)
+   return;
+
device_broadcast_event(dev, DEV_EVENT_DOWN);
 }
 
-- 
1.9.1


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

[LEDE-DEV] [PATCH netifd 4/7] tunnel: Use tunnel as device type name

[Hans Dedecker]

Fixes creation of tunnel devices by UCI due to device handlers rework

Signed-off-by: Hans Dedecker 
---
 tunnel.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tunnel.c b/tunnel.c
index 32f3613..3fa3e21 100644
--- a/tunnel.c
+++ b/tunnel.c
@@ -90,7 +90,7 @@ tunnel_free(struct device *dev)
 }
 
 struct device_type tunnel_device_type = {
-   .name = "IP tunnel",
+   .name = "tunnel",
.config_params = &tunnel_attr_list,
.reload = tunnel_reload,
.create = tunnel_create,
-- 
1.9.1


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

[LEDE-DEV] [PATCH netifd 3/7] macvlan: Use macvlan as device type name

[Hans Dedecker]

Fixes creation of macvlan devices by UCI due to device handlers rework

Signed-off-by: Hans Dedecker 
---
 macvlan.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/macvlan.c b/macvlan.c
index 01a48cd..021d394 100644
--- a/macvlan.c
+++ b/macvlan.c
@@ -254,7 +254,7 @@ macvlan_create(const char *name, struct device_type 
*devtype,
 }
 
 static struct device_type macvlan_device_type = {
-   .name = "MAC VLAN",
+   .name = "macvlan",
.config_params = &macvlan_attr_list,
.create = macvlan_create,
.config_init = macvlan_config_init,
-- 
1.9.1


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

[LEDE-DEV] [PATCH netifd 2/7] bridge: Make bridge_device_type static

[Hans Dedecker]

Signed-off-by: Hans Dedecker 
---
 bridge.c   | 2 +-
 device.h   | 1 -
 wireless.c | 2 +-
 3 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/bridge.c b/bridge.c
index 98e237b..8e6c9a6 100644
--- a/bridge.c
+++ b/bridge.c
@@ -80,7 +80,7 @@ static void bridge_dump_info(struct device *dev, struct 
blob_buf *b);
 enum dev_change_type
 bridge_reload(struct device *dev, struct blob_attr *attr);
 
-struct device_type bridge_device_type = {
+static struct device_type bridge_device_type = {
.name = "bridge",
.config_params = &bridge_attr_list,
 
diff --git a/device.h b/device.h
index f3ca957..2af93bb 100644
--- a/device.h
+++ b/device.h
@@ -226,7 +226,6 @@ struct device_hotplug_ops {
 
 extern const struct uci_blob_param_list device_attr_list;
 extern struct device_type simple_device_type;
-extern struct device_type bridge_device_type;
 extern struct device_type tunnel_device_type;
 
 void device_lock(void);
diff --git a/wireless.c b/wireless.c
index be94c34..9109ce1 100644
--- a/wireless.c
+++ b/wireless.c
@@ -83,7 +83,7 @@ vif_config_add_bridge(struct blob_buf *buf, struct blob_attr 
*networks, bool pre
if (!dev)
return;
 
-   if (dev->type != &bridge_device_type)
+   if (!dev->type->bridge_capability)
return;
}
 
-- 
1.9.1


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

[LEDE-DEV] [PATCH] initramfs: Escape colons in depfile

[Michal Marek]

Special characters are problematic in depfiles, but we can fix colons
easily.

Reported-by: Florian Fainelli 
Signed-off-by: Michal Marek 
---
 scripts/gen_initramfs_list.sh | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/scripts/gen_initramfs_list.sh b/scripts/gen_initramfs_list.sh
index 17fa901418ae..0055b07b03b6 100755
--- a/scripts/gen_initramfs_list.sh
+++ b/scripts/gen_initramfs_list.sh
@@ -97,7 +97,10 @@ print_mtime() {
 }
 
 list_parse() {
-   [ ! -L "$1" ] && echo "$1 \\" || :
+   if [ -L "$1" ]; then
+   return
+   fi
+   echo "$1" | sed 's/:/\\:/g; s/$/ \\/'
 }
 
 # for each file print a line in following format
-- 
2.6.6


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

Re: [LEDE-DEV] gen_initramfs_list.sh escaping problem or stale dependency file?

[Michal Marek]

On 2016-09-19 22:00, Florian Fainelli wrote:
> On 09/13/2016 12:24 AM, Michal Marek wrote:
>> On Mon, Sep 12, 2016 at 05:12:15PM -0700, Florian Fainelli wrote:
>>> Hi,
>>>
>>> I have a root filesystem embedding filenames that look like these:
>>>
>>> /lib/data/:
>>>
>>> these are essentially files that can be matched against an USB
>>> vendor/product id in an easy way.
>>>
>>> Now, the fun part is that this is only a problem when doing the
>>> following (using OpenWrt/LEDE as a build system):
>>>
>>> 1:
>>> - set CONFIG_INITRAMFS_SOURCE=""
>>> - build kernel modules
>>> - build my user-space tools
>>> - build the kernel image
>>> - reconfigure the kernel to now use an initramfs
>>> - build the kernel w/ initramfs
>>>
>>> and then back to step 1 with the kernel build, would I hit this error:
>>>
>>> usr/Makefile:64: *** multiple target patterns.  Stop.
>> [...]
>>> Which sorts of make sense here because the file name contains a ":"
>>> which is not escaped, so GNU Make tries to interpret it.
>>>
>>> Now the part that does not quite make sense to me is why this file is
>>> even relevant here considering that the first thing we do is set
>>> CONFIG_INITRAMFS_SOURCE="" to disable the initramfs basically.
>>
>> It is possible that we read usr/Makefile twice for some reason. But the
>> real problem is the lack of escaping. Can you try the following
>> (untested) patch?
> 
> Can you submit an official patch for this? Thanks a lot!

The % escape is wrong. I'm trying to fix it or drop this escape.

Michal


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