[LEDE-DEV] [PATCH RESEND] mvebu: configure switch on WRT1200AC and WRT1900ACv2/S

2016-05-21 Thread Claudio Leite 
Also collapses the three identical configurations into one block.

Signed-off-by: Claudio Leite 
---
 target/linux/mvebu/base-files/etc/board.d/02_network | 10 --
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/target/linux/mvebu/base-files/etc/board.d/02_network 
b/target/linux/mvebu/base-files/etc/board.d/02_network
index f81d0ac..8f633c9 100755
--- a/target/linux/mvebu/base-files/etc/board.d/02_network
+++ b/target/linux/mvebu/base-files/etc/board.d/02_network
@@ -11,14 +11,12 @@ board_config_update
 board=$(mvebu_board_name)
 
 case "$board" in
-armada-385-linksys-caiman)
-   ucidef_set_interfaces_lan_wan "eth1" "eth0"
-   ;;
-armada-385-linksys-cobra)
-   ucidef_set_interfaces_lan_wan "eth1" "eth0"
-   ;;
+armada-385-linksys-caiman|\
+armada-385-linksys-cobra|\
 armada-385-linksys-shelby)
ucidef_set_interfaces_lan_wan "eth1" "eth0"
+   ucidef_add_switch "switch0" \
+   "0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "6@eth1" "4:wan" 
"5@eth0"
;;
 armada-xp-linksys-mamba)
ucidef_set_interfaces_lan_wan "eth0" "eth1"
-- 
2.1.4


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

[LEDE-DEV] Need help with apu2 system

2016-05-21 Thread Ben Greear 

I'm trying to install LEDE on an apu2 system.

My first attempt is not working:  I see grub menu, then it hangs as soon as
it tries to boot.  If someone has a working .config
and/or other hints on how to go about this, I'd appreciate some pointers.

Thanks,
Ben

--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com


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

Re: [LEDE-DEV] OpenWRT tree vs LEDE tree

2016-05-21 Thread Daniel Curran-Dickinson 
Must...remember...don't feed the trolls (or their close cousins the
vocal unrealistic idealogues).


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

Re: [LEDE-DEV] [PATCH v2] cyassl/wolfssl: update to 3.9.0

2016-05-21 Thread Dirk Neukirchen 
On 21.05.2016 14:39, Hauke Mehrtens wrote:
> Hi,
> 
> 
> On 05/21/2016 07:35 AM, Dirk Neukirchen wrote:
>> @@ -38,12 +38,10 @@ endef
>>  TARGET_CFLAGS += $(FPIC)
>>  
>>  CONFIGURE_ARGS += \
>> ---without-zlib \
> 
> Was the zlib dependency completely removed from wolfssl? Have you tried
> to compile zlib in LEDE so that configure on wolfssl would find it and
> made sure that wolfssl does not depend on it.
> 

The zlib switch is not working, the configure.ac is "wrong" and I think its
deactivated by default anyway:

configure.ac has AC_ARG_WITH _libz_ 
so the zlib switch gets a warning that this config option is unknown in log.

Then "--without" does not work if its stated - but leaving out that argument 
does
I think its an issue like: 
http://www.yassl.com/forums/topic80-wolfssl-configure-zlib-check.html
and the configure.ac that is "wrong" - if you try to set "--without-libz" then
zlib gets enabled anyway


>>  --enable-singlethreaded \
>>  --enable-opensslextra \
>>  --enable-sni \
>>  --enable-ecc \
>> ---enable-sslv3 \
>>  --disable-examples
>>  



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

Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure

2016-05-21 Thread Felix Fietkau 
On 2016-05-21 14:05, Dheeran Senthilvel wrote:
> Hi Guys,
>   
> Nice work there getting everything to Linux 4.4.11. Tested the new
> build (r321 dated 20/05/2016) Everything is seems to work pretty
> decently, except that upon reboot (both manually or through command
> line) the device is struck. When serially accessed an error is seen
Please make a clean build from the latest version and reflash the image
from the boot loader. I just pushed some flash driver fixes...

- Felix

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

Re: [LEDE-DEV] b53 cpu_port patch for cavium boards

2016-05-21 Thread Hauke Mehrtens 
Hi,

On 05/21/2016 10:07 AM, Michał Osowiecki wrote:
> Cisco RV042G is Cavium based router with BCM53125 switch and BCM54612E
> connected to port 8, and port 5 acts as cpu port. Probably Linksys
> LRT214 and LRT224 will be affected by this patch too (boards are
> identical).
> I don't know if there are other Cavium boards with BCM53125. If so, this
> patch will need more work to detect them.
> 
> Signed-off-by: Michał Osowiecki 
> 

Could you send the patch inside the text of the mail please that makes
review easier.

How is the switch connected to the main SoC? I do not like the #ifdef in
there, if it is not absolutely needed, would it be possible to extend
some platform_data structure or similar to add this?

Hauke

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

[LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure

2016-05-21 Thread Dheeran Senthilvel 
Hi Guys,

Nice work there getting everything to Linux 4.4.11. Tested the new build (r321 
dated 20/05/2016) Everything is seems to work pretty decently, except that upon 
reboot (both manually or through command line) the device is struck. When 
serially accessed an error is seen 


 __   __  _ _
|  \/  | __ _ _    _| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|\_/ \___|_|_|
 _   _   _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/|/ \___/ \___/ \__|
 ** LOADER **


U-Boot 2013.01 (Mar 27 2015 - 16:50:46) Marvell version: 2014_T3.0p6

Boot version : v1.0.13

Board: RD-NAS-88F6820-DDR3
SoC:   MV88F6820 Rev A0
   running 2 CPUs
CPU:   ARM Cortex A9 MPCore (Rev 1) LE
   CPU 0
   CPU@ 1600 [MHz]
   L2 @ 800 [MHz]
   TClock @ 200 [MHz]
   DDR@ 800 [MHz]
   DDR 32 Bit Width, FastPath Memory Access, DLB Enabled, ECC Disabled
DRAM:  512 MiB

Map:   Code:0x1fea9000:0x1ff7632c
   BSS: 0x1ffef6b4
   Stack:   0x1f9a8f20
   Heap:0x1f9a9000:0x1fea9000
raise: Signal # 8 caught
U-ENV offset == 0x20
raise: Signal # 8 caught
U-ENV offset == 0x20
   U-Boot Environment:  0x0020:0x0022 (NAND)

NAND:  128 MiB
MMC:   mv_sdh: 0
DEVINFO offset == 0x90
U-ENV offset == 0x20
U-ENV offset == 0x20
S-ENV offset == 0x24


 auto_recovery 
[u_env] get auto_recovery == yes
[u_env] get auto_recovery == yes
[u_env] get boot_part == 
set boot_part=1 as default value at u_env
[u_env] get boot_part_ready == 
set boot_part_ready=3 as default value at u_env
auto_recovery enabled:1, boot_part:1, boot_part_ready:3

S-ENV offset == 0x24
[boot_count_read] block:0x24, size:128KB, records:64
[boot_count_read_record] boot_count:0, next_record:51

[boot_count_write] erase:0, auto_recovery->block_offset:0x24 offset=0x259800

Updating boot_count ...
[boot_count_write] offset:0x259800 , length:2048
done

PCI-e 0 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 2.0
PCI-e 1 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1
USB2.0 0: Host Mode
USB3.0 1: Host Mode
USB3.0 0: Host Mode
Board configuration detected:
mvEthE6171SwitchBasicInit init
Net:
|  port  | Interface | PHY address  |
||---|--|
| egiga0 |   RGMII   | 0x01 |
| egiga1 |   SGMII   | 0x00 |
egiga0 [PRIME], egiga1
auto_recovery_check changes bootcmd: run nandboot
Hit any key to stop autoboot:  0
## Error: "nandboot" not defined
Marvell>>


## The env variables during error boot is as follows 
##

Marvell>> printenv
CASset=max
MALLOC_len=5
MPmode=SMP
auto_recovery=yes
autoload=no
baudrate=115200
boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr
boot_part=1
boot_part_ready=3
bootargs_dflt=$console $nandEcc $mtdparts $bootargs_root 
nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig 
video=dovefb:lcd0:$lcd0_para
ms clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:10.4.50.254:255.255.255.0:Armada38x:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} 
ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootcmd_auto=stage_boot $boot_order
bootcmd_fdt=tftpboot 0x200 $image_name;tftpboot $fdtaddr $fdtfile;setenv 
bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath 
ip=
$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params 
clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x200 - 
$fdtaddr;
bootcmd_fdt_boot=tftpboot 0x200 $image_name; setenv bootargs $console 
$nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath 
ip=$ipaddr:$serverip$boo
targs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params 
clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x200 - 
$fdtaddr;
bootcmd_fdt_edit=tftpboot $fdtaddr $fdtfile; fdt addr $fdtaddr; setenv bootcmd 
$bootcmd_fdt_boot
bootcmd_lgcy=tftpboot 0x200 $image_name; setenv bootargs $bootargs_dflt; 
bootm 0x200;
bootdelay=5
cacheShare=no
console=console=ttyS0,115200
device_partition=0:1
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1addr=00:50:43:87:dd:02
eth1mtu=1500
eth2addr=00:50:43:87:9c:02
eth2mtu=1500
eth3addr=00:50:43:dd:9c:87
eth3mtu=1500
ethact=egiga0
ethaddr=00:50:43:9c:dd:02
ethmtu=1500
ethprime=egiga0
fdt_addr=204
fdt_skip_update=no
fdtaddr=0x100
fdtfile=armada-38x-modular.dtb
ide_path=/
image_name=uImage
initrd_name=uInitrd
kernel_addr_r=208
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
loadaddr=0x0200
mtdids=nand0=armada-nand

Re: [LEDE-DEV] [PATCH 03/13] ar71xx: enable sysupgrade for the OpenMesh OM2P-HSv3

2016-05-21 Thread John Crispin 
Hi Sven,

this patch fails to apply.

mind re-spinning the series on top of latest source.git ?

John

On 20/05/2016 17:53, Sven Eckelmann wrote:
> Signed-off-by: Sven Eckelmann 
> ---
>  target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh | 1 +
>  target/linux/ar71xx/base-files/lib/upgrade/platform.sh | 2 ++
>  2 files changed, 3 insertions(+)
> 
> diff --git a/target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh 
> b/target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh
> index bc362a7..270ef40 100644
> --- a/target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh
> +++ b/target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh
> @@ -47,6 +47,7 @@ platform_check_image_target_openmesh()
>   [ "$board" = "om2p-lc" ] && return 0
>   [ "$board" = "om2p-hs" ] && return 0
>   [ "$board" = "om2p-hsv2" ] && return 0
> + [ "$board" = "om2p-hsv3" ] && return 0
>   echo "Invalid image board target ($img_board_target) 
> for this platform: $board. Use the correct image for this platform"
>   return 1
>   ;;
> diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh 
> b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
> index 0d6aa6b..ec1cdbd 100755
> --- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
> +++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
> @@ -322,6 +322,7 @@ platform_check_image() {
>   om2pv2 | \
>   om2p-hs | \
>   om2p-hsv2 | \
> + om2p-hsv3 | \
>   om2p-lc | \
>   om5p | \
>   om5p-an | \
> @@ -581,6 +582,7 @@ platform_do_upgrade() {
>   om2pv2 | \
>   om2p-hs | \
>   om2p-hsv2 | \
> + om2p-hsv3 | \
>   om2p-lc | \
>   om5p | \
>   om5p-an | \
> 

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