date:20151015

[OpenWrt-Devel] [PATCH] package/devel/perf: fix build for kernel 4.1

2015-10-15 Thread Alexandru Ardelean

This fix contains 2 parts:
 - kernel 4.1: backport upstream patch "perf build: Do not fail on missing 
Build file"
 - add +liblzma dependency

Signed-off-by: Alexandru Ardelean 
---
 package/devel/perf/Makefile|  2 +-
 ...f-build-Do-not-fail-on-missing-Build-file.patch | 67 ++
 2 files changed, 68 insertions(+), 1 deletion(-)
 create mode 100644 
target/linux/generic/patches-4.1/222-perf-build-Do-not-fail-on-missing-Build-file.patch

diff --git a/package/devel/perf/Makefile b/package/devel/perf/Makefile
index b77e29a..5eba8f1 100644
--- a/package/devel/perf/Makefile
+++ b/package/devel/perf/Makefile
@@ -19,7 +19,7 @@ include $(INCLUDE_DIR)/package.mk
 define Package/perf
   SECTION:=devel
   CATEGORY:=Development
-  DEPENDS:= @USE_GLIBC +libelf1 +libdw +libpthread +librt +binutils
+  DEPENDS:= @USE_GLIBC +libelf1 +libdw +libpthread +librt +binutils +liblzma
   TITLE:=Linux performance monitoring tool
   VERSION:=$(LINUX_VERSION)-$(PKG_RELEASE)
   URL:=http://www.kernel.org
diff --git 
a/target/linux/generic/patches-4.1/222-perf-build-Do-not-fail-on-missing-Build-file.patch
 
b/target/linux/generic/patches-4.1/222-perf-build-Do-not-fail-on-missing-Build-file.patch
new file mode 100644
index 000..3fb2df6
--- /dev/null
+++ 
b/target/linux/generic/patches-4.1/222-perf-build-Do-not-fail-on-missing-Build-file.patch
@@ -0,0 +1,67 @@
+From d7a3d85e08477a979933a2bb3b525a8de99543c2 Mon Sep 17 00:00:00 2001
+From: Jiri Olsa 
+Date: Fri, 29 May 2015 17:42:58 +0200
+Subject: [PATCH] perf build: Do not fail on missing Build file
+
+Allow nesting into directories without Build file. Currently we force
+include of the Build file, which fails the build when the Build file is
+missing.
+
+We already support empty *-in.o' objects if there's nothing in the
+directory to be compiled, so we can just use it for missing Build file
+cases.
+
+Also adding this case under tests.
+
+Reported-by: Rabin Vincent 
+Signed-off-by: Jiri Olsa 
+Cc: David Ahern 
+Cc: Namhyung Kim 
+Cc: Paul Mackerras 
+Cc: Peter Zijlstra 
+Cc: Rabin Vincent 
+Link: 
http://lkml.kernel.org/r/1432914178-24086-1-git-send-email-jo...@kernel.org
+Signed-off-by: Arnaldo Carvalho de Melo 
+---
+ tools/build/Makefile.build | 2 +-
+ tools/build/tests/ex/Build | 1 +
+ tools/build/tests/ex/empty2/README | 2 ++
+ 3 files changed, 4 insertions(+), 1 deletion(-)
+ create mode 100644 tools/build/tests/ex/empty2/README
+
+diff --git a/tools/build/Makefile.build b/tools/build/Makefile.build
+index 10df572..69c35cf 100644
+--- a/tools/build/Makefile.build
 b/tools/build/Makefile.build
+@@ -37,7 +37,7 @@ subdir-obj-y :=
+ 
+ # Build definitions
+ build-file := $(dir)/Build
+-include $(build-file)
++-include $(build-file)
+ 
+ quiet_cmd_flex  = FLEX $@
+ quiet_cmd_bison = BISON$@
+diff --git a/tools/build/tests/ex/Build b/tools/build/tests/ex/Build
+index 0e6c3e6..70d8762 100644
+--- a/tools/build/tests/ex/Build
 b/tools/build/tests/ex/Build
+@@ -2,6 +2,7 @@ ex-y += ex.o
+ ex-y += a.o
+ ex-y += b.o
+ ex-y += empty/
++ex-y += empty2/
+ 
+ libex-y += c.o
+ libex-y += d.o
+diff --git a/tools/build/tests/ex/empty2/README 
b/tools/build/tests/ex/empty2/README
+new file mode 100644
+index 000..2107cc5
+--- /dev/null
 b/tools/build/tests/ex/empty2/README
+@@ -0,0 +1,2 @@
++This directory is left intentionally without Build file
++to test proper nesting into Build-less directories.
+-- 
+2.1.4
+
-- 
2.1.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Question about kernel build number

2015-10-15 Thread Hannu Nyman


Drasko DRASKOVIC wrote on Thu Oct 15 11:06:09 CEST 2015:
> I guess that 7bed08fa9c06eb8089e82c200340ec66 is a random hash to give 
UUID to each build


Wrong.
That hash is a checksum of all the kernel options used when compiling the 
kernel.

And that checksum is the usual reason for the dependency error.

See  https://dev.openwrt.org/changeset/29686  for detailed explanation.

Note: 'opkg install --force-depends' can be used to override the check, but 
the modules may then not be quite compatible.

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

[OpenWrt-Devel] [PATCH] target/ramips: NixCore X1 Board Support

2015-10-15 Thread Andrew Gaylo


from: Andrew Gaylo 

This submission is for support of the NixCore X1 board at
http://nixcores.com.  This board uses the RT5350 Ralink processor
already supported by a number of boards in the OpenWRT repository.

Signed-off-by: Andrew Gaylo 
---
diff -uprN 
openwrt_vanilla/target/linux/ramips/base-files/etc/board.d/02_network 
openwrt_submit/target/linux/ramips/base-files/etc/board.d/02_network
--- 
openwrt_vanilla/target/linux/ramips/base-files/etc/board.d/02_network	2015-10-13 
11:10:15.784957130 -0600
+++ 
openwrt_submit/target/linux/ramips/base-files/etc/board.d/02_network	2015-10-15 
08:35:48.341341581 -0600

@@ -217,7 +217,7 @@ ramips_setup_interfaces()
ucidef_add_switch_vlan "switch0" "1" "0t 1 2 3 4"
ucidef_add_switch_vlan "switch0" "2" "0t 5"
;;
-
+nixcorex1 |\
vocore)
ucidef_set_interface_lan "eth0.1"
ucidef_add_switch "switch0" "1" "1"
diff -uprN openwrt_vanilla/target/linux/ramips/base-files/lib/ramips.sh 
openwrt_submit/target/linux/ramips/base-files/lib/ramips.sh
--- 
openwrt_vanilla/target/linux/ramips/base-files/lib/ramips.sh	2015-10-13 
11:10:15.784957130 -0600
+++ 
openwrt_submit/target/linux/ramips/base-files/lib/ramips.sh	2015-10-15 
08:36:21.021340613 -0600

@@ -232,6 +232,9 @@ ramips_board_detect() {
*"Nexx WT3020")
name="wt3020"
;;
+*"NixcoreX1")
+   name="nixcorex1"
+   ;;
*"NW718")
name="nw718"
;;
diff -uprN 
openwrt_vanilla/target/linux/ramips/base-files/lib/upgrade/platform.sh 
openwrt_submit/target/linux/ramips/base-files/lib/upgrade/platform.sh
--- 
openwrt_vanilla/target/linux/ramips/base-files/lib/upgrade/platform.sh	2015-10-13 
11:10:15.784957130 -0600
+++ 
openwrt_submit/target/linux/ramips/base-files/lib/upgrade/platform.sh	2015-10-15 
08:37:00.029339459 -0600

@@ -72,6 +72,7 @@ platform_check_image() {
mr-102n | \
mzk-w300nh2 | \
nbg-419n | \
+nixcorex1 | \
nw718 | \
omni-emb | \
omni-emb-hpm | \
diff -uprN openwrt_vanilla/target/linux/ramips/image/Makefile 
openwrt_submit/target/linux/ramips/image/Makefile
--- openwrt_vanilla/target/linux/ramips/image/Makefile	2015-10-13 
11:10:15.788957130 -0600
+++ openwrt_submit/target/linux/ramips/image/Makefile	2015-10-15 
08:37:25.885338693 -0600

@@ -569,6 +569,8 @@ Image/Build/Profile/MZKW300NH2=$(call Bu

 Image/Build/Profile/NCS601W=$(call 
BuildFirmware/Default8M/$(1),$(1),ncs601W,NCS601W)


+Image/Build/Profile/NIXCORE-X1=$(call 
BuildFirmware/Default8M/$(1),$(1),nixcorex1,NIXCORE-X1)

+
 nw718_mtd_size=3801088
 Image/Build/Profile/NW718=$(call 
BuildFirmware/CustomFlashFactory/$(1),$(1),nw718m,NW718,$(nw718_mtd_size),ARA1B4NCRNW718;1,factory)


@@ -741,6 +743,7 @@ define Image/Build/Profile/Default
$(call Image/Build/Profile/MZKW300NH2,$(1))
$(call Image/Build/Profile/NBG-419N,$(1))
$(call Image/Build/Profile/NCS601W,$(1))
+   $(call Image/Build/Profile/NIXCORE-X1,$(1))
$(call Image/Build/Profile/NW718,$(1))
$(call Image/Build/Profile/OMNI-EMB,$(1))
$(call Image/Build/Profile/OMNI-PLUG,$(1))
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] target/ramips: NixCore X1 Board Support

2015-10-15 Thread John Crispin



On 15/10/2015 17:49, Andrew Gaylo wrote:
> from: Andrew Gaylo 
> 
> This submission is for support of the NixCore X1 board at
> http://nixcores.com.  This board uses the RT5350 Ralink processor
> already supported by a number of boards in the OpenWRT repository.
> 
> Signed-off-by: Andrew Gaylo 



i think the dts file is missing



> ---
> diff -uprN
> openwrt_vanilla/target/linux/ramips/base-files/etc/board.d/02_network
> openwrt_submit/target/linux/ramips/base-files/etc/board.d/02_network
> ---
> openwrt_vanilla/target/linux/ramips/base-files/etc/board.d/02_network   
> 2015-10-13 11:10:15.784957130 -0600
> +++
> openwrt_submit/target/linux/ramips/base-files/etc/board.d/02_network   
> 2015-10-15 08:35:48.341341581 -0600
> @@ -217,7 +217,7 @@ ramips_setup_interfaces()
>  ucidef_add_switch_vlan "switch0" "1" "0t 1 2 3 4"
>  ucidef_add_switch_vlan "switch0" "2" "0t 5"
>  ;;
> -
> +nixcorex1 |\
>  vocore)
>  ucidef_set_interface_lan "eth0.1"
>  ucidef_add_switch "switch0" "1" "1"
> diff -uprN openwrt_vanilla/target/linux/ramips/base-files/lib/ramips.sh
> openwrt_submit/target/linux/ramips/base-files/lib/ramips.sh
> --- openwrt_vanilla/target/linux/ramips/base-files/lib/ramips.sh   
> 2015-10-13 11:10:15.784957130 -0600
> +++ openwrt_submit/target/linux/ramips/base-files/lib/ramips.sh   
> 2015-10-15 08:36:21.021340613 -0600
> @@ -232,6 +232,9 @@ ramips_board_detect() {
>  *"Nexx WT3020")
>  name="wt3020"
>  ;;
> +*"NixcoreX1")
> +name="nixcorex1"
> +;;
>  *"NW718")
>  name="nw718"
>  ;;
> diff -uprN
> openwrt_vanilla/target/linux/ramips/base-files/lib/upgrade/platform.sh
> openwrt_submit/target/linux/ramips/base-files/lib/upgrade/platform.sh
> ---
> openwrt_vanilla/target/linux/ramips/base-files/lib/upgrade/platform.sh
> 2015-10-13
> 11:10:15.784957130 -0600
> +++
> openwrt_submit/target/linux/ramips/base-files/lib/upgrade/platform.sh   
> 2015-10-15 08:37:00.029339459 -0600
> @@ -72,6 +72,7 @@ platform_check_image() {
>  mr-102n | \
>  mzk-w300nh2 | \
>  nbg-419n | \
> +nixcorex1 | \
>  nw718 | \
>  omni-emb | \
>  omni-emb-hpm | \
> diff -uprN openwrt_vanilla/target/linux/ramips/image/Makefile
> openwrt_submit/target/linux/ramips/image/Makefile
> --- openwrt_vanilla/target/linux/ramips/image/Makefile2015-10-13
> 11:10:15.788957130 -0600
> +++ openwrt_submit/target/linux/ramips/image/Makefile2015-10-15
> 08:37:25.885338693 -0600
> @@ -569,6 +569,8 @@ Image/Build/Profile/MZKW300NH2=$(call Bu
> 
>  Image/Build/Profile/NCS601W=$(call
> BuildFirmware/Default8M/$(1),$(1),ncs601W,NCS601W)
> 
> +Image/Build/Profile/NIXCORE-X1=$(call
> BuildFirmware/Default8M/$(1),$(1),nixcorex1,NIXCORE-X1)
> +
>  nw718_mtd_size=3801088
>  Image/Build/Profile/NW718=$(call
> BuildFirmware/CustomFlashFactory/$(1),$(1),nw718m,NW718,$(nw718_mtd_size),ARA1B4NCRNW718;1,factory)
> 
> 
> @@ -741,6 +743,7 @@ define Image/Build/Profile/Default
>  $(call Image/Build/Profile/MZKW300NH2,$(1))
>  $(call Image/Build/Profile/NBG-419N,$(1))
>  $(call Image/Build/Profile/NCS601W,$(1))
> +$(call Image/Build/Profile/NIXCORE-X1,$(1))
>  $(call Image/Build/Profile/NW718,$(1))
>  $(call Image/Build/Profile/OMNI-EMB,$(1))
>  $(call Image/Build/Profile/OMNI-PLUG,$(1))
> ___
> 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] [PATCH] target/ramips: NixCore X1 Board Support

2015-10-15 Thread Andrew Gaylo

The DTS and the MK files were in an earlier patch.  My first submission 
to OpenWRT, still getting the hang of the process.


https://lists.openwrt.org/pipermail/openwrt-devel/2015-October/036563.html

Drew

On 2015-10-15 09:53, John Crispin wrote:

On 15/10/2015 17:49, Andrew Gaylo wrote:

from: Andrew Gaylo 

This submission is for support of the NixCore X1 board at
http://nixcores.com.  This board uses the RT5350 Ralink processor
already supported by a number of boards in the OpenWRT repository.

Signed-off-by: Andrew Gaylo 




i think the dts file is missing




---
diff -uprN

openwrt_vanilla/target/linux/ramips/base-files/etc/board.d/02_network
openwrt_submit/target/linux/ramips/base-files/etc/board.d/02_network
---

openwrt_vanilla/target/linux/ramips/base-files/etc/board.d/02_network
2015-10-13 11:10:15.784957130 -0600
+++
openwrt_submit/target/linux/ramips/base-files/etc/board.d/02_network
2015-10-15 08:35:48.341341581 -0600
@@ -217,7 +217,7 @@ ramips_setup_interfaces()
 ucidef_add_switch_vlan "switch0" "1" "0t 1 2 3 4"
 ucidef_add_switch_vlan "switch0" "2" "0t 5"
 ;;
-
+nixcorex1 |\
 vocore)
 ucidef_set_interface_lan "eth0.1"
 ucidef_add_switch "switch0" "1" "1"
diff -uprN 
openwrt_vanilla/target/linux/ramips/base-files/lib/ramips.sh

openwrt_submit/target/linux/ramips/base-files/lib/ramips.sh
--- openwrt_vanilla/target/linux/ramips/base-files/lib/ramips.sh
2015-10-13 11:10:15.784957130 -0600
+++ openwrt_submit/target/linux/ramips/base-files/lib/ramips.sh
2015-10-15 08:36:21.021340613 -0600
@@ -232,6 +232,9 @@ ramips_board_detect() {
 *"Nexx WT3020")
 name="wt3020"
 ;;
+*"NixcoreX1")
+name="nixcorex1"
+;;
 *"NW718")
 name="nw718"
 ;;
diff -uprN

openwrt_vanilla/target/linux/ramips/base-files/lib/upgrade/platform.sh

openwrt_submit/target/linux/ramips/base-files/lib/upgrade/platform.sh
---

openwrt_vanilla/target/linux/ramips/base-files/lib/upgrade/platform.sh 
  2015-10-13

11:10:15.784957130 -0600
+++

openwrt_submit/target/linux/ramips/base-files/lib/upgrade/platform.sh
2015-10-15 08:37:00.029339459 -0600
@@ -72,6 +72,7 @@ platform_check_image() {
 mr-102n | \
 mzk-w300nh2 | \
 nbg-419n | \
+nixcorex1 | \
 nw718 | \
 omni-emb | \
 omni-emb-hpm | \
diff -uprN openwrt_vanilla/target/linux/ramips/image/Makefile
openwrt_submit/target/linux/ramips/image/Makefile
--- openwrt_vanilla/target/linux/ramips/image/Makefile2015-10-13
11:10:15.788957130 -0600
+++ openwrt_submit/target/linux/ramips/image/Makefile2015-10-15
08:37:25.885338693 -0600
@@ -569,6 +569,8 @@ Image/Build/Profile/MZKW300NH2=$(call Bu

 Image/Build/Profile/NCS601W=$(call
BuildFirmware/Default8M/$(1),$(1),ncs601W,NCS601W)

+Image/Build/Profile/NIXCORE-X1=$(call
BuildFirmware/Default8M/$(1),$(1),nixcorex1,NIXCORE-X1)
+
 nw718_mtd_size=3801088
 Image/Build/Profile/NW718=$(call

BuildFirmware/CustomFlashFactory/$(1),$(1),nw718m,NW718,$(nw718_mtd_size),ARA1B4NCRNW718;1,factory)


@@ -741,6 +743,7 @@ define Image/Build/Profile/Default
 $(call Image/Build/Profile/MZKW300NH2,$(1))
 $(call Image/Build/Profile/NBG-419N,$(1))
 $(call Image/Build/Profile/NCS601W,$(1))
+$(call Image/Build/Profile/NIXCORE-X1,$(1))
 $(call Image/Build/Profile/NW718,$(1))
 $(call Image/Build/Profile/OMNI-EMB,$(1))
 $(call Image/Build/Profile/OMNI-PLUG,$(1))
___
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] [PATCH] target/ramips: NixCore X1 Board Support

2015-10-15 Thread John Crispin

Hi,

ok. can you send a single patch containing both of the patches you made
please.

John

On 15/10/2015 18:15, Andrew Gaylo wrote:
> The DTS and the MK files were in an earlier patch.  My first submission
> to OpenWRT, still getting the hang of the process.
> 
> https://lists.openwrt.org/pipermail/openwrt-devel/2015-October/036563.html
> 
> Drew
> 
> On 2015-10-15 09:53, John Crispin wrote:
>> On 15/10/2015 17:49, Andrew Gaylo wrote:
>>> from: Andrew Gaylo 
>>>
>>> This submission is for support of the NixCore X1 board at
>>> http://nixcores.com.  This board uses the RT5350 Ralink processor
>>> already supported by a number of boards in the OpenWRT repository.
>>>
>>> Signed-off-by: Andrew Gaylo 
>>
>>
>>
>> i think the dts file is missing
>>
>>
>>
>>> ---
>>> diff -uprN
>>>
>>> openwrt_vanilla/target/linux/ramips/base-files/etc/board.d/02_network
>>> openwrt_submit/target/linux/ramips/base-files/etc/board.d/02_network
>>> ---
>>>
>>> openwrt_vanilla/target/linux/ramips/base-files/etc/board.d/02_network
>>> 2015-10-13 11:10:15.784957130 -0600
>>> +++
>>> openwrt_submit/target/linux/ramips/base-files/etc/board.d/02_network
>>> 2015-10-15 08:35:48.341341581 -0600
>>> @@ -217,7 +217,7 @@ ramips_setup_interfaces()
>>>  ucidef_add_switch_vlan "switch0" "1" "0t 1 2 3 4"
>>>  ucidef_add_switch_vlan "switch0" "2" "0t 5"
>>>  ;;
>>> -
>>> +nixcorex1 |\
>>>  vocore)
>>>  ucidef_set_interface_lan "eth0.1"
>>>  ucidef_add_switch "switch0" "1" "1"
>>> diff -uprN openwrt_vanilla/target/linux/ramips/base-files/lib/ramips.sh
>>> openwrt_submit/target/linux/ramips/base-files/lib/ramips.sh
>>> --- openwrt_vanilla/target/linux/ramips/base-files/lib/ramips.sh
>>> 2015-10-13 11:10:15.784957130 -0600
>>> +++ openwrt_submit/target/linux/ramips/base-files/lib/ramips.sh
>>> 2015-10-15 08:36:21.021340613 -0600
>>> @@ -232,6 +232,9 @@ ramips_board_detect() {
>>>  *"Nexx WT3020")
>>>  name="wt3020"
>>>  ;;
>>> +*"NixcoreX1")
>>> +name="nixcorex1"
>>> +;;
>>>  *"NW718")
>>>  name="nw718"
>>>  ;;
>>> diff -uprN
>>>
>>> openwrt_vanilla/target/linux/ramips/base-files/lib/upgrade/platform.sh
>>>
>>> openwrt_submit/target/linux/ramips/base-files/lib/upgrade/platform.sh
>>> ---
>>>
>>> openwrt_vanilla/target/linux/ramips/base-files/lib/upgrade/platform.sh  
>>> 2015-10-13
>>> 11:10:15.784957130 -0600
>>> +++
>>>
>>> openwrt_submit/target/linux/ramips/base-files/lib/upgrade/platform.sh
>>> 2015-10-15 08:37:00.029339459 -0600
>>> @@ -72,6 +72,7 @@ platform_check_image() {
>>>  mr-102n | \
>>>  mzk-w300nh2 | \
>>>  nbg-419n | \
>>> +nixcorex1 | \
>>>  nw718 | \
>>>  omni-emb | \
>>>  omni-emb-hpm | \
>>> diff -uprN openwrt_vanilla/target/linux/ramips/image/Makefile
>>> openwrt_submit/target/linux/ramips/image/Makefile
>>> --- openwrt_vanilla/target/linux/ramips/image/Makefile2015-10-13
>>> 11:10:15.788957130 -0600
>>> +++ openwrt_submit/target/linux/ramips/image/Makefile2015-10-15
>>> 08:37:25.885338693 -0600
>>> @@ -569,6 +569,8 @@ Image/Build/Profile/MZKW300NH2=$(call Bu
>>>
>>>  Image/Build/Profile/NCS601W=$(call
>>> BuildFirmware/Default8M/$(1),$(1),ncs601W,NCS601W)
>>>
>>> +Image/Build/Profile/NIXCORE-X1=$(call
>>> BuildFirmware/Default8M/$(1),$(1),nixcorex1,NIXCORE-X1)
>>> +
>>>  nw718_mtd_size=3801088
>>>  Image/Build/Profile/NW718=$(call
>>>
>>> BuildFirmware/CustomFlashFactory/$(1),$(1),nw718m,NW718,$(nw718_mtd_size),ARA1B4NCRNW718;1,factory)
>>>
>>>
>>>
>>> @@ -741,6 +743,7 @@ define Image/Build/Profile/Default
>>>  $(call Image/Build/Profile/MZKW300NH2,$(1))
>>>  $(call Image/Build/Profile/NBG-419N,$(1))
>>>  $(call Image/Build/Profile/NCS601W,$(1))
>>> +$(call Image/Build/Profile/NIXCORE-X1,$(1))
>>>  $(call Image/Build/Profile/NW718,$(1))
>>>  $(call Image/Build/Profile/OMNI-EMB,$(1))
>>>  $(call Image/Build/Profile/OMNI-PLUG,$(1))
>>> ___
>>> openwrt-devel mailing list
>>> openwrt-devel@lists.openwrt.org
>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] How to config GPIO and read the GPIO value in OpenWRT

2015-10-15 Thread Afkar Rafique

Thanks for the reply.

I have change the script as below:

#!/bin/sh /etc/rc.common

START=19
start() {
echo in > /sys/class/gpio/gpio16/direction 2> /dev/null
echo 16 > /sys/class/gpio/export 2> /dev/null
if [ "$(cat /sys/class/gpio/gpio16/value)" == "1" ] ; then
echo "255" >
/sys/devices/platform/leds-gpio/leds/db120:green:status/brightness
else
echo "0" >
/sys/devices/platform/leds-gpio/leds/db120:green:status/brightness
fi
}

I need to monitor the LED on/off all the time during runtime.

During start of this script its working, but not getting how to make it
work run time.

Could you please explain how i can do it in gpio-button.

On Fri, Oct 16, 2015 at 3:38 AM, Hartmut Knaack  wrote:

> Afkar Rafique schrieb am 15.10.2015 um 04:07:
> > Thanks for the reply.
> >
> > i have Create /etc/init.d/buttons and written below script:
> >
> > #!/bin/sh /etc/rc.common
> > START=19
> > start() {
> > /bin/umount /etc/config 2>/dev/null
> > echo out > /sys/class/gpio/gpio16/direction 2> /dev/null
> > echo 16 > /sys/class/gpio/export 2> /dev/null
> > if [ "$(cat /sys/class/gpio/gpio16/value)" == "1" ] ; then
> > echo "255" >
> /sys/devices/platform/leds-gpio/leds/db120:green:status/brightness
> > else
> > echo "0" >
> /sys/devices/platform/leds-gpio/leds/db120:green:status/brightness
> > fi
> > }
> >
> > and restart .
> >
> > chmod +x /etc/init.d/buttons
> > /etc/init.d/buttons enable
> > /etc/init.d/buttons start
> >
> > Now i am able to read the GPIO 16 value 1/0 based on GPIO state, but as
> above script i have written to ON/OFF the Status LED based on GPIO value,
> Status LED is not getting OFF even if GPIO16 value is "0".
> >
> > Can anyone please help on this
> >
>
> Quite a mess you've got there. No idea why you need to umount /etc/config,
> but anyway: First thing in GPIO setup is exporting, then you set its
> direction.
> If you intend to read the GPIO status, then better use "in" as direction.
> Now, do you just want to do an action (LED on/off) just during start of
> this
> script, or all the time during runtime, when the GPIO status changes? In
> the
> latter case, you should look into gpio-button.
>
> >
> >
> > On Thu, Oct 15, 2015 at 12:37 AM, Martin Blumenstingl <
> martin.blumensti...@googlemail.com  martin.blumensti...@googlemail.com>> wrote:
> >
> > On Wed, Oct 14, 2015 at 12:19 PM, Afkar Rafique  > wrote:
> > > Could anyone please explain how i can configure and read GPIO
> value.
> > There's an article on the wiki which explains how to set a GPIO to a
> > specific value: [0]
> > If you want to read a GPIO value then you use direction "in" and then
> > simply cat to read the "value".
> >
> > The only thing that you might have to do is doing a bit of maths to
> > get the correct GPIO number.
> > When you are trying to read GPIO #16 then it's GPIO #16 of a specific
> > chip -> /sys/class/gpio/ should contain a file gpiochipNNN.
> > What you do is take NNN (let's assume it's 456) and add your GPIO
> > number to it: 456 + 16 = 472 -> this is the number needef to "export"
> > the GPIO.
> >
> >
> > [0] http://wiki.openwrt.org/doc/hardware/port.gpio#software
> >
> >
> >
> >
> > ___
> > 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] Broken SPI transfers on TD-W8970 (latest trunk)

2015-10-15 Thread Martin Blumenstingl

Hi John,

On Thu, Oct 15, 2015 at 7:59 AM, John Crispin  wrote:
> bummer. i had hoped that my patch fixed the issue.
>
> did you try the patch graham posted ?
I split the patch into two and tried:
1) flushing in ltq_spi_wait_ready
2) reducing rxreq_max in ltq_spi_rxreq_set
3) both of the changes from above together

The results:
1) Most of the time the kernel does not boot at all, yielding the
following errors (sometimes it does go further though, but that seems
random):
[2.183972] spi-xway 1e100800.spi: error c4002203
[2.187270] spi_master spi32766: failed to transfer one message from queue
[2.194145] blk_update_request: I/O error, dev mtdblock2, sector 1490
[2.200713] SQUASHFS error: squashfs_read_data failed to read block 0xb877e
[2.207549] SQUASHFS error: Unable to read fragment cache entry [b877e]
[2.214141] SQUASHFS error: Unable to read page, block b877e, size 14eb8
[2.220894] SQUASHFS error: Unable to read fragment cache entry [b877e]
...
Error loading shared library libgcc_s.so.1: I/O error (needed by /etc/preinit)

2) device does not boot in this case, it hangs with:
[2.044041] spi-xway 1e100800.spi: SPI wait ready timed out stat: c4002003
[2.049657] m25p80 spi32766.3: wait failed

3) Still yields read errors (sometimes all files in /etc/config are
empty in that case):
[   11.528674] spi-xway 1e100800.spi: error a40b2203
[   11.532011] spi_master spi32766: failed to transfer one message from queue
[   11.538845] jffs2: error: (304) check_node_data: short read at
0x009ad0: 0 instead of 202.
[   11.547097] jffs2: error: (304) check_tn_node: check_node_data()
returned error: -5.
[   11.696937] procd: - ubus -
[   12.124641] spi-xway 1e100800.spi: error 940c2203
[   12.127979] spi_master spi32766: failed to transfer one message from queue
[   12.134805] jffs2: error: (304) check_node_data: short read at
0x0068a8: 0 instead of 89.
[   12.142981] jffs2: error: (304) check_tn_node: check_node_data()
returned error: -5.
[   12.150828] jffs2: warning: (304) jffs2_do_read_inode_internal:
Truncating ino #39 to 103 bytes failed because it only had 0 bytes to
start with!
[   12.264631] spi-xway 1e100800.spi: error 94052203
[   12.267911] spi_master spi32766: failed to transfer one message from queue
[   12.274798] jffs2: error: (304) check_node_data: short read at
0x006dc8: 0 instead of 89.
[   12.282971] jffs2: error: (304) check_tn_node: check_node_data()
returned error: -5.
[   12.290844] jffs2: warning: (304) jffs2_do_read_inode_internal:
Truncating ino #42 to 92 bytes failed because it only had 0 bytes to
start with!
[   12.508613] spi-xway 1e100800.spi: error 94052203

So it seems that flushing in ltq_spi_wait_ready helps a bit, but then
we get LTQ_SPI_STAT_RE ("receive errors") from the HW.
Let me know if you need more details.

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

[OpenWrt-Devel] Enforce RSA-Key-Transport on openssl

2015-10-15 Thread xxiao8

Due to fips requirement our https server must only do 
"RSA-Key-Transport"(no DSA,etc), is there a way to limit/enforce that on 
FIPS-compatible-Openssl? yes the https server uses openssl as its ssl 
library.


I'm checking openssl-1.0.2d/ssl/t1_trce.c and trying to find out if I 
should hack the code or do it via compiler-options, so far I failed to 
find the right places.


Or will the fips-openssl-module will enforce RSA-Key-Transport?

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

[OpenWrt-Devel] [PATCH] ramips: NixCore X1 Board Support unified patch

2015-10-15 Thread Andrew Gaylo


from: Andrew Gaylo 

Submission for support of the NixCore X1 board (http://nixcores.com.)
This board uses the RT5350 Ralink processor already supported by a
number of board in the OpenWRT repository. This is a unified patch from
two earlier patches

Signed-off-by: Andrew Gaylo 
---
diff -uprN openwrt_vanilla/target/linux/ramips/dts/NIXCORE-X1.dts 
openwrt_submit/target/linux/ramips/dts/NIXCORE-X1.dts
--- openwrt_vanilla/target/linux/ramips/dts/NIXCORE-X1.dts	1969-12-31 
17:00:00.0 -0700
+++ openwrt_submit/target/linux/ramips/dts/NIXCORE-X1.dts	2015-10-13 
11:04:19.636954204 -0600

@@ -0,0 +1,186 @@
+/dts-v1/;
+
+/include/ "rt5350.dtsi"
+
+/ {
+   compatible = "NixcoreX1", "ralink,rt5350-soc";
+   model = "NixcoreX1";
+
+   palmbus@1000 {
+/* Re-enable the gpio1 ports */
+   gpio1: gpio@660 {
+   status = "okay";
+   };
+
+   i2c@900 {
+   status = "okay";
+   };
+   uart@500 {
+   status = "okay";
+/* Mix of uart and gpio */
+reset-names = "gpio uartf";
+   };
+   spi@b00 {
+   status = "okay";
+
+   m25p80@0 {
+   #address-cells = <1>;
+   #size-cells = <1>;
+   compatible = "s25fl064k";
+   reg = <0>;
+   linux,modalias = "m25p80", "s25fl064k";
+   spi-max-frequency = <1000>;
+
+   partition@0 {
+   label = "uboot";
+   reg = <0x0 0x3>;
+   read-only;
+   };
+
+   partition@3 {
+   label = "uboot-env";
+   reg = <0x3 0x1>;
+   read-only;
+   };
+
+   factory: partition@4 {
+   label = "factory";
+   reg = <0x4 0x1>;
+   read-only;
+   };
+
+   partition@5 {
+   label = "firmware";
+   reg = <0x5 0x7b>;
+   };
+   };
+
+   spidev@1 {
+   compatible = "linux,spidev";
+   spi-max-frequency = <1000>;
+   reg = <1>;
+   };
+   };
+   };
+
+   pinctrl {
+   state_default: pinctrl0 {
+   gpio {
+/* Associate the tjag, uartf and led groups with gpio 
*/

+   ralink,group = "jtag", "led", "spi_cs1";
+/* How do we set individual pins? */
+   ralink,function = "gpio";
+   };
+   };
+   };
+
+   ethernet@1010 {
+   mtd-mac-address = < 0x4>;
+   };
+
+   esw@1011 {
+   ralink,portmap = <0x17>;
+   };
+
+   wmac@1018 {
+   ralink,mtd-eeprom = < 0>;
+   };
+
+   ehci@101c {
+   status = "okay";
+   };
+
+   ohci@101c1000 {
+   status = "okay";
+   };
+
+chosen {
+   bootargs = "console=ttyS1,57600";
+   };
+   gpio-export {
+   compatible = "gpio-export";
+   #size-cells = <0>;
+
+   gpio0 {
+   gpio-export,name = "gpio0";
+   gpio-export,direction_may_change = <1>;
+   gpios = < 0 0>;
+   };
+
+/* GPIOs 1-6 are I2C,SPI */
+
+/* GPIO 7-14 are uart1 */
+
+/* GPIOs 15 & 16 are uart2 */
+
+   /* JTAG */
+   gpio17 {
+   /* JTAG_TDO */
+   gpio-export,name = "gpio17";
+   gpio-export,direction_may_change = <1>;
+   gpios = < 17 0>;
+   };
+   gpio18 {
+   /* JTAG_TDI */
+   gpio-export,name = "gpio18";
+   gpio-export,direction_may_change = <1>;
+   gpios = < 18 0>;
+   };
+   gpio19 {
+   /* JTAG_TMS */
+   gpio-export,name = "gpio19";
+   gpio-export,direction_may_change = <1>;
+   gpios = < 19 0>;
+   };
+

Re: [OpenWrt-Devel] How to config GPIO and read the GPIO value in OpenWRT

2015-10-15 Thread Hartmut Knaack

Afkar Rafique schrieb am 15.10.2015 um 04:07:
> Thanks for the reply.
> 
> i have Create /etc/init.d/buttons and written below script:
> 
> #!/bin/sh /etc/rc.common
> START=19
> start() {
> /bin/umount /etc/config 2>/dev/null
> echo out > /sys/class/gpio/gpio16/direction 2> /dev/null   
> echo 16 > /sys/class/gpio/export 2> /dev/null
> if [ "$(cat /sys/class/gpio/gpio16/value)" == "1" ] ; then
> echo "255" > 
> /sys/devices/platform/leds-gpio/leds/db120:green:status/brightness 
> else
> echo "0" > 
> /sys/devices/platform/leds-gpio/leds/db120:green:status/brightness 
> fi
> }
> 
> and restart .
> 
> chmod +x /etc/init.d/buttons
> /etc/init.d/buttons enable
> /etc/init.d/buttons start
> 
> Now i am able to read the GPIO 16 value 1/0 based on GPIO state, but as above 
> script i have written to ON/OFF the Status LED based on GPIO value, Status 
> LED is not getting OFF even if GPIO16 value is "0".
> 
> Can anyone please help on this
> 

Quite a mess you've got there. No idea why you need to umount /etc/config,
but anyway: First thing in GPIO setup is exporting, then you set its direction.
If you intend to read the GPIO status, then better use "in" as direction.
Now, do you just want to do an action (LED on/off) just during start of this
script, or all the time during runtime, when the GPIO status changes? In the
latter case, you should look into gpio-button.

> 
> 
> On Thu, Oct 15, 2015 at 12:37 AM, Martin Blumenstingl 
>  > wrote:
> 
> On Wed, Oct 14, 2015 at 12:19 PM, Afkar Rafique  > wrote:
> > Could anyone please explain how i can configure and read GPIO value.
> There's an article on the wiki which explains how to set a GPIO to a
> specific value: [0]
> If you want to read a GPIO value then you use direction "in" and then
> simply cat to read the "value".
> 
> The only thing that you might have to do is doing a bit of maths to
> get the correct GPIO number.
> When you are trying to read GPIO #16 then it's GPIO #16 of a specific
> chip -> /sys/class/gpio/ should contain a file gpiochipNNN.
> What you do is take NNN (let's assume it's 456) and add your GPIO
> number to it: 456 + 16 = 472 -> this is the number needef to "export"
> the GPIO.
> 
> 
> [0] http://wiki.openwrt.org/doc/hardware/port.gpio#software
> 
> 
> 
> 
> ___
> 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] Broken SPI transfers on TD-W8970 (latest trunk)

2015-10-15 Thread John Crispin

bummer. i had hoped that my patch fixed the issue.

did you try the patch graham posted ?

John

On 14/10/2015 20:38, Martin Blumenstingl wrote:
> Hi John,
> 
> I am getting SPI errors on latest trunk.
> It seems that those might be related to your SPI changes from last week.
> 
> I found that someone else reported a similar issue a few years ago: [0].
> That patch was never applied and I'm not sure if it's 100% correct.
> 
> These are the errors I get without the rxreq_max correction
> (hw->rxfs -1) applied - the device is barely usable in this case:
> [  106.211973] spi-xway 1e100800.spi: SPI wait ready timed out stat: 44002003
> [  106.217446] m25p80 spi32766.3: wait failed
> [  106.419959] spi-xway 1e100800.spi: SPI wait ready timed out stat: 44002003
> [  106.623973] spi-xway 1e100800.spi: SPI wait ready timed out stat: c4002003
> [  106.629442] m25p80 spi32766.3: wait failed
> [  106.831959] spi-xway 1e100800.spi: SPI wait ready timed out stat: c4002003
> [  107.035969] spi-xway 1e100800.spi: SPI wait ready timed out stat: c4002003
> [  107.041432] m25p80 spi32766.3: wait failed
> [  107.243966] spi-xway 1e100800.spi: SPI wait ready timed out stat: c4002003
> [  107.447973] spi-xway 1e100800.spi: SPI wait ready timed out stat: c4002003
> 
> However, with the rxreq_max correction applied it works better, but I
> get read errors sometimes:
> [   18.798861] spi-xway 1e100800.spi: error 441e2203
> [   18.802207] spi_master spi32766: failed to transfer one message from queue
> [   18.810784] spi-xway 1e100800.spi: error 44162203
> [   18.814123] spi_master spi32766: failed to transfer one message from queue
> or:
> # passwd
> [  123.844172] spi-xway 1e100800.spi: error b4092203
> [  123.847459] spi_master spi32766: failed to transfer one message from queue
> passwd: no record of root in /etc/shadow, using /etc/passwd: I/O error
> 
> I've attached two patches where the second one should help debugging
> this (or further) issues, and the other one might actually fix an actual
> on some devices.
> 
> Are you able to reproduce these issues on your TD-W89x0 as well?
> 
> Regards,
> Martin
> 
> 
> [0] https://lists.openwrt.org/pipermail/openwrt-devel/2012-April/014794.html
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH][ar71xx] Mikrotik Routerboard RB2011 switch fix

2015-10-15 Thread George Chriss

On Thu, April 23, 2015 06:16:08 CEST, Toerless Eckert wrote:
> This mail thread seem to have gone dark since december with seemingly
> no conclusion.
>
> I have tried to collect the experiences reported on the wiki page:
>
> wiki.openwrt.org/toh/mikrotik/rb2011uias
>
> As you can see from the table, for me it only works with 0x6f.
> Chris, for whom both 0x3e and 0x6f work has a rev 2 AR9344. I have
> a rev 3. AR8327 is rev. 4 on both our routerboards. No info what rev Matt
> has, he is the other one reporting that only 0x6f works.
>
> I am also observing some amount of increases in switch 0 port 0
> RxBadByte (aka: from CPU to AR8327). It seems to happen for
> all type of traffic sent from CPU to switch, eg: whether i inject it from
> WiFi or from a 100 Mbps port, and whether i send it out
> on an untagged port (lan) or tagged one (from CPU, Wan).

I'm under the impression that some of the "OK/Not OK" reports are based on
ping packet loss which provides limited insight into actual throughput.  My
results with a RB2011UiAS-IN (no WiFi, empty SFP cage, AR9344 Rev. 2, CPU @
600MHz powered from the DC-in jack) on patched 15.05:

0x0600 (Unpatched)
No TCP/IP 2-way connection [Not OK]

==

0x3e00
(MikroTik Eth1 -> laptop, crossover cable)
/bin/bash -c "dd if=/dev/zero bs=1M count=1000 | netcat 192.168.1.101 "
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 1589.44 s, 660 kB/s  [Not OK]

(laptop -> MikroTik Eth1, crossover cable)
dd if=/dev/zero bs=1M count=1000 | nc 192.168.1.121 
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 49.6707 s, 21.1 MB/s  [OK]

==

0x6f00
(MikroTik Eth1 -> laptop, crossover cable)
/bin/bash -c "dd if=/dev/zero bs=1M count=1000 | netcat 192.168.
1.101 "
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 176.224 s, 6.0 MB/s  [OK?]

(laptop -> MikroTik Eth1, crossover cable)
dd if=/dev/zero bs=1M count=1000 | nc 192.168.1.121 
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 50.7454 s, 20.7 MB/s  [OK]


Any word on the bootloader patch?  Happy to test more values as needed.

Sincerely,
George


> I have not really identified any noticeable performance impact from
> this effect through.
>
> Would be nice to hear some logic why 0x6f is the right value.
>
>> From the discussion it looks a bit like trial and error.
>>
>
> Cheers
> Toerless
>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH][ar71xx] Mikrotik Routerboard RB2011 switch fix

2015-10-15 Thread Fernando Frediani

Out of curiosity. Dp these builds of OpenWrt for Mikrotik RBs make usage 
of any possible hardware off-loads or config customizations are CPU 
affinity possibility made by Mikrotik themselves in their original 
RouterOS ?


Thanks
Fernando

On 15/10/2015 14:48, George Chriss wrote:


On Thu, April 23, 2015 06:16:08 CEST, Toerless Eckert wrote:
> This mail thread seem to have gone dark since december with seemingly
> no conclusion.
>
> I have tried to collect the experiences reported on the wiki page:
>
> wiki.openwrt.org/toh/mikrotik/rb2011uias 


>
> As you can see from the table, for me it only works with 0x6f.
> Chris, for whom both 0x3e and 0x6f work has a rev 2 AR9344. I have
> a rev 3. AR8327 is rev. 4 on both our routerboards. No info what rev 
Matt

> has, he is the other one reporting that only 0x6f works.
>
> I am also observing some amount of increases in switch 0 port 0
> RxBadByte (aka: from CPU to AR8327). It seems to happen for
> all type of traffic sent from CPU to switch, eg: whether i inject it 
from

> WiFi or from a 100 Mbps port, and whether i send it out
> on an untagged port (lan) or tagged one (from CPU, Wan).

I'm under the impression that some of the "OK/Not OK" reports are 
based on ping packet loss which provides limited insight into actual 
throughput.  My results with a RB2011UiAS-IN (no WiFi, empty SFP cage, 
AR9344 Rev. 2, CPU @ 600MHz powered from the DC-in jack) on patched 15.05:


0x0600 (Unpatched)
No TCP/IP 2-way connection [Not OK]

==

0x3e00
(MikroTik Eth1 -> laptop, crossover cable)
/bin/bash -c "dd if=/dev/zero bs=1M count=1000 | netcat 192.168.1.101 
"

1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 1589.44 s, 660 kB/s  [Not OK]

(laptop -> MikroTik Eth1, crossover cable)
dd if=/dev/zero bs=1M count=1000 | nc 192.168.1.121 
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 49.6707 s, 21.1 MB/s  [OK]

==

0x6f00
(MikroTik Eth1 -> laptop, crossover cable)
/bin/bash -c "dd if=/dev/zero bs=1M count=1000 | netcat 192.168.
1.101 "
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 176.224 s, 6.0 MB/s  [OK?]

(laptop -> MikroTik Eth1, crossover cable)
dd if=/dev/zero bs=1M count=1000 | nc 192.168.1.121 
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 50.7454 s, 20.7 MB/s  [OK]


Any word on the bootloader patch?  Happy to test more values as needed.

Sincerely,
George


> I have not really identified any noticeable performance impact from
> this effect through.
>
> Would be nice to hear some logic why 0x6f is the right value.
>
>> From the discussion it looks a bit like trial and error.
>>
>
> Cheers
> Toerless
>
>




___
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] [PATCH][ar71xx] Mikrotik Routerboard RB2011 switch fix

2015-10-15 Thread Fernando Frediani


Hello George.
No, unfortunatelly it doesn't. I was trying to get a more objective 
reply from perhaps whoever built and maintains this router profile in 
order to understand and compare when using original firmware and OpenWrt 
customized to it. All around the performance X feature list.

As the wiki doesn't mention that I asked it here.

Thanks
Fernando

On 15/10/2015 15:17, George Chriss wrote:
On Thu, Oct 15, 2015 at 2:00 PM, Fernando Frediani 
> wrote:

>
> Out of curiosity. Dp these builds of OpenWrt for Mikrotik RBs make 
usage of any possible hardware off-loads or config customizations are 
CPU affinity possibility made by Mikrotik themselves in their original 
RouterOS ?


Does this help to answer your question?
http://www.mikrotik.com/download/share/gpl_source.zip 



-George


> Thanks
> Fernando
>
>
> On 15/10/2015 14:48, George Chriss wrote:
>
>
> On Thu, April 23, 2015 06:16:08 CEST, Toerless Eckert wrote:
> > This mail thread seem to have gone dark since december with seemingly
> > no conclusion.
> >
> > I have tried to collect the experiences reported on the wiki page:
> >
> > wiki.openwrt.org/toh/mikrotik/rb2011uias 


> >
> > As you can see from the table, for me it only works with 0x6f.
> > Chris, for whom both 0x3e and 0x6f work has a rev 2 AR9344. I have
> > a rev 3. AR8327 is rev. 4 on both our routerboards. No info what 
rev Matt

> > has, he is the other one reporting that only 0x6f works.
> >
> > I am also observing some amount of increases in switch 0 port 0
> > RxBadByte (aka: from CPU to AR8327). It seems to happen for
> > all type of traffic sent from CPU to switch, eg: whether i inject 
it from

> > WiFi or from a 100 Mbps port, and whether i send it out
> > on an untagged port (lan) or tagged one (from CPU, Wan).
>
> I'm under the impression that some of the "OK/Not OK" reports are 
based on ping packet loss which provides limited insight into actual 
throughput.  My results with a RB2011UiAS-IN (no WiFi, empty SFP cage, 
AR9344 Rev. 2, CPU @ 600MHz powered from the DC-in jack) on patched 15.05:

>
> 0x0600 (Unpatched)
> No TCP/IP 2-way connection [Not OK]
>
> ==
>
> 0x3e00
> (MikroTik Eth1 -> laptop, crossover cable)
> /bin/bash -c "dd if=/dev/zero bs=1M count=1000 | netcat 
192.168.1.101 "

> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes (1.0 GB) copied, 1589.44 s, 660 kB/s  [Not OK]
>
> (laptop -> MikroTik Eth1, crossover cable)
> dd if=/dev/zero bs=1M count=1000 | nc 192.168.1.121 
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes (1.0 GB) copied, 49.6707 s, 21.1 MB/s  [OK]
>
> ==
>
> 0x6f00
> (MikroTik Eth1 -> laptop, crossover cable)
> /bin/bash -c "dd if=/dev/zero bs=1M count=1000 | netcat 192.168.
> 1.101 "
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes (1.0 GB) copied, 176.224 s, 6.0 MB/s  [OK?]
>
> (laptop -> MikroTik Eth1, crossover cable)
> dd if=/dev/zero bs=1M count=1000 | nc 192.168.1.121 
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes (1.0 GB) copied, 50.7454 s, 20.7 MB/s  [OK]
>
>
> Any word on the bootloader patch?  Happy to test more values as needed.
>
> Sincerely,
> George
>
>
> > I have not really identified any noticeable performance impact from
> > this effect through.
> >
> > Would be nice to hear some logic why 0x6f is the right value.
> >
> >> From the discussion it looks a bit like trial and error.
> >>
> >
> > Cheers
> > Toerless
> >
> >
>
>
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org 
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org 
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>


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

Re: [OpenWrt-Devel] [PATCH][ar71xx] Mikrotik Routerboard RB2011 switch fix

2015-10-15 Thread George Chriss

On Thu, Oct 15, 2015 at 2:00 PM, Fernando Frediani 
wrote:
>
> Out of curiosity. Dp these builds of OpenWrt for Mikrotik RBs make usage
of any possible hardware off-loads or config customizations are CPU
affinity possibility made by Mikrotik themselves in their original RouterOS
?

Does this help to answer your question?
http://www.mikrotik.com/download/share/gpl_source.zip

-George


> Thanks
> Fernando
>
>
> On 15/10/2015 14:48, George Chriss wrote:
>
>
> On Thu, April 23, 2015 06:16:08 CEST, Toerless Eckert wrote:
> > This mail thread seem to have gone dark since december with seemingly
> > no conclusion.
> >
> > I have tried to collect the experiences reported on the wiki page:
> >
> > wiki.openwrt.org/toh/mikrotik/rb2011uias
> >
> > As you can see from the table, for me it only works with 0x6f.
> > Chris, for whom both 0x3e and 0x6f work has a rev 2 AR9344. I have
> > a rev 3. AR8327 is rev. 4 on both our routerboards. No info what rev
Matt
> > has, he is the other one reporting that only 0x6f works.
> >
> > I am also observing some amount of increases in switch 0 port 0
> > RxBadByte (aka: from CPU to AR8327). It seems to happen for
> > all type of traffic sent from CPU to switch, eg: whether i inject it
from
> > WiFi or from a 100 Mbps port, and whether i send it out
> > on an untagged port (lan) or tagged one (from CPU, Wan).
>
> I'm under the impression that some of the "OK/Not OK" reports are based
on ping packet loss which provides limited insight into actual throughput.
My results with a RB2011UiAS-IN (no WiFi, empty SFP cage, AR9344 Rev. 2,
CPU @ 600MHz powered from the DC-in jack) on patched 15.05:
>
> 0x0600 (Unpatched)
> No TCP/IP 2-way connection [Not OK]
>
> ==
>
> 0x3e00
> (MikroTik Eth1 -> laptop, crossover cable)
> /bin/bash -c "dd if=/dev/zero bs=1M count=1000 | netcat 192.168.1.101
"
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes (1.0 GB) copied, 1589.44 s, 660 kB/s  [Not OK]
>
> (laptop -> MikroTik Eth1, crossover cable)
> dd if=/dev/zero bs=1M count=1000 | nc 192.168.1.121 
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes (1.0 GB) copied, 49.6707 s, 21.1 MB/s  [OK]
>
> ==
>
> 0x6f00
> (MikroTik Eth1 -> laptop, crossover cable)
> /bin/bash -c "dd if=/dev/zero bs=1M count=1000 | netcat 192.168.
> 1.101 "
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes (1.0 GB) copied, 176.224 s, 6.0 MB/s  [OK?]
>
> (laptop -> MikroTik Eth1, crossover cable)
> dd if=/dev/zero bs=1M count=1000 | nc 192.168.1.121 
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes (1.0 GB) copied, 50.7454 s, 20.7 MB/s  [OK]
>
>
> Any word on the bootloader patch?  Happy to test more values as needed.
>
> Sincerely,
> George
>
>
> > I have not really identified any noticeable performance impact from
> > this effect through.
> >
> > Would be nice to hear some logic why 0x6f is the right value.
> >
> >> From the discussion it looks a bit like trial and error.
> >>
> >
> > Cheers
> > Toerless
> >
> >
>
>
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] package/devel/perf: fix build for kernel 4.1

Re: [OpenWrt-Devel] Question about kernel build number

[OpenWrt-Devel] [PATCH] target/ramips: NixCore X1 Board Support

Re: [OpenWrt-Devel] [PATCH] target/ramips: NixCore X1 Board Support

Re: [OpenWrt-Devel] [PATCH] target/ramips: NixCore X1 Board Support

Re: [OpenWrt-Devel] [PATCH] target/ramips: NixCore X1 Board Support

Re: [OpenWrt-Devel] How to config GPIO and read the GPIO value in OpenWRT

Re: [OpenWrt-Devel] Broken SPI transfers on TD-W8970 (latest trunk)

[OpenWrt-Devel] Enforce RSA-Key-Transport on openssl

[OpenWrt-Devel] [PATCH] ramips: NixCore X1 Board Support unified patch

Re: [OpenWrt-Devel] How to config GPIO and read the GPIO value in OpenWRT

Re: [OpenWrt-Devel] Broken SPI transfers on TD-W8970 (latest trunk)

[OpenWrt-Devel] [PATCH][ar71xx] Mikrotik Routerboard RB2011 switch fix

Re: [OpenWrt-Devel] [PATCH][ar71xx] Mikrotik Routerboard RB2011 switch fix

Re: [OpenWrt-Devel] [PATCH][ar71xx] Mikrotik Routerboard RB2011 switch fix

Re: [OpenWrt-Devel] [PATCH][ar71xx] Mikrotik Routerboard RB2011 switch fix

16 matches

Site Navigation

Mail list logo

Footer information