Re: [OpenWrt-Devel] [PATCH] [RFC] add unison-2.48.3

[Stefan Hellermann]

two comments to my own patch:

2015-09-18 7:13 GMT+02:00 Stefan Hellermann :

> should probably be sent to the packages repo on github.
>
> Signed-of-by: Stefan Hellermann 
> ---
>  package/network/utils/unison/Makefile  |  36 
>  .../utils/unison/patches/100-ocamlopt.patch| 225
> +
>  2 files changed, 261 insertions(+)
>  create mode 100644 package/network/utils/unison/Makefile
>  create mode 100644 package/network/utils/unison/patches/100-ocamlopt.patch
>
> diff --git a/package/network/utils/unison/Makefile
> b/package/network/utils/unison/Makefile
> new file mode 100644
> index 000..91d9516
> --- /dev/null
> +++ b/package/network/utils/unison/Makefile
> @@ -0,0 +1,36 @@
> +#
> +# Copyright (C) 2009-2011 OpenWrt.org
> +#
> +# This is free software, licensed under the GNU General Public License v2.
> +# See /LICENSE for more information.
> +#
> +
> +include $(TOPDIR)/rules.mk
> +
> +PKG_NAME:=unison
> +PKG_VERSION:=2.48.3
> +PKG_RELEASE:=1
> +
> +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
> +PKG_SOURCE_URL:=
> http://www.seas.upenn.edu/~bcpierce/unison//download/releases/$(PKG_NAME)-$(PKG_VERSION)/
> +
> +include $(INCLUDE_DIR)/package.mk
> +
> +define Package/unison
> +  SECTION:=utilities
> +  CATEGORY:=Utilities
> +  TITLE:=Unison file synchronizer
> +  URL:=http://www.cis.upenn.edu/~bcpierce/unison/
> +  DEPENDS:= libncurses
> +endef
> +
>

There is a # missing in front of next line


> +Stripping OCaml binaries is not possible
> +RSTRIP:=:
> +STRIP:=:
> +
> +define Package/unison/install
> +   $(INSTALL_DIR) $(1)/usr/bin
> +   $(INSTALL_BIN) $(PKG_BUILD_DIR)/unison $(1)/usr/bin
> +endef
> +
> +$(eval $(call BuildPackage,unison))
> diff --git a/package/network/utils/unison/patches/100-ocamlopt.patch
> b/package/network/utils/unison/patches/100-ocamlopt.patch
> new file mode 100644
> index 000..a8132e2
>

inotify_compat.h is missing in unison, this is known upstream.
https://www.marc.info/?l=unison-hackers=138390422022273=2
Another option is to remove fsmonitor from unison, as the binary
"unison-fsmonitor" is not currently installed onto the target.

--- /dev/null
> +++ b/package/network/utils/unison/patches/100-ocamlopt.patch
> @@ -0,0 +1,225 @@
> +--- /dev/null  2015-08-24 10:52:13.18000 +0200
>  unison-2.48.3/fsmonitor/linux/inotify_compat.h 2015-09-11
> 22:59:01.05600 +0200
> +@@ -0,0 +1,167 @@
> ++/*
> ++ * This header is used if  cannot be found.
> ++ *
> ++ * Inode based directory notification for Linux
> ++ *
> ++ * Copyright (C) 2005 John McCutchan
> ++ */
> ++
> ++#ifndef _LINUX_INOTIFY_H
> ++#define _LINUX_INOTIFY_H
> ++
> ++#include 
> ++#include 
> ++#include 
> ++
> ++/*
> ++ * struct inotify_event - structure read from the inotify device for
> each event
> ++ *
> ++ * When you are watching a directory, you will receive the filename for
> events
> ++ * such as IN_CREATE, IN_DELETE, IN_OPEN, IN_CLOSE, ..., relative to the
> wd.
> ++ */
> ++struct inotify_event {
> ++  int wd; /* watch descriptor */
> ++  uint32_tmask;   /* watch mask */
> ++  uint32_tcookie; /* cookie to synchronize
> two events */
> ++  uint32_tlen;/* length (including
> nulls) of name */
> ++  charname __flexarr; /* stub for possible name */
> ++};
> ++
> ++/* the following are legal, implemented events that user-space can watch
> for */
> ++#define IN_ACCESS 0x0001  /* File was accessed */
> ++#define IN_MODIFY 0x0002  /* File was modified */
> ++#define IN_ATTRIB 0x0004  /* Metadata changed */
> ++#define IN_CLOSE_WRITE0x0008  /* Writtable file
> was closed */
> ++#define IN_CLOSE_NOWRITE  0x0010  /* Unwrittable file closed
> */
> ++#define IN_OPEN   0x0020  /* File was opened
> */
> ++#define IN_MOVED_FROM 0x0040  /* File was moved from X */
> ++#define IN_MOVED_TO   0x0080  /* File was moved to Y */
> ++#define IN_CREATE 0x0100  /* Subfile was created */
> ++#define IN_DELETE 0x0200  /* Subfile was deleted */
> ++#define IN_DELETE_SELF0x0400  /* Self was
> deleted */
> ++#define IN_MOVE_SELF  0x0800  /* Self was moved */
> ++
> ++/* the following are legal events.  they are sent as needed to any watch
> */
> ++#define IN_UNMOUNT0x2000  /* Backing fs was
> unmounted */
> ++#define IN_Q_OVERFLOW 0x4000  /* Event queued overflowed
> */
> ++#define IN_IGNORED0x8000  /* File was ignored */
> ++
> ++/* helper events */
> ++#define IN_CLOSE  (IN_CLOSE_WRITE | IN_CLOSE_NOWRITE) /*
> close */
> ++#define IN_MOVE   (IN_MOVED_FROM | IN_MOVED_TO) /*
> moves 

[OpenWrt-Devel] [PATCH] ar71xx: Add Gainstrong MiniBox v1.0 support to 15.05

[Stijn Segers]

The following patch adds support for the Gainstrong MiniBox to 15.05 
Chaos Calmer.

Fixed items:

- Inverted LED polarity (OOLITE seems to suffer from the same problem).
- Changed uppercase MINIBOX_V1_ prefix as requested.
- Prefixes are now gs_minibox_ similar to gs_oolite_ (same vendor).
- Mention the vendor (Gainstrong) in code headers.

Compiles fine, has been confirmed working by owners. I assume it won't
be added to 15.05 post release but like this people who do want to migrate
their MiniBox to 15.05 don't need to fiddle with the patch for trunk.

Compile-tested by myself and confirmed working by owners.

Thank you

Signed-off by: Stijn Segers 

---
 target/linux/ar71xx/base-files/etc/diag.sh |  3 +
 .../ar71xx/base-files/etc/uci-defaults/02_network  |  1 +
 target/linux/ar71xx/base-files/lib/ar71xx.sh   |  6 ++
 .../ar71xx/base-files/lib/upgrade/platform.sh  |  1 +
 target/linux/ar71xx/config-3.18|  1 +
 .../files/arch/mips/ath79/mach-gs-minibox-v1.c | 85 ++
 target/linux/ar71xx/generic/profiles/minibox-v1.mk | 17 +
 target/linux/ar71xx/image/Makefile |  9 +++
 .../799-MIPS-ath79-add-minibox-v1-support.patch| 39 ++
 9 files changed, 162 insertions(+)
 create mode 100644 
target/linux/ar71xx/files/arch/mips/ath79/mach-gs-minibox-v1.c
 create mode 100644 target/linux/ar71xx/generic/profiles/minibox-v1.mk
 create mode 100644 
target/linux/ar71xx/patches-3.18/799-MIPS-ath79-add-minibox-v1-support.patch

diff --git a/target/linux/ar71xx/base-files/etc/diag.sh 
b/target/linux/ar71xx/base-files/etc/diag.sh
index ece7098..c1b7598 100644
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -212,6 +212,9 @@ get_status_led() {
smart-300)
status_led="nc-link:green:system"
;;
+   minibox-v1)
+   status_led="minibox-v1:green:system"
+   ;;
oolite)
status_led="oolite:red:system"
;;
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network 
b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
index 7e26886..4e7b8c6 100644
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
@@ -414,6 +414,7 @@ dir-615-e4 |\
 hiwifi-hc6361 |\
 ja76pf |\
 mc-mac1200r|\
+minibox-v1 |\
 mynet-n600 |\
 oolite |\
 qihoo-c301 |\
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh 
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index cacf362..f60f451 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -119,6 +119,9 @@ tplink_board_detect() {
"3C0001"*)
model="OOLITE"
;;
+   "3C0002"*)
+   model="MINIBOX_V1"
+   ;;
"070300"*)
model="TP-Link TL-WR703N"
;;
@@ -490,6 +493,9 @@ ar71xx_board_detect() {
*"MAC1200R")
name="mc-mac1200r"
;;
+   *"MiniBox V1.0")
+   name="minibox-v1"
+   ;;
*MR12)
name="mr12"
;;
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh 
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
index e5376ef..9e027ff 100755
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -311,6 +311,7 @@ platform_check_image() {
el-mini | \
gl-inet | \
mc-mac1200r | \
+   minibox-v1 |\
onion-omega | \
oolite | \
smart-300 | \
diff --git a/target/linux/ar71xx/config-3.18 b/target/linux/ar71xx/config-3.18
index d661aa7..ad861e1 100644
--- a/target/linux/ar71xx/config-3.18
+++ b/target/linux/ar71xx/config-3.18
@@ -68,6 +68,7 @@ CONFIG_ATH79_MACH_ESR900=y
 CONFIG_ATH79_MACH_EW_DORIN=y
 CONFIG_ATH79_MACH_F9K1115V2=y
 CONFIG_ATH79_MACH_GL_INET=y
+CONFIG_ATH79_MACH_GS_MINIBOX_V1=y
 CONFIG_ATH79_MACH_GS_OOLITE=y
 CONFIG_ATH79_MACH_HIWIFI_HC6361=y
 CONFIG_ATH79_MACH_HORNET_UB=y
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-gs-minibox-v1.c 
b/target/linux/ar71xx/files/arch/mips/ath79/mach-gs-minibox-v1.c
new file mode 100644
index 000..47eeb65
--- /dev/null
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-gs-minibox-v1.c
@@ -0,0 +1,85 @@
+/*
+ *  Gainstrong MiniBox V1.0 board support
+ *
+ *
+ *  This program is free software; you can redistribute it and/or modify it
+ *  under the terms of the GNU General Public License version 2 as published
+ *  by the Free Software Foundation.
+ */
+
+#include 
+
+#include 
+#include 
+
+#include "common.h"
+#include "dev-eth.h"
+#include "dev-gpio-buttons.h"
+#include "dev-leds-gpio.h"
+#include "dev-m25p80.h"
+#include "dev-usb.h"
+#include "dev-wmac.h"
+#include "machtypes.h"
+
+#define 

Re: [OpenWrt-Devel] [PATCH v2 0/7] target: mxs: various fixes

[Zoltan HERPAI]

Hi Michael,

Michael Heimpold wrote:

This patch series is to bring OpenWrt's Duckbill support back in shape:
- U-Boot build is fixed
- SD card generation is adopted for Duckbill images

I've tested my changes with I2SE Duckbill and Olimex OLinuXino
Maxi board, however, I've no Micro/Mini at hand.

This series obsoletes my series "packages: uboot-mxs: various fixes"
from Mon, 31 Aug 2015 21:49:28 +0200, so I've choosen to name this
one "v2".

It's possible to pull this series from
https://github.com/mhei/openwrt/tree/mxs-fixes, but I'm
rebasing this branch from time to time.

Changes in v2:
- don't break Olimex (i.MX233) based boards anymore
- SD card generation now support Duckbill's partitioning scheme

Michael Heimpold (7):
  packages: uboot-mxs: place binaries in the designated path
  

Committed this one.


  packages: uboot-mxs: do no modify the U-Boot image, copy as-is
  
I'm checking this - seems to break the i.MX233 support (olinuxino-maxi 
to be exact, but it shouldn't really matter with the imx23 boards), with 
this one in place, u-boot is not coming up, the board is stuck at the 
0x80502008 printouts. Might be PEBKAC on me.



  packages: uboot-mxs: bless UBOOT_IMAGE with a meaning, otherwise we
could drop this C left-over
  

I'm OK with this - will commit once we discussed the above.


  target/mxs: adopt SD card generation to fixed U-Boot path
  

As above.


  packages: uboot-mxs: fix I2SE Duckbill variant
  

Committed this one as well.


  tools: add sdimage (for mxs target)
  
  target: mxs: re-work SD card image generation
  
OK, so You're working with ext4+ext4 on Duckbill - happy to add these 
in, will take a look.


As always, thanks for the patches, the Duckbill support really needed 
some tender care.


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

Re: [OpenWrt-Devel] [PATCH] musl: fix build on sh3

[Zoltan HERPAI]

Felix Fietkau wrote:

On 2015-09-16 09:27, John Crispin wrote:
  

Hi,

On 14/09/2015 10:38, Zoltan HERPAI wrote:


musl fails to build when compiled with gcc on sh3 (GCC target/#67260).
Work it around.

Signed-off-by: Zoltan HERPAI 
---
 toolchain/musl/common.mk |5 +
 1 file changed, 5 insertions(+)

diff --git a/toolchain/musl/common.mk b/toolchain/musl/common.mk
index 82c1543..ba467fb 100644
--- a/toolchain/musl/common.mk
+++ b/toolchain/musl/common.mk
@@ -23,6 +23,11 @@
HOST_BUILD_DIR:=$(BUILD_DIR_TOOLCHAIN)/$(PKG_NAME)-$(PKG_VERSION)
 include $(INCLUDE_DIR)/toolchain-build.mk
 include $(INCLUDE_DIR)/hardening.mk

+ifeq ($(CONFIG_sh3),y)
+TARGET_CFLAGS+= \
+   -fno-optimize-sibling-calls
+endif
+
  

i am worried that this will be added and never removed as we will forget
about it. how about making it also depend on the broken gcc version.


There is no non-broken gcc version yet. I think we should at least have
a link to the gcc bug report directly above these lines, so we don't
have to dig through the log to figure out why this was added.
  
Can't argue with the need to have a link directly to describe the issue 
- I'll create a v2.


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

[OpenWrt-Devel] [PATCH v4] ar71xx: Add Gainstrong MiniBox v1.0 support to trunk

[Stijn Segers]

The following patch adds support for the Gainstrong MiniBox into trunk
(or 'Designated Drive' :D )..

Fixed items:

- Inverted LED polarity (OOLITE seems to suffer from the same problem).
- Changed uppercase MINIBOX_V1_ prefix as requested.
- Prefixes are now gs_minibox_ similar to gs_oolite_ (same vendor).
- Mention the vendor (Gainstrong) in code headers.

Compiles fine, has been confirmed working by owners on 15.05.

Question: I've seen some boards use tools/firmware-utils/src/mktplinkfw.c,
the MiniBox images build fine without, so I'm wondering: do I need to add
it in there as well? Any added benefit?

Thank you

Signed-off by: Stijn Segers 

---
 target/linux/ar71xx/base-files/etc/diag.sh |  3 +
 .../ar71xx/base-files/etc/uci-defaults/02_network  |  1 +
 target/linux/ar71xx/base-files/lib/ar71xx.sh   |  6 ++
 .../ar71xx/base-files/lib/upgrade/platform.sh  |  1 +
 target/linux/ar71xx/config-4.1 |  1 +
 .../files/arch/mips/ath79/mach-gs-minibox-v1.c | 85 ++
 target/linux/ar71xx/generic/profiles/minibox-v1.mk | 17 +
 target/linux/ar71xx/image/Makefile |  9 +++
 .../799-MIPS-ath79-add-minibox-v1-support.patch| 39 ++
 9 files changed, 162 insertions(+)
 create mode 100644 
target/linux/ar71xx/files/arch/mips/ath79/mach-gs-minibox-v1.c
 create mode 100644 target/linux/ar71xx/generic/profiles/minibox-v1.mk
 create mode 100644 
target/linux/ar71xx/patches-4.1/799-MIPS-ath79-add-minibox-v1-support.patch

diff --git a/target/linux/ar71xx/base-files/etc/diag.sh 
b/target/linux/ar71xx/base-files/etc/diag.sh
index cfba6b4..2732994 100644
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -225,6 +225,9 @@ get_status_led() {
smart-300)
status_led="nc-link:green:system"
;;
+   minibox-v1)
+   status_led="minibox-v1:green:system"
+   ;;
oolite)
status_led="oolite:red:system"
;;
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network 
b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
index 880953c..a93a9ad 100644
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
@@ -433,6 +433,7 @@ dir-615-e4 |\
 hiwifi-hc6361 |\
 ja76pf |\
 mc-mac1200r|\
+minibox-v1 |\
 mynet-n600 |\
 oolite |\
 qihoo-c301 |\
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh 
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index efb3d16..edaad73 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -119,6 +119,9 @@ tplink_board_detect() {
"3C0001"*)
model="OOLITE"
;;
+   "3C0002"*)
+   model="MINIBOX_V1"
+   ;;
"070300"*)
model="TP-Link TL-WR703N"
;;
@@ -514,6 +517,9 @@ ar71xx_board_detect() {
*"MAC1200R")
name="mc-mac1200r"
;;
+   *"MiniBox V1.0")
+   name="minibox-v1"
+   ;;
*MR12)
name="mr12"
;;
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh 
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
index cad8b43..043b6ed 100755
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -317,6 +317,7 @@ platform_check_image() {
el-mini | \
gl-inet | \
mc-mac1200r | \
+   minibox-v1 |\
onion-omega | \
oolite | \
smart-300 | \
diff --git a/target/linux/ar71xx/config-4.1 b/target/linux/ar71xx/config-4.1
index 51f2f2f..883d0d7 100644
--- a/target/linux/ar71xx/config-4.1
+++ b/target/linux/ar71xx/config-4.1
@@ -75,6 +75,7 @@ CONFIG_ATH79_MACH_ESR900=y
 CONFIG_ATH79_MACH_EW_DORIN=y
 CONFIG_ATH79_MACH_F9K1115V2=y
 CONFIG_ATH79_MACH_GL_INET=y
+CONFIG_ATH79_MACH_GS_MINIBOX_V1=y
 CONFIG_ATH79_MACH_GS_OOLITE=y
 CONFIG_ATH79_MACH_HIWIFI_HC6361=y
 CONFIG_ATH79_MACH_HORNET_UB=y
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-gs-minibox-v1.c 
b/target/linux/ar71xx/files/arch/mips/ath79/mach-gs-minibox-v1.c
new file mode 100644
index 000..47eeb65
--- /dev/null
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-gs-minibox-v1.c
@@ -0,0 +1,85 @@
+/*
+ *  Gainstrong MiniBox V1.0 board support
+ *
+ *
+ *  This program is free software; you can redistribute it and/or modify it
+ *  under the terms of the GNU General Public License version 2 as published
+ *  by the Free Software Foundation.
+ */
+
+#include 
+
+#include 
+#include 
+
+#include "common.h"
+#include "dev-eth.h"
+#include "dev-gpio-buttons.h"
+#include "dev-leds-gpio.h"
+#include "dev-m25p80.h"
+#include "dev-usb.h"
+#include "dev-wmac.h"
+#include "machtypes.h"
+
+#define 

[OpenWrt-Devel] [PATCH v2] lantiq: ARV7519RW22 fixes - fix flash register (only 1 flash) - power led is green - rename message leds to internet - add leds configuration - enable switch vlans

[Álvaro Fernández Rojas]

Signed-off-by: Álvaro Fernández Rojas 
Signed-off-by: José Vázquez Fernández 
---
 target/linux/lantiq/base-files/etc/uci-defaults/01_leds  |  5 +
 .../linux/lantiq/base-files/etc/uci-defaults/02_network  |  3 +++
 target/linux/lantiq/dts/ARV7519RW22.dts  | 16 
 3 files changed, 16 insertions(+), 8 deletions(-)

diff --git a/target/linux/lantiq/base-files/etc/uci-defaults/01_leds 
b/target/linux/lantiq/base-files/etc/uci-defaults/01_leds
index 8041ac9..6956d61 100644
--- a/target/linux/lantiq/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/lantiq/base-files/etc/uci-defaults/01_leds
@@ -51,6 +51,11 @@ P2812HNUF*)
ucidef_set_led_netdev "dsl" "dsl" "dsl" "nas0"
ucidef_set_led_netdev "internet_green" "internet_green" 
"internet_green" "pppoe-wan"
;;
+ARV7519RW22)
+   ucidef_set_led_default "power" "power" "power" "1"
+   ucidef_set_led_netdev "internet_green" "internet_green" 
"internet_green" "pppoe-wan"
+   ucidef_set_led_netdev "lan" "lan" "lan" "eth0.1"
+   ;;
 *)
;;
 esac
diff --git a/target/linux/lantiq/base-files/etc/uci-defaults/02_network 
b/target/linux/lantiq/base-files/etc/uci-defaults/02_network
index afb8714..721098e 100644
--- a/target/linux/lantiq/base-files/etc/uci-defaults/02_network
+++ b/target/linux/lantiq/base-files/etc/uci-defaults/02_network
@@ -162,6 +162,9 @@ TDW8970)
 ARV7519RW22)
lan_mac=$(mtd_get_mac_binary boardconfig 22)
wan_mac=$(macaddr_add "$lan_mac" 1)
+   ucidef_set_interface_lan "eth0.1"
+   ucidef_add_switch "switch0" "1" "1"
+   ucidef_add_switch_vlan "switch0" "1" "0 2 3 4 5 6t"
;;
 
 BTHOMEHUBV2B|BTHOMEHUBV3A)
diff --git a/target/linux/lantiq/dts/ARV7519RW22.dts 
b/target/linux/lantiq/dts/ARV7519RW22.dts
index 6823753..73d5487 100644
--- a/target/linux/lantiq/dts/ARV7519RW22.dts
+++ b/target/linux/lantiq/dts/ARV7519RW22.dts
@@ -18,7 +18,7 @@
nor-boot@0 {
compatible = "lantiq,nor";
bank-width = <2>;
-   reg = <0 0x0 0x200>, <1 0x200 
0x200>;
+   reg = <0 0x0 0x200>;
#address-cells = <1>;
#size-cells = <1>;
 
@@ -202,11 +202,11 @@
label = "lan";
gpios = < 2 1>;
};
-   message_red {
-   label = "message_red";
+   internet_red {
+   label = "internet_red";
gpios = < 10 1>;
};
-   power_red {
+   power_green {
label = "power";
gpios = < 14 1>;
default-state = "on";
@@ -215,12 +215,12 @@
label = "alarm";
gpios = < 15 1>;
};
-   message_orange {
-   label = "message_orange";
+   internet_orange {
+   label = "internet_orange";
gpios = < 19 1>;
};
-   message_green {
-   label = "message_green";
+   internet_green {
+   label = "internet_green";
gpios = < 28 1>;
};
voice_green {
-- 
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCHv2] musl: fix build on sh3

[Zoltan HERPAI]

musl fails to build when compiled with gcc on sh3 (GCC target/#67260).
Work it around.

Signed-off-by: Zoltan HERPAI 
---
 toolchain/musl/common.mk |6 ++
 1 file changed, 6 insertions(+)

diff --git a/toolchain/musl/common.mk b/toolchain/musl/common.mk
index 82c1543..3045c63 100644
--- a/toolchain/musl/common.mk
+++ b/toolchain/musl/common.mk
@@ -23,6 +23,12 @@ 
HOST_BUILD_DIR:=$(BUILD_DIR_TOOLCHAIN)/$(PKG_NAME)-$(PKG_VERSION)
 include $(INCLUDE_DIR)/toolchain-build.mk
 include $(INCLUDE_DIR)/hardening.mk
 
+# Please see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67260
+ifeq ($(CONFIG_sh3),y)
+TARGET_CFLAGS+= \
+   -fno-optimize-sibling-calls
+endif
+
 MUSL_CONFIGURE:= \
$(TARGET_CONFIGURE_OPTS) \
CFLAGS="$(TARGET_CFLAGS)" \
-- 
1.7.10.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [Patch 1/3] Update uboot-omap to 15.07

[Dirk Neukirchen]

On 17.09.2015 21:22, Tara Lorenz wrote:
> 
> Hello everybody,
> 
> the old uboot-omap package fails to compile when using gcc 5.x.
> Therefore i made a patch using a more recent version of u-boot.
> I decided to choose 15.07, the same version as currently used for the
> sunxi based boards.
> 
> So far i only tested that the package can now be compiled using
> gcc 5.x.  I can test functionality for beagle-board, beagle-bone
> and panda-board during the weekend, if that's needed.
> 
> I hope it's helpful somehow.
> 
> Cheers, Tara
> 

u-boot 2015.07 does not boot at my end.
Hardware: BeagleBoard C4 ("ebvbeagle")

I was doing some development locally and wanted to update u-boot but 
the MLO seems to be broken.
2015.04 works (all earlier versions work too)
2015.07 does not work (holding USR button, pressing RESET does not work)
2015.10-rc3 does not work

I used default gcc 4.8 to eliminate compile issues (backporting gcc5 patches 
to uboot 2013 works)

Please test the update on your 3 boards

working bootlog - as written before 2015.07 does not react/print anything:

U-Boot SPL 2015.04 (Sep 18 2015 - 08:05:03)
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
reading u-boot.img


U-Boot 2015.04 (Sep 18 2015 - 08:05:03)

OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 MHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

Beagle Rev C4
Timed out in wait_for_event: status=
Check if pads/pull-ups of bus 1 are properly configured
No EEPROM on expansion board
Die ID #2f920004040365fa16001013
Net:   usb_ether
Error: usb_ether address not set.

Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
gpio: pin 173 (gpio 173) value is 1
gpio: pin 7 (gpio 7) value is 0
SD/MMC found on device 0
reading uEnv.txt
488 bytes read in 5 ms (94.7 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
reading openwrt-omap-zImage
2081208 bytes read in 160 ms (12.4 MiB/s)
reading omap3-beagle.dtb
61168 bytes read in 12 ms (4.9 MiB/s)
Kernel image @ 0x8020 [ 0x00 - 0x1fc1b8 ]
## Flattened Device Tree blob at 80f8
   Booting using the fdt blob at 0x80f8
   Using Device Tree in place at 80f8, end 80f91eef

Starting kernel ...

[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 3.18.21 (tenchi@tenchi-htpc) (gcc version 4.8.3 
(OpenWrt/Linaro GCC 4.8-2014.04 r46986) ) #1 SMP Fri Sep 18 08:08:04 CEST 2015
[0.00] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing 
instruction cache
[0.00] Machine model: TI OMAP3 BeagleBoard
...


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

Re: [OpenWrt-Devel] [PATCH] procd: Allow override of default respawn parameters

[Etienne Champetier]

Hi,

2015-09-18 11:03 GMT+02:00 Helmut Schaa :

> Hi John,
>
> On Fri, Sep 18, 2015 at 10:18 AM, John Crispin  wrote:
> > Hi
> >
> > On 18/09/2015 09:59, Helmut Schaa wrote:
> >> Allow to pass RESPAWN_THESHOLD_DEFAULT, DRESPAWN_TIMEOUT_DEFAULT
> >> and RESPAWN_RETRY_DEFAULT as parameters to cmake to change the
> >> default respawn behavior.
> >>
> >
> > technically ok but why cant you tweak them in your packages initd script
> > ? i am wondering what the use case is and if there are other possible
> > solutions
>
> In our tree we've patched most (maybe even all) services to respawn forever
> (respawn_retry=-1). Including all OpenWrt provided services. Instead of
> keeping
> these local modifications to several packages it's easier to just
> override procds
> default behavior.
>
> I think there might be other people around running OpenWrt on headless
> boxes
> where the respawn retry should not be limited by default. However,
> this is of course
> not suitable for a default OpenWrt box.
>
> If there are good reasons not to include this in procd feel free to
> drop this patch.
> However, it causes zero runtime overhead and is quite simple.
>
> As a followup I'd add a config flag for procd "respawn_forver_mode" or so
> that
> just sets respawn_retry to -1.
>
> Helmut
>
> It would be great to be able to configure these settings at runtime (ie in
an uci file)

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

Re: [OpenWrt-Devel] [PATCH] procd: Allow override of default respawn parameters

[Helmut Schaa]

Hi John,

On Fri, Sep 18, 2015 at 10:18 AM, John Crispin  wrote:
> Hi
>
> On 18/09/2015 09:59, Helmut Schaa wrote:
>> Allow to pass RESPAWN_THESHOLD_DEFAULT, DRESPAWN_TIMEOUT_DEFAULT
>> and RESPAWN_RETRY_DEFAULT as parameters to cmake to change the
>> default respawn behavior.
>>
>
> technically ok but why cant you tweak them in your packages initd script
> ? i am wondering what the use case is and if there are other possible
> solutions

In our tree we've patched most (maybe even all) services to respawn forever
(respawn_retry=-1). Including all OpenWrt provided services. Instead of keeping
these local modifications to several packages it's easier to just
override procds
default behavior.

I think there might be other people around running OpenWrt on headless boxes
where the respawn retry should not be limited by default. However,
this is of course
not suitable for a default OpenWrt box.

If there are good reasons not to include this in procd feel free to
drop this patch.
However, it causes zero runtime overhead and is quite simple.

As a followup I'd add a config flag for procd "respawn_forver_mode" or so that
just sets respawn_retry to -1.

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

[OpenWrt-Devel] [PATCH] arm64: switch to Kernel 4.1

[Dirk Neukirchen]

- fix Kernel dts subdir location
- enable virtio networking
  we are using -M virt which supports virtio devices

changes in symbols due to make kernel_oldconfig:

- CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y : removed
fix security: upstream id: d1fd836dcf00d2028c700c7e44d2c23404062c90

- CONFIG_ARM64_CPU_SUSPEND: removed
commit id: af3cfdbf56b91785650f54e7c9a899d814b4b9fb

- CONFIG_ARM64_PGTABLE_LEVELS=3 : renamed PGTABLE_LEVELS
commit id: 9f25e6ad58e1fb3b4d441e4c55635c4598a6fa94

- CONFIG_GENERIC_CLOCKEVENTS_BUILD=y : removed upstream
commit id: 9f083b74df3a7eaa100b456f2dc195512daf728e

-# CONFIG_PREEMPT_RCU: unnecessary

unknown remove reasons:
-CONFIG_GENERIC_IOMAP=y
-# CONFIG_POWER_RESET_GPIO is not set
-# CONFIG_POWER_RESET_GPIO_RESTART is not set
-# CONFIG_POWER_RESET_LTC2952 is not set
-# CONFIG_POWER_RESET_SYSCON is not set
-# CONFIG_XEN is not set

tested and boot, networking work with qemu

Signed-off-by: Dirk Neukirchen 
---
 target/linux/arm64/Makefile|  2 +-
 target/linux/arm64/config-default  | 56 --
 target/linux/arm64/image/boot-wrapper/Makefile |  2 +-
 3 files changed, 46 insertions(+), 14 deletions(-)

diff --git a/target/linux/arm64/Makefile b/target/linux/arm64/Makefile
index 8292cfe..25ece9a 100644
--- a/target/linux/arm64/Makefile
+++ b/target/linux/arm64/Makefile
@@ -13,7 +13,7 @@ FEATURES:=fpu ramdisk
 CFLAGS:=-Os -pipe -fno-caller-saves
 MAINTAINER:=Florian Fainelli 
 
-KERNEL_PATCHVER:=3.18
+KERNEL_PATCHVER:=4.1
 
 DEVICE_TYPE:=developerboard
 
diff --git a/target/linux/arm64/config-default 
b/target/linux/arm64/config-default
index 1ff61d5..55d333d 100644
--- a/target/linux/arm64/config-default
+++ b/target/linux/arm64/config-default
@@ -1,16 +1,31 @@
 CONFIG_64BIT=y
-CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y
+CONFIG_ACPI=y
+# CONFIG_ACPI_CONTAINER is not set
+# CONFIG_ACPI_CUSTOM_DSDT is not set
+# CONFIG_ACPI_DEBUG is not set
+# CONFIG_ACPI_DOCK is not set
+# CONFIG_ACPI_EC_DEBUGFS is not set
+CONFIG_ACPI_GENERIC_GSI=y
+# CONFIG_ACPI_PCI_SLOT is not set
+# CONFIG_ACPI_PROCFS_POWER is not set
+CONFIG_ACPI_REDUCED_HARDWARE_ONLY=y
 CONFIG_ARCH_DMA_ADDR_T_64BIT=y
+# CONFIG_ARCH_EXYNOS7 is not set
+# CONFIG_ARCH_FSL_LS2085A is not set
 CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y
 CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
+CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
+CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
 CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
 CONFIG_ARCH_HAS_SG_CHAIN=y
 CONFIG_ARCH_HAS_TICK_BROADCAST=y
 CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
 CONFIG_ARCH_REQUIRE_GPIOLIB=y
+# CONFIG_ARCH_SEATTLE is not set
 CONFIG_ARCH_SELECT_MEMORY_MODEL=y
 CONFIG_ARCH_SPARSEMEM_DEFAULT=y
 CONFIG_ARCH_SPARSEMEM_ENABLE=y
+# CONFIG_ARCH_SPRD is not set
 CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
 CONFIG_ARCH_SUSPEND_POSSIBLE=y
 # CONFIG_ARCH_THUNDER is not set
@@ -22,10 +37,10 @@ CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
 CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
 CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
 # CONFIG_ARCH_XGENE is not set
+# CONFIG_ARCH_ZYNQMP is not set
 CONFIG_ARM64=y
 CONFIG_ARM64_4K_PAGES=y
 # CONFIG_ARM64_64K_PAGES is not set
-# CONFIG_ARM64_CPU_SUSPEND is not set
 # CONFIG_ARM64_CRYPTO is not set
 CONFIG_ARM64_ERRATUM_819472=y
 CONFIG_ARM64_ERRATUM_824069=y
@@ -33,11 +48,12 @@ CONFIG_ARM64_ERRATUM_826319=y
 CONFIG_ARM64_ERRATUM_827319=y
 CONFIG_ARM64_ERRATUM_832075=y
 CONFIG_ARM64_ERRATUM_845719=y
-CONFIG_ARM64_PGTABLE_LEVELS=3
+# CONFIG_ARM64_PTDUMP is not set
 # CONFIG_ARM64_RANDOMIZE_TEXT_OFFSET is not set
 CONFIG_ARM64_VA_BITS=39
 CONFIG_ARM64_VA_BITS_39=y
 # CONFIG_ARM64_VA_BITS_48 is not set
+# CONFIG_ARMV8_DEPRECATED is not set
 CONFIG_ARM_AMBA=y
 CONFIG_ARM_ARCH_TIMER=y
 CONFIG_ARM_ARCH_TIMER_EVTSTREAM=y
@@ -46,6 +62,7 @@ CONFIG_ARM_GIC_V3=y
 # CONFIG_ARM_SP805_WATCHDOG is not set
 CONFIG_ATOMIC64_SELFTEST=y
 CONFIG_AUDIT_ARCH_COMPAT_GENERIC=y
+CONFIG_AVERAGE=y
 CONFIG_BLK_DEV_SD=y
 CONFIG_BLOCK_COMPAT=y
 CONFIG_BOUNCE=y
@@ -73,6 +90,8 @@ CONFIG_CRC16=y
 CONFIG_CRYPTO_CRC32C=y
 CONFIG_CRYPTO_HASH=y
 CONFIG_CRYPTO_HASH2=y
+CONFIG_CRYPTO_RNG2=y
+CONFIG_CRYPTO_WORKQUEUE=y
 CONFIG_CUSE=y
 CONFIG_DCACHE_WORD_ACCESS=y
 CONFIG_DEBUG_INFO=y
@@ -92,20 +111,22 @@ CONFIG_FB_CFB_FILLRECT=y
 CONFIG_FB_CFB_IMAGEBLIT=y
 CONFIG_FB_CMDLINE=y
 CONFIG_FB_MODE_HELPERS=y
+# CONFIG_FB_SM750 is not set
 CONFIG_FIX_EARLYCON_MEM=y
 CONFIG_FRAME_POINTER=y
+# CONFIG_FSL_MC_BUS is not set
+# CONFIG_FS_DAX is not set
 CONFIG_FS_MBCACHE=y
 CONFIG_FUSE_FS=y
 CONFIG_GENERIC_ALLOCATOR=y
 CONFIG_GENERIC_CLOCKEVENTS=y
 CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
-CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
 CONFIG_GENERIC_CPU_AUTOPROBE=y
 CONFIG_GENERIC_CSUM=y
 CONFIG_GENERIC_EARLY_IOREMAP=y
 CONFIG_GENERIC_IO=y
-CONFIG_GENERIC_IOMAP=y
 CONFIG_GENERIC_IRQ_SHOW=y
+CONFIG_GENERIC_IRQ_SHOW_LEVEL=y
 CONFIG_GENERIC_PCI_IOMAP=y
 CONFIG_GENERIC_SCHED_CLOCK=y
 CONFIG_GENERIC_SMP_IDLE_THREAD=y
@@ -113,6 +134,7 @@ CONFIG_GENERIC_STRNCPY_FROM_USER=y
 CONFIG_GENERIC_STRNLEN_USER=y
 

[OpenWrt-Devel] [PATCH] can: disable xilinx CAN

[Dirk Neukirchen]

fix missing symbol on arm64

Signed-off-by: Dirk Neukirchen 
---
 package/kernel/linux/modules/can.mk | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/kernel/linux/modules/can.mk 
b/package/kernel/linux/modules/can.mk
index f9490b4..eeef88a 100644
--- a/package/kernel/linux/modules/can.mk
+++ b/package/kernel/linux/modules/can.mk
@@ -26,6 +26,7 @@ define KernelPackage/can
CONFIG_CAN_MSCAN=n \
CONFIG_CAN_SJA1000=n \
CONFIG_CAN_SOFTING=n \
+   CONFIG_CAN_XILINXCAN=n \
CONFIG_NET_EMATCH_CANID=n \
CONFIG_CAN_DEBUG_DEVICES=n
   FILES:=$(LINUX_DIR)/drivers/net/can/can-dev.ko \
-- 
2.5.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] [RFC] toolchain: add OCaml compiler

[Stefan Hellermann]

A few ideas about the large binaries compiled with OCaml:

- Currently each OCaml binary contains the OCaml bytecode and the full
OCaml interpreter. This is okay if there is only one binary (in my case
unison), but wasteful in case of multiple binaries on the target. It should
be possible to create a package ocaml-runtime for the target. This would
allow to strip the binaries, which removes the interpreter but leaves the
bytecode.

- There is a patch in debian to allow stipping of OCaml binaries with
included OCaml interpreter:
http://patches.osdyson.org/patch/series/view/ocaml/4.01.0-3+dyson1/0008-Embed-bytecode-in-C-object-when-using-custom.patch
Sadly I haven't got it to work on openwrt.

- OCaml allows native code compilation to get more performance and smaller
binaries. But this is only supported on a few archs (x86, arm, powerpc and
sparc) so I haven't implemented it.

Stefan

2015-09-17 22:40 GMT+02:00 Bastian Bittorf :

> * Stefan Hellermann  [17.09.2015 20:00]:
> > Tested with Unison File Synchronizer on ar71xx and x86_64. Beware:
> > Stripping unison won't work!
> > Better solutions and comments are appreciated!
> >
> > Signed-off-by: Stefan Hellermann 
>
> thank you!
>
> tested and works for me on ar71xx.
> the resulting unison-binary is a little
> bit fat (~2mb gzipped) but thats not your fault 8-)
>
> bye, bastian
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] procd: Allow override of default respawn parameters

[Helmut Schaa]

Allow to pass RESPAWN_THESHOLD_DEFAULT, DRESPAWN_TIMEOUT_DEFAULT
and RESPAWN_RETRY_DEFAULT as parameters to cmake to change the
default respawn behavior.

This can be used to set the default respawn mode to infinite retries
for example.

Signed-off-by: Helmut Schaa 
---
 CMakeLists.txt | 12 
 service/instance.c |  4 +++-
 service/instance.h | 12 +++-
 3 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/CMakeLists.txt b/CMakeLists.txt
index 6af17a3..721a381 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -23,6 +23,18 @@ SET(SOURCES procd.c signal.c watchdog.c state.c  
inittab.c rcS.c ubus.c system.c
 
 SET(LIBS ubox ubus json-c blobmsg_json json_script)
 
+IF(RESPAWN_THESHOLD_DEFAULT)
+  ADD_DEFINITIONS(-DRESPAWN_THESHOLD_DEFAULT=${RESPAWN_THESHOLD_DEFAULT})
+ENDIF()
+
+IF(RESPAWN_TIMEOUT_DEFAULT)
+  ADD_DEFINITIONS(-DRESPAWN_TIMEOUT_DEFAULT=${RESPAWN_TIMEOUT_DEFAULT})
+ENDIF()
+
+IF(RESPAWN_RETRY_DEFAULT)
+  ADD_DEFINITIONS(-DRESPAWN_RETRY_DEFAULT=${RESPAWN_RETRY_DEFAULT})
+ENDIF()
+
 IF(DEBUG)
   ADD_DEFINITIONS(-DDEBUG -g3)
 ENDIF()
diff --git a/service/instance.c b/service/instance.c
index 40ff021..9d4df7c 100644
--- a/service/instance.c
+++ b/service/instance.c
@@ -709,7 +709,9 @@ instance_config_parse(struct service_instance *in)
 
if (tb[INSTANCE_ATTR_RESPAWN]) {
int i = 0;
-   uint32_t vals[3] = { 3600, 5, 5};
+   uint32_t vals[3] = { RESPAWN_THRESHOLD_DEFAULT,
+RESPAWN_TIMEOUT_DEFAULT,
+RESPAWN_RETRY_DEFAULT };
 
blobmsg_for_each_attr(cur2, tb[INSTANCE_ATTR_RESPAWN], rem) {
if ((i >= 3) && (blobmsg_type(cur2) == 
BLOBMSG_TYPE_STRING))
diff --git a/service/instance.h b/service/instance.h
index 3fb33e9..ab05f20 100644
--- a/service/instance.h
+++ b/service/instance.h
@@ -20,7 +20,17 @@
 #include 
 #include "../utils/utils.h"
 
-#define RESPAWN_ERROR  (5 * 60)
+#ifndef RESPAWN_THRESHOLD_DEFAULT
+#define RESPAWN_THRESHOLD_DEFAULT 3600
+#endif
+
+#ifndef RESPAWN_TIMEOUT_DEFAULT
+#define RESPAWN_TIMEOUT_DEFAULT 5
+#endif
+
+#ifndef RESPAWN_RETRY_DEFAULT
+#define RESPAWN_RETRY_DEFAULT 5
+#endif
 
 struct jail {
bool procfs;
-- 
1.8.4.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Patch 210-dnssec-improve-timestamp-heuristic.patch fails when building DNSMASQ-full

[Derek Werthmuller]

Not sure why building dnsmasq-full on cc 15.05 for sunxi this patch Patch
210-dnssec-improve-timestamp-heuristic.patch fails.  If I remove that patch
the build continues successfully, but don't want to miss a patch that
should be there. I believe that I'm using the dnsmasq 2.7.5 from
https://dev.openwrt.org/browser/trunk/package/network/services/dnsmasq

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

Re: [OpenWrt-Devel] how to build two sub target simultaneously under same target

[Sami Olmari]

This is not an support channel... but I'll answer you best of mine
abilities: you do have thing called "env".. this allows you to use same
sourcecodes for multiple devices and their configurations. More info about
that http://wiki.openwrt.org/doc/devel/env

This allows you to build whatever targets (even multiple times same) with
whatever config each. Nothing does automatically build everything, but you
can make simple script that builds one, changes env, builds another... Best
thing I know to have currently, without modifying anything heavily.

 Sami Olmari

On Fri, Sep 18, 2015 at 7:56 PM, punith kumar  wrote:

> Dear Openwrt-devel,
>
> I want to know if it is possible to setup build environment to compile
> two sub-target simultaneously which will use same toolchain options,
> build environment and etc.
> Simultaneously both sub-targets should be configurable as a prerequisite
>
> Thanks in advance for any sort of suggestion and direction
>
> Regards,
> Punith Kumar
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [RFC] netifd: backport support of checkup_interval option

[Felix Fietkau]

On 2015-09-18 03:58, Yousong Zhou wrote:
> This is needed for L2TP with xl2tpd daemon.
> 
> Signed-off-by: Yousong Zhou 
> ---
> Another option would be bump the netifd version to the lastest, but I am a bit
> conservative now.  That said, I plan to backport xl2tpd from trunk to
> packages;for-15.05 after this checkup_interval option will be available in CC
> as the current version there does not work at all [1]
I'm currently preparing a backport of latest netifd to CC, because we
also need the updated multicast-to-unicast fixes there.

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

[OpenWrt-Devel] [PATCH] netifd: Prevent flapping IPv6 routes

[Kristian Evensen]

From: Kristian Evensen 

Comparing valid_until will always return false as the value is updated for each
route update message. This causes IPv6 routes to jump more around than House of
Pain, which might have undesirable consequences for user-space and user-space
applications.

Removing the valid_until comparison when setting keep fixes this problem, and
seems to have no side-effects. I am no IPv6 expert, but I see that valid of the
route is updated correctly and route is deleted if I block the route update
messages.

Signed-off-by: Kristian Evensen 
---
 interface-ip.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/interface-ip.c b/interface-ip.c
index 8eb2ff3..4a2ee35 100644
--- a/interface-ip.c
+++ b/interface-ip.c
@@ -591,7 +591,7 @@ interface_update_proto_route(struct vlist_tree *tree,
if (node_old && node_new)
keep = !memcmp(_old->nexthop, _new->nexthop, 
sizeof(route_old->nexthop)) &&
(route_old->mtu == route_new->mtu) && (route_old->type 
== route_new->type) &&
-   (route_old->valid_until == route_new->valid_until) && 
!route_old->failed;
+   !route_old->failed;
 
if (node_old) {
if (!(route_old->flags & DEVADDR_EXTERNAL) && 
route_old->enabled && !keep)
-- 
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] procd: Allow override of default respawn parameters

[John Crispin]

Hi

On 18/09/2015 09:59, Helmut Schaa wrote:
> Allow to pass RESPAWN_THESHOLD_DEFAULT, DRESPAWN_TIMEOUT_DEFAULT
> and RESPAWN_RETRY_DEFAULT as parameters to cmake to change the
> default respawn behavior.
> 

technically ok but why cant you tweak them in your packages initd script
? i am wondering what the use case is and if there are other possible
solutions


> This can be used to set the default respawn mode to infinite retries
> for example.
> 

it can already to that.


John



> Signed-off-by: Helmut Schaa 
> ---
>  CMakeLists.txt | 12 
>  service/instance.c |  4 +++-
>  service/instance.h | 12 +++-
>  3 files changed, 26 insertions(+), 2 deletions(-)
> 
> diff --git a/CMakeLists.txt b/CMakeLists.txt
> index 6af17a3..721a381 100644
> --- a/CMakeLists.txt
> +++ b/CMakeLists.txt
> @@ -23,6 +23,18 @@ SET(SOURCES procd.c signal.c watchdog.c state.c
> inittab.c rcS.c ubus.c system.c
>  
>  SET(LIBS ubox ubus json-c blobmsg_json json_script)
>  
> +IF(RESPAWN_THESHOLD_DEFAULT)
> +  ADD_DEFINITIONS(-DRESPAWN_THESHOLD_DEFAULT=${RESPAWN_THESHOLD_DEFAULT})
> +ENDIF()
> +
> +IF(RESPAWN_TIMEOUT_DEFAULT)
> +  ADD_DEFINITIONS(-DRESPAWN_TIMEOUT_DEFAULT=${RESPAWN_TIMEOUT_DEFAULT})
> +ENDIF()
> +
> +IF(RESPAWN_RETRY_DEFAULT)
> +  ADD_DEFINITIONS(-DRESPAWN_RETRY_DEFAULT=${RESPAWN_RETRY_DEFAULT})
> +ENDIF()
> +
>  IF(DEBUG)
>ADD_DEFINITIONS(-DDEBUG -g3)
>  ENDIF()
> diff --git a/service/instance.c b/service/instance.c
> index 40ff021..9d4df7c 100644
> --- a/service/instance.c
> +++ b/service/instance.c
> @@ -709,7 +709,9 @@ instance_config_parse(struct service_instance *in)
>  
>   if (tb[INSTANCE_ATTR_RESPAWN]) {
>   int i = 0;
> - uint32_t vals[3] = { 3600, 5, 5};
> + uint32_t vals[3] = { RESPAWN_THRESHOLD_DEFAULT,
> +  RESPAWN_TIMEOUT_DEFAULT,
> +  RESPAWN_RETRY_DEFAULT };
>  
>   blobmsg_for_each_attr(cur2, tb[INSTANCE_ATTR_RESPAWN], rem) {
>   if ((i >= 3) && (blobmsg_type(cur2) == 
> BLOBMSG_TYPE_STRING))
> diff --git a/service/instance.h b/service/instance.h
> index 3fb33e9..ab05f20 100644
> --- a/service/instance.h
> +++ b/service/instance.h
> @@ -20,7 +20,17 @@
>  #include 
>  #include "../utils/utils.h"
>  
> -#define RESPAWN_ERROR(5 * 60)
> +#ifndef RESPAWN_THRESHOLD_DEFAULT
> +#define RESPAWN_THRESHOLD_DEFAULT 3600
> +#endif
> +
> +#ifndef RESPAWN_TIMEOUT_DEFAULT
> +#define RESPAWN_TIMEOUT_DEFAULT 5
> +#endif
> +
> +#ifndef RESPAWN_RETRY_DEFAULT
> +#define RESPAWN_RETRY_DEFAULT 5
> +#endif
>  
>  struct jail {
>   bool procfs;
> 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] procd: Allow override of default respawn parameters

[John Crispin]

On 18/09/2015 11:40, Etienne Champetier wrote:
> Hi,
> 
> 2015-09-18 11:03 GMT+02:00 Helmut Schaa  >:
> 
> Hi John,
> 
> On Fri, Sep 18, 2015 at 10:18 AM, John Crispin  > wrote:
> > Hi
> >
> > On 18/09/2015 09:59, Helmut Schaa wrote:
> >> Allow to pass RESPAWN_THESHOLD_DEFAULT, DRESPAWN_TIMEOUT_DEFAULT
> >> and RESPAWN_RETRY_DEFAULT as parameters to cmake to change the
> >> default respawn behavior.
> >>
> >
> > technically ok but why cant you tweak them in your packages initd script
> > ? i am wondering what the use case is and if there are other possible
> > solutions
> 
> In our tree we've patched most (maybe even all) services to respawn
> forever
> (respawn_retry=-1). Including all OpenWrt provided services. Instead
> of keeping
> these local modifications to several packages it's easier to just
> override procds
> default behavior.
> 
> I think there might be other people around running OpenWrt on
> headless boxes
> where the respawn retry should not be limited by default. However,
> this is of course
> not suitable for a default OpenWrt box.
> 
> If there are good reasons not to include this in procd feel free to
> drop this patch.
> However, it causes zero runtime overhead and is quite simple.
> 
> As a followup I'd add a config flag for procd "respawn_forver_mode"
> or so that
> just sets respawn_retry to -1.
> 
> Helmut
> 
> It would be great to be able to configure these settings at runtime (ie
> in an uci file)
>
> Etienne
>

agreed, i think the best would be to add support for -1 == endless
respawn and then change procd.sh to use current values as default but
allow overriding them vom /etc/config/system or similar. would that
solve your use case ?

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

[OpenWrt-Devel] [PATCH] package: Remove dependencies to kmod-ipv6

[Arjen de Korte]

Since r46834, IPv6 support is builtin if selected. Therefor, dependencies
on kmod-ipv6 can no longer be fulfilled, since it is not a module anymore.

Signed-off-by: Arjen de Korte 
---
 package/kernel/linux/modules/netfilter.mk | 6 +++---
 package/network/config/gre/Makefile   | 2 +-
 package/network/ipv6/6in4/Makefile| 2 +-
 package/network/ipv6/6rd/Makefile | 2 +-
 package/network/ipv6/6to4/Makefile| 2 +-
 package/network/ipv6/ds-lite/Makefile | 2 +-
 package/network/ipv6/map/Makefile | 2 +-
 package/network/ipv6/odhcp6c/Makefile | 2 +-
 package/network/services/dnsmasq/Makefile | 2 +-
 package/network/utils/xtables-addons/Makefile | 2 +-
 10 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/package/kernel/linux/modules/netfilter.mk 
b/package/kernel/linux/modules/netfilter.mk
index 3a436ac..e21895d 100644
--- a/package/kernel/linux/modules/netfilter.mk
+++ b/package/kernel/linux/modules/netfilter.mk
@@ -80,7 +80,7 @@ define KernelPackage/nf-conntrack6
   SUBMENU:=$(NF_MENU)
   TITLE:=Netfilter IPv6 connection tracking
   KCONFIG:=$(KCONFIG_NF_CONNTRACK6)
-  DEPENDS:=+kmod-ipv6 +kmod-nf-conntrack
+  DEPENDS:=@IPV6 +kmod-nf-conntrack
   FILES:=$(foreach mod,$(NF_CONNTRACK6-m),$(LINUX_DIR)/net/$(mod).ko)
   AUTOLOAD:=$(call AutoProbe,$(notdir $(NF_CONNTRACK6-m)))
 endef
@@ -454,7 +454,7 @@ $(eval $(call KernelPackage,ipt-led))
 
 define KernelPackage/ipt-tproxy
   TITLE:=Transparent proxying support
-  DEPENDS+=+kmod-ipt-conntrack +IPV6:kmod-ipv6 +IPV6:kmod-ip6tables
+  DEPENDS+=+kmod-ipt-conntrack +IPV6:kmod-ip6tables
   KCONFIG:= \
CONFIG_NETFILTER_TPROXY \
CONFIG_NETFILTER_XT_MATCH_SOCKET \
@@ -473,7 +473,7 @@ $(eval $(call KernelPackage,ipt-tproxy))
 
 define KernelPackage/ipt-tee
   TITLE:=TEE support
-  DEPENDS:=+kmod-ipt-conntrack +IPV6:kmod-ipv6
+  DEPENDS:=+kmod-ipt-conntrack
   KCONFIG:= \
CONFIG_NETFILTER_XT_TARGET_TEE
   FILES:= \
diff --git a/package/network/config/gre/Makefile 
b/package/network/config/gre/Makefile
index 217c276..49e7d19 100644
--- a/package/network/config/gre/Makefile
+++ b/package/network/config/gre/Makefile
@@ -42,7 +42,7 @@ endef
 define Package/grev6
 $(call Package/gre/Default)
   TITLE:=Generic Routing Encapsulation (IPv6) config support
-  DEPENDS:=@(PACKAGE_gre) +kmod-ipv6 +kmod-ip6-gre
+  DEPENDS:=@(PACKAGE_gre) @IPV6 +kmod-ip6-gre
 endef
 
 define Package/grev6/description
diff --git a/package/network/ipv6/6in4/Makefile 
b/package/network/ipv6/6in4/Makefile
index b7c2da7..2ffdfc0 100644
--- a/package/network/ipv6/6in4/Makefile
+++ b/package/network/ipv6/6in4/Makefile
@@ -17,7 +17,7 @@ include $(INCLUDE_DIR)/package.mk
 define Package/6in4
   SECTION:=net
   CATEGORY:=Network
-  DEPENDS:=+kmod-ipv6 +kmod-sit
+  DEPENDS:=@IPV6 +kmod-sit
   TITLE:=IPv6-in-IPv4 configuration support
   MAINTAINER:=Jo-Philipp Wich 
   PKGARCH:=all
diff --git a/package/network/ipv6/6rd/Makefile 
b/package/network/ipv6/6rd/Makefile
index cde7117..04d607e 100644
--- a/package/network/ipv6/6rd/Makefile
+++ b/package/network/ipv6/6rd/Makefile
@@ -17,7 +17,7 @@ include $(INCLUDE_DIR)/package.mk
 define Package/6rd
   SECTION:=net
   CATEGORY:=Network
-  DEPENDS:=+kmod-ipv6 +kmod-sit
+  DEPENDS:=@IPV6 +kmod-sit
   TITLE:=6rd configuration support
   MAINTAINER:=Steven Barth 
   PKGARCH:=all
diff --git a/package/network/ipv6/6to4/Makefile 
b/package/network/ipv6/6to4/Makefile
index fcec90d..20605f6 100644
--- a/package/network/ipv6/6to4/Makefile
+++ b/package/network/ipv6/6to4/Makefile
@@ -17,7 +17,7 @@ include $(INCLUDE_DIR)/package.mk
 define Package/6to4
   SECTION:=net
   CATEGORY:=Network
-  DEPENDS:=+kmod-ipv6 +kmod-sit
+  DEPENDS:=@IPV6 +kmod-sit
   TITLE:=IPv6-to-IPv4 configuration support
   MAINTAINER:=Jo-Philipp Wich 
   PKGARCH:=all
diff --git a/package/network/ipv6/ds-lite/Makefile 
b/package/network/ipv6/ds-lite/Makefile
index 8c22c46..919ac7e 100644
--- a/package/network/ipv6/ds-lite/Makefile
+++ b/package/network/ipv6/ds-lite/Makefile
@@ -17,7 +17,7 @@ include $(INCLUDE_DIR)/package.mk
 define Package/ds-lite
   SECTION:=net
   CATEGORY:=Network
-  DEPENDS:=+kmod-ipv6 +kmod-ip6-tunnel +resolveip
+  DEPENDS:=@IPV6 +kmod-ip6-tunnel +resolveip
   TITLE:=Dual-Stack Lite (DS-Lite) configuration support
   MAINTAINER:=Steven Barth 
   PKGARCH:=all
diff --git a/package/network/ipv6/map/Makefile 
b/package/network/ipv6/map/Makefile
index f6f2cd6..af6f758 100644
--- a/package/network/ipv6/map/Makefile
+++ b/package/network/ipv6/map/Makefile
@@ -18,7 +18,7 @@ include $(INCLUDE_DIR)/cmake.mk
 define Package/map
   SECTION:=net
   CATEGORY:=Network
-  DEPENDS:=+kmod-ipv6 +kmod-ip6-tunnel +libubox +libubus 
+iptables-mod-conntrack-extra
+  DEPENDS:=@IPV6 +kmod-ip6-tunnel +libubox +libubus 
+iptables-mod-conntrack-extra
   TITLE:=MAP-E and Lightweight 4over6 configuration 

[OpenWrt-Devel] omap: add Kernel 4.1

[Dirk Neukirchen]

tested on Beagleboard C4

Signed-off-by: Dirk Neukirchen 
---
bootlog: https://paste.debian.net/312304/

 target/linux/omap/config-4.1   | 540 +
 .../0334-video-da8xx-fb-adding-dt-support.patch| 201 
 ...-fb-Add-API-to-register-wait-for-vsync-ca.patch |  91 
 ...-fb-fix-defect-with-vsync-callback-invoca.patch |  38 ++
 ...ts-am335x-evmsk-add-support-for-lcd-panel.patch |  70 +++
 .../patches-4.1/950-am335x-evmsk-wilink-dts.patch  |  79 +++
 6 files changed, 1019 insertions(+)
 create mode 100644 target/linux/omap/config-4.1
 create mode 100644 
target/linux/omap/patches-4.1/0334-video-da8xx-fb-adding-dt-support.patch
 create mode 100644 
target/linux/omap/patches-4.1/0343-video-da8xx-fb-Add-API-to-register-wait-for-vsync-ca.patch
 create mode 100644 
target/linux/omap/patches-4.1/0752-video-da8xx-fb-fix-defect-with-vsync-callback-invoca.patch
 create mode 100644 
target/linux/omap/patches-4.1/920-arm-dts-am335x-evmsk-add-support-for-lcd-panel.patch
 create mode 100644 
target/linux/omap/patches-4.1/950-am335x-evmsk-wilink-dts.patch

diff --git a/target/linux/omap/config-4.1 b/target/linux/omap/config-4.1
new file mode 100644
index 000..14f13f0
--- /dev/null
+++ b/target/linux/omap/config-4.1
@@ -0,0 +1,540 @@
+CONFIG_ALIGNMENT_TRAP=y
+# CONFIG_APM_EMULATION is not set
+CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y
+CONFIG_ARCH_HAS_BANDGAP=y
+CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
+CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
+CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
+CONFIG_ARCH_HAS_SG_CHAIN=y
+CONFIG_ARCH_HAS_TICK_BROADCAST=y
+CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y
+CONFIG_ARCH_HIBERNATION_POSSIBLE=y
+CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
+CONFIG_ARCH_MULTIPLATFORM=y
+# CONFIG_ARCH_MULTI_CPU_AUTO is not set
+CONFIG_ARCH_MULTI_V6_V7=y
+CONFIG_ARCH_MULTI_V7=y
+CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED=y
+CONFIG_ARCH_NR_GPIO=0
+CONFIG_ARCH_OMAP=y
+CONFIG_ARCH_OMAP2PLUS=y
+CONFIG_ARCH_OMAP2PLUS_TYPICAL=y
+CONFIG_ARCH_OMAP3=y
+CONFIG_ARCH_OMAP4=y
+CONFIG_ARCH_REQUIRE_GPIOLIB=y
+# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set
+# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set
+CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
+CONFIG_ARCH_SUPPORTS_UPROBES=y
+CONFIG_ARCH_SUSPEND_POSSIBLE=y
+CONFIG_ARCH_USE_BUILTIN_BSWAP=y
+CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
+CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
+CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y
+CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
+CONFIG_ARM=y
+# CONFIG_ARM_CPUIDLE is not set
+CONFIG_ARM_CPU_SUSPEND=y
+CONFIG_ARM_ERRATA_720789=y
+CONFIG_ARM_ERRATA_754322=y
+CONFIG_ARM_ERRATA_775420=y
+CONFIG_ARM_GIC=y
+CONFIG_ARM_HAS_SG_CHAIN=y
+CONFIG_ARM_L1_CACHE_SHIFT=6
+CONFIG_ARM_L1_CACHE_SHIFT_6=y
+# CONFIG_ARM_LPAE is not set
+CONFIG_ARM_OMAP2PLUS_CPUFREQ=y
+CONFIG_ARM_PATCH_PHYS_VIRT=y
+CONFIG_ARM_THUMB=y
+# CONFIG_ARM_THUMBEE is not set
+CONFIG_ARM_VIRT_EXT=y
+CONFIG_AT803X_PHY=y
+CONFIG_AUTO_ZRELADDR=y
+CONFIG_AVERAGE=y
+CONFIG_BACKLIGHT_CLASS_DEVICE=y
+# CONFIG_BACKLIGHT_GENERIC is not set
+CONFIG_BACKLIGHT_LCD_SUPPORT=y
+CONFIG_BACKLIGHT_PWM=y
+# CONFIG_BACKLIGHT_TPS65217 is not set
+CONFIG_BCH=y
+CONFIG_BOUNCE=y
+CONFIG_CACHE_L2X0=y
+CONFIG_CLKDEV_LOOKUP=y
+CONFIG_CLKSRC_MMIO=y
+CONFIG_CLKSRC_OF=y
+# CONFIG_CLK_TWL6040 is not set
+CONFIG_CLONE_BACKWARDS=y
+CONFIG_CMDLINE="console=ttyO0,115200n8"
+CONFIG_COMMON_CLK=y
+CONFIG_CONSOLE_TRANSLATIONS=y
+# CONFIG_CPUFREQ_DT is not set
+CONFIG_CPU_32v6K=y
+CONFIG_CPU_32v7=y
+CONFIG_CPU_ABRT_EV7=y
+# CONFIG_CPU_BPREDICT_DISABLE is not set
+CONFIG_CPU_CACHE_V7=y
+CONFIG_CPU_CACHE_VIPT=y
+CONFIG_CPU_COPY_V6=y
+CONFIG_CPU_CP15=y
+CONFIG_CPU_CP15_MMU=y
+CONFIG_CPU_FREQ=y
+# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
+CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
+# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
+# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
+# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
+CONFIG_CPU_FREQ_GOV_COMMON=y
+# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
+CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
+# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
+# CONFIG_CPU_FREQ_GOV_USERSPACE is not set
+CONFIG_CPU_FREQ_STAT=y
+# CONFIG_CPU_FREQ_STAT_DETAILS is not set
+CONFIG_CPU_HAS_ASID=y
+# CONFIG_CPU_ICACHE_DISABLE is not set
+CONFIG_CPU_IDLE=y
+CONFIG_CPU_IDLE_GOV_LADDER=y
+CONFIG_CPU_IDLE_GOV_MENU=y
+CONFIG_CPU_PABRT_V7=y
+CONFIG_CPU_PM=y
+CONFIG_CPU_RMAP=y
+CONFIG_CPU_TLB_V7=y
+CONFIG_CPU_V7=y
+CONFIG_CRC16=y
+CONFIG_CRYPTO_AEAD=m
+CONFIG_CRYPTO_AEAD2=m
+CONFIG_CRYPTO_CCM=m
+CONFIG_CRYPTO_CRC32C=y
+CONFIG_CRYPTO_CTR=m
+CONFIG_CRYPTO_GCM=m
+CONFIG_CRYPTO_GF128MUL=m
+CONFIG_CRYPTO_GHASH=m
+CONFIG_CRYPTO_HASH=y
+CONFIG_CRYPTO_HASH2=y
+CONFIG_CRYPTO_MANAGER=m
+CONFIG_CRYPTO_MANAGER2=y
+CONFIG_CRYPTO_NULL=m
+CONFIG_CRYPTO_RNG=m
+CONFIG_CRYPTO_RNG2=y
+CONFIG_CRYPTO_SEQIV=m
+CONFIG_CRYPTO_WORKQUEUE=y
+CONFIG_DCACHE_WORD_ACCESS=y
+CONFIG_DDR=y
+CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S"
+# CONFIG_DEBUG_UART_8250 is not set
+# CONFIG_DEBUG_USER is not set
+# 

[OpenWrt-Devel] how to build two sub target simultaneously under same target

[punith kumar]

Dear Openwrt-devel,

I want to know if it is possible to setup build environment to compile
two sub-target simultaneously which will use same toolchain options,
build environment and etc.
Simultaneously both sub-targets should be configurable as a prerequisite

Thanks in advance for any sort of suggestion and direction

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

[OpenWrt-Devel] [PATCH v2] lantiq: ARV7519RW22 fixes - fix flash register (only 1 flash) - power led is green - rename message leds to internet - add leds configuration - enable switch vlans

[Álvaro Fernández Rojas]

Signed-off-by: Álvaro Fernández Rojas 
Signed-off-by: José Vázquez Fernández 
---
 target/linux/lantiq/base-files/etc/uci-defaults/01_leds  |  5 +
 .../linux/lantiq/base-files/etc/uci-defaults/02_network  |  3 +++
 target/linux/lantiq/dts/ARV7519RW22.dts  | 16 
 3 files changed, 16 insertions(+), 8 deletions(-)

diff --git a/target/linux/lantiq/base-files/etc/uci-defaults/01_leds 
b/target/linux/lantiq/base-files/etc/uci-defaults/01_leds
index 7ef88ea..b9e5420 100644
--- a/target/linux/lantiq/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/lantiq/base-files/etc/uci-defaults/01_leds
@@ -51,6 +51,11 @@ P2812HNUF*)
ucidef_set_led_netdev "dsl" "dsl" "dsl" "nas0"
ucidef_set_led_netdev "internet_green" "internet_green" 
"internet_green" "pppoe-wan"
;;
+ARV7519RW22)
+   ucidef_set_led_default "power" "power" "power" "1"
+   ucidef_set_led_netdev "internet_green" "internet_green" 
"internet_green" "pppoe-wan"
+   ucidef_set_led_netdev "lan" "lan" "lan" "eth0.1"
+   ;;
 ARV8539PW22)
 ucidef_set_led_default "power" "power" "soc:green:power" "1"
 ucidef_set_led_default "power2" "power2" "soc:red:power" "0"
diff --git a/target/linux/lantiq/base-files/etc/uci-defaults/02_network 
b/target/linux/lantiq/base-files/etc/uci-defaults/02_network
index ff21e02..f2cc37d 100644
--- a/target/linux/lantiq/base-files/etc/uci-defaults/02_network
+++ b/target/linux/lantiq/base-files/etc/uci-defaults/02_network
@@ -162,6 +162,9 @@ TDW8970)
 ARV7519RW22)
lan_mac=$(mtd_get_mac_binary boardconfig 22)
wan_mac=$(macaddr_add "$lan_mac" 1)
+   ucidef_set_interface_lan "eth0.1"
+   ucidef_add_switch "switch0" "1" "1"
+   ucidef_add_switch_vlan "switch0" "1" "0 2 3 4 5 6t"
;;
 
 BTHOMEHUBV2B|BTHOMEHUBV3A)
diff --git a/target/linux/lantiq/dts/ARV7519RW22.dts 
b/target/linux/lantiq/dts/ARV7519RW22.dts
index 6823753..73d5487 100644
--- a/target/linux/lantiq/dts/ARV7519RW22.dts
+++ b/target/linux/lantiq/dts/ARV7519RW22.dts
@@ -18,7 +18,7 @@
nor-boot@0 {
compatible = "lantiq,nor";
bank-width = <2>;
-   reg = <0 0x0 0x200>, <1 0x200 
0x200>;
+   reg = <0 0x0 0x200>;
#address-cells = <1>;
#size-cells = <1>;
 
@@ -202,11 +202,11 @@
label = "lan";
gpios = < 2 1>;
};
-   message_red {
-   label = "message_red";
+   internet_red {
+   label = "internet_red";
gpios = < 10 1>;
};
-   power_red {
+   power_green {
label = "power";
gpios = < 14 1>;
default-state = "on";
@@ -215,12 +215,12 @@
label = "alarm";
gpios = < 15 1>;
};
-   message_orange {
-   label = "message_orange";
+   internet_orange {
+   label = "internet_orange";
gpios = < 19 1>;
};
-   message_green {
-   label = "message_green";
+   internet_green {
+   label = "internet_green";
gpios = < 28 1>;
};
voice_green {
-- 
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] procd: Allow override of default respawn parameters

[Helmut Schaa]

On Fri, Sep 18, 2015 at 11:52 AM, John Crispin  wrote:
>
>
> On 18/09/2015 11:40, Etienne Champetier wrote:
>> Hi,
>>
>> 2015-09-18 11:03 GMT+02:00 Helmut Schaa > >:
>>
>> Hi John,
>>
>> On Fri, Sep 18, 2015 at 10:18 AM, John Crispin > > wrote:
>> > Hi
>> >
>> > On 18/09/2015 09:59, Helmut Schaa wrote:
>> >> Allow to pass RESPAWN_THESHOLD_DEFAULT, DRESPAWN_TIMEOUT_DEFAULT
>> >> and RESPAWN_RETRY_DEFAULT as parameters to cmake to change the
>> >> default respawn behavior.
>> >>
>> >
>> > technically ok but why cant you tweak them in your packages initd 
>> script
>> > ? i am wondering what the use case is and if there are other possible
>> > solutions
>>
>> In our tree we've patched most (maybe even all) services to respawn
>> forever
>> (respawn_retry=-1). Including all OpenWrt provided services. Instead
>> of keeping
>> these local modifications to several packages it's easier to just
>> override procds
>> default behavior.
>>
>> I think there might be other people around running OpenWrt on
>> headless boxes
>> where the respawn retry should not be limited by default. However,
>> this is of course
>> not suitable for a default OpenWrt box.
>>
>> If there are good reasons not to include this in procd feel free to
>> drop this patch.
>> However, it causes zero runtime overhead and is quite simple.
>>
>> As a followup I'd add a config flag for procd "respawn_forver_mode"
>> or so that
>> just sets respawn_retry to -1.
>>
>> Helmut
>>
>> It would be great to be able to configure these settings at runtime (ie
>> in an uci file)
>>
>> Etienne
>>
>
> agreed, i think the best would be to add support for -1 == endless
> respawn and then change procd.sh to use current values as default but
> allow overriding them vom /etc/config/system or similar. would that
> solve your use case ?

Hmm, could work. However, changing the setting in /etc/config/system would
only affect all services started after the config file change. In our case we'd
just add it to the default /etc/config/system ...

Let me look into it next week.

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