date:20170106

Re: [LEDE-DEV] [PATCH] lantiq: update USB controller handling

2017-01-06 Thread Antti Seppälä

On 6 January 2017 at 21:32, Hauke Mehrtens  wrote:
> On 01/06/2017 08:26 PM, Martin Blumenstingl wrote:
>> Hi Hauke,
>>
>> (CC'ing Mathias as he was looking into some of the USB issues as well)
>>
>> On Fri, Jan 6, 2017 at 8:06 PM, Hauke Mehrtens  wrote:
>>> This makes the code use the same settings aas the vendor sdrivers.
>> s/aas/as/
>> s/sdrivers/driver/
>> you should probably also mention that this:
>> 1. backports USB initialization fixes for XRX300, Danube and Amazon-SE
>> 2. sets the clock source for all SoCs which fixes USB (initialization)
>> issues on Danube when using the dwc2 driver (thus fixes FS#351 and
>> supersedes Mathias' "lantiq: set the usb clock source" RFC patch)
>
> Yes after I send the patch I noticed that I haven't updated the commit
> message. I will fix that.
>
> Could someone please test this patch and report back if it fixes the
> problems on Danube and works on Amazon SE or improves something in VR9?
> Positive and negative reports would be nice. I have only tested it on
> VR9 till now, I have to look what other boards I have here.
>

Hi Hauke.

The patch looks good except for the choices of fifo sizes from vendor
driver which from the point-of-view of usb packet sizes are quite odd
will break at least certain audio devices.

If I recall correctly the dwc2 specification (Method 1) proposes
values for fifo size at minimum of:

rx fifo size: 258 + number of host channels
non-periodic tx fifo size: 128
periodic tx fifo size: 768

The spec Method 2 which is used by the upstream driver autodetection
logic[1] doubles the rx and nptx sizes to try to fit two packets at
once for greater performance.

Especially the periodic fifo size choice of 32 for vr9 is way too
small to accommodate a complete usb packet.
We used to have the vendor driver values in use for vr9 but there were
some complaints on openwrt forum that usb audio devices did not work.

Changing the values to closer resemble the dwc2 specification actually
allows audio devices to work for some people [2].

Unfortunately the default total fifo size is 512 which can never
fulfil the dwc2 specification completely.
Is there a way to programmatically re-allocate a bigger fifo for the
lantiq platform during initialization? If there is we could let the
dwc2 driver autoconfigure the fifos as it sees fit.

Also the dwc2 driver apparently does a pretty good job at
autoconfiguring various other parameters for optimum performance so I
wonder whether we should rely on that instead of hard-coding them?

A disclaimer though: I'm not an usb expert. I only did the best I
could with the fifo values based on my testing and reading the dwc2
spec :)

1. 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/dwc2/core.c?h=v4.4#n892
2. https://forum.openwrt.org/viewtopic.php?pid=299862#p299862

-- 
Antti

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

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH oldpackage/eventlog oldpackage/syslog-ng3] version bump to latest

2017-01-06 Thread Stijn Tintel

On 06-01-17 20:38, Hauke Mehrtens wrote:
> Please do not send a mail with just an attachment, oldpackage is frozen
> since some years, please send add the package to the official openwrt
> package repository, add yourself as a maintainer and send a pull request
> on github.
There are PRs for this already, which I have merged just a few moments ago.

Stijn

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

Re: [LEDE-DEV] [PATCH oldpackage/eventlog oldpackage/syslog-ng3] version bump to latest

2017-01-06 Thread Hauke Mehrtens

Please do not send a mail with just an attachment, oldpackage is frozen
since some years, please send add the package to the official openwrt
package repository, add yourself as a maintainer and send a pull request
on github.

On 01/06/2017 08:19 PM, Philip Prindeville wrote:

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

Re: [LEDE-DEV] [PATCH] lantiq: update USB controller handling

2017-01-06 Thread Hauke Mehrtens

On 01/06/2017 08:26 PM, Martin Blumenstingl wrote:
> Hi Hauke,
> 
> (CC'ing Mathias as he was looking into some of the USB issues as well)
> 
> On Fri, Jan 6, 2017 at 8:06 PM, Hauke Mehrtens  wrote:
>> This makes the code use the same settings aas the vendor sdrivers.
> s/aas/as/
> s/sdrivers/driver/
> you should probably also mention that this:
> 1. backports USB initialization fixes for XRX300, Danube and Amazon-SE
> 2. sets the clock source for all SoCs which fixes USB (initialization)
> issues on Danube when using the dwc2 driver (thus fixes FS#351 and
> supersedes Mathias' "lantiq: set the usb clock source" RFC patch)

Yes after I send the patch I noticed that I haven't updated the commit
message. I will fix that.

Could someone please test this patch and report back if it fixes the
problems on Danube and works on Amazon SE or improves something in VR9?
Positive and negative reports would be nice. I have only tested it on
VR9 till now, I have to look what other boards I have here.

>> Signed-off-by: Hauke Mehrtens 
>> ---
>>  target/linux/lantiq/dts/amazonse.dtsi  |   3 +-
>>  target/linux/lantiq/dts/ar9.dtsi   |   6 +-
>>  target/linux/lantiq/dts/danube.dtsi|   2 +-
>>  target/linux/lantiq/dts/vr9.dtsi   |   6 +-
>>  ...MIPS-lantiq-danube-initialize-usb-on-boot.patch |  10 -
>>  .../patches-4.4/0041-USB-DWC2-add-ltq-params.patch |  75 
>>  .../linux/lantiq/patches-4.4/0047-poweroff.patch   |   2 +-
>>  ...2-Add-support-for-Lantiq-ARX-and-XRX-SoCs.patch |  78 
>>  ...ke-the-lantiq-settings-match-vendor-drive.patch |  53 ++
>>  .../patches-4.4/0062-USB-DWC2-add-ltq-params.patch |  47 +
>>  ...65-MIPS-lantiq-improve-USB-initialization.patch | 202 
>> +
>>  ...x200-add-gphy-clk-src-device-tree-binding.patch |   6 +-
>>  12 files changed, 395 insertions(+), 95 deletions(-)
>>  delete mode 100644 
>> target/linux/lantiq/patches-4.4/0039-MIPS-lantiq-danube-initialize-usb-on-boot.patch
>>  delete mode 100644 
>> target/linux/lantiq/patches-4.4/0041-USB-DWC2-add-ltq-params.patch
>>  create mode 100644 
>> target/linux/lantiq/patches-4.4/0060-usb-dwc2-Add-support-for-Lantiq-ARX-and-XRX-SoCs.patch
>>  create mode 100644 
>> target/linux/lantiq/patches-4.4/0061-USB-DWC2-make-the-lantiq-settings-match-vendor-drive.patch
>>  create mode 100644 
>> target/linux/lantiq/patches-4.4/0062-USB-DWC2-add-ltq-params.patch
>>  create mode 100644 
>> target/linux/lantiq/patches-4.4/0065-MIPS-lantiq-improve-USB-initialization.patch
>>
>> diff --git a/target/linux/lantiq/dts/amazonse.dtsi 
>> b/target/linux/lantiq/dts/amazonse.dtsi
>> index bce618fed8..2b8ad08140 100644
>> --- a/target/linux/lantiq/dts/amazonse.dtsi
>> +++ b/target/linux/lantiq/dts/amazonse.dtsi
>> @@ -122,11 +122,12 @@
>> };
>>
>> ifxhcd@E101000 {
>> -   compatible = "lantiq,ifxhcd-ase";
>> +   compatible = "lantiq,ase-usb", "lantiq,ifxhcd-ase";
>> reg = <0xE101000 0x1000
>> 0xE12 0x3f000>;
>> interrupt-parent = <>;
>> interrupts = <39>;
>> +   dr_mode = "host";
>> status = "disabled";
>> };
>>
>> diff --git a/target/linux/lantiq/dts/ar9.dtsi 
>> b/target/linux/lantiq/dts/ar9.dtsi
>> index 569f25f02c..2638a4b268 100644
>> --- a/target/linux/lantiq/dts/ar9.dtsi
>> +++ b/target/linux/lantiq/dts/ar9.dtsi
>> @@ -137,20 +137,22 @@
>> };
>>
>> ifxhcd@E101000 {
>> -   compatible = "lantiq,ifxhcd-arx100", 
>> "lantiq,ifxhcd-arx100-dwc2";
>> +   compatible = "lantiq,arx100-usb", 
>> "lantiq,ifxhcd-arx100";
>> reg = <0xE101000 0x1000
>> 0xE12 0x3f000>;
>> interrupt-parent = <>;
>> interrupts = <62 91>;
>> +   dr_mode = "host";
>> status = "disabled";
>> };
>>
>> ifxhcd@E106000 {
>> -   compatible = "lantiq,ifxhcd-arx100-dwc2";
>> +   compatible = "lantiq,arx100-usb";
>> reg = <0xE106000 0x1000
>> 0xE1E 0x3f000>;
>> interrupt-parent = <>;
>> interrupts = <91>;
>> +   dr_mode = "host";
>> status = "disabled";
>> };
>>
>> diff --git a/target/linux/lantiq/dts/danube.dtsi 
>> b/target/linux/lantiq/dts/danube.dtsi
>> index f11787f975..83e85c36a5 100644
>> --- a/target/linux/lantiq/dts/danube.dtsi
>> +++ b/target/linux/lantiq/dts/danube.dtsi
>> @@ -143,7 +143,7 @@
>> };
>>
>> ifxhcd@E101000 {
>> -

Re: [LEDE-DEV] [PATCH] lantiq: update USB controller handling

2017-01-06 Thread Martin Blumenstingl via Lede-dev

The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.

To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Hauke,

(CC'ing Mathias as he was looking into some of the USB issues as well)

On Fri, Jan 6, 2017 at 8:06 PM, Hauke Mehrtens  wrote:
> This makes the code use the same settings aas the vendor sdrivers.
s/aas/as/
s/sdrivers/driver/
you should probably also mention that this:
1. backports USB initialization fixes for XRX300, Danube and Amazon-SE
2. sets the clock source for all SoCs which fixes USB (initialization)
issues on Danube when using the dwc2 driver (thus fixes FS#351 and
supersedes Mathias' "lantiq: set the usb clock source" RFC patch)

> Signed-off-by: Hauke Mehrtens 
> ---
>  target/linux/lantiq/dts/amazonse.dtsi  |   3 +-
>  target/linux/lantiq/dts/ar9.dtsi   |   6 +-
>  target/linux/lantiq/dts/danube.dtsi|   2 +-
>  target/linux/lantiq/dts/vr9.dtsi   |   6 +-
>  ...MIPS-lantiq-danube-initialize-usb-on-boot.patch |  10 -
>  .../patches-4.4/0041-USB-DWC2-add-ltq-params.patch |  75 
>  .../linux/lantiq/patches-4.4/0047-poweroff.patch   |   2 +-
>  ...2-Add-support-for-Lantiq-ARX-and-XRX-SoCs.patch |  78 
>  ...ke-the-lantiq-settings-match-vendor-drive.patch |  53 ++
>  .../patches-4.4/0062-USB-DWC2-add-ltq-params.patch |  47 +
>  ...65-MIPS-lantiq-improve-USB-initialization.patch | 202 
> +
>  ...x200-add-gphy-clk-src-device-tree-binding.patch |   6 +-
>  12 files changed, 395 insertions(+), 95 deletions(-)
>  delete mode 100644 
> target/linux/lantiq/patches-4.4/0039-MIPS-lantiq-danube-initialize-usb-on-boot.patch
>  delete mode 100644 
> target/linux/lantiq/patches-4.4/0041-USB-DWC2-add-ltq-params.patch
>  create mode 100644 
> target/linux/lantiq/patches-4.4/0060-usb-dwc2-Add-support-for-Lantiq-ARX-and-XRX-SoCs.patch
>  create mode 100644 
> target/linux/lantiq/patches-4.4/0061-USB-DWC2-make-the-lantiq-settings-match-vendor-drive.patch
>  create mode 100644 
> target/linux/lantiq/patches-4.4/0062-USB-DWC2-add-ltq-params.patch
>  create mode 100644 
> target/linux/lantiq/patches-4.4/0065-MIPS-lantiq-improve-USB-initialization.patch
>
> diff --git a/target/linux/lantiq/dts/amazonse.dtsi 
> b/target/linux/lantiq/dts/amazonse.dtsi
> index bce618fed8..2b8ad08140 100644
> --- a/target/linux/lantiq/dts/amazonse.dtsi
> +++ b/target/linux/lantiq/dts/amazonse.dtsi
> @@ -122,11 +122,12 @@
> };
>
> ifxhcd@E101000 {
> -   compatible = "lantiq,ifxhcd-ase";
> +   compatible = "lantiq,ase-usb", "lantiq,ifxhcd-ase";
> reg = <0xE101000 0x1000
> 0xE12 0x3f000>;
> interrupt-parent = <>;
> interrupts = <39>;
> +   dr_mode = "host";
> status = "disabled";
> };
>
> diff --git a/target/linux/lantiq/dts/ar9.dtsi 
> b/target/linux/lantiq/dts/ar9.dtsi
> index 569f25f02c..2638a4b268 100644
> --- a/target/linux/lantiq/dts/ar9.dtsi
> +++ b/target/linux/lantiq/dts/ar9.dtsi
> @@ -137,20 +137,22 @@
> };
>
> ifxhcd@E101000 {
> -   compatible = "lantiq,ifxhcd-arx100", 
> "lantiq,ifxhcd-arx100-dwc2";
> +   compatible = "lantiq,arx100-usb", 
> "lantiq,ifxhcd-arx100";
> reg = <0xE101000 0x1000
> 0xE12 0x3f000>;
> interrupt-parent = <>;
> interrupts = <62 91>;
> +   dr_mode = "host";
> status = "disabled";
> };
>
> ifxhcd@E106000 {
> -   compatible = "lantiq,ifxhcd-arx100-dwc2";
> +   compatible = "lantiq,arx100-usb";
> reg = <0xE106000 0x1000
> 0xE1E 0x3f000>;
> interrupt-parent = <>;
> interrupts = <91>;
> +   dr_mode = "host";
> status = "disabled";
> };
>
> diff --git a/target/linux/lantiq/dts/danube.dtsi 
> b/target/linux/lantiq/dts/danube.dtsi
> index f11787f975..83e85c36a5 100644
> --- a/target/linux/lantiq/dts/danube.dtsi
> +++ b/target/linux/lantiq/dts/danube.dtsi
> @@ -143,7 +143,7 @@
> };
>
> ifxhcd@E101000 {
> -   compatible = "lantiq,ifxhcd-danube-dwc2", 
> "lantiq,ifxhcd-danube";
> +   compatible = "lantiq,danube-usb", 
> "lantiq,ifxhcd-danube";
> reg = <0xE101000 0x1000
> 0xE12 0x3f000>;
>

[LEDE-DEV] [PATCH oldpackage/eventlog oldpackage/syslog-ng3] version bump to latest

2017-01-06 Thread Philip Prindeville



update-syslog-eventlog.patch
Description: Binary data
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] lantiq: update USB controller handling

2017-01-06 Thread Hauke Mehrtens

This makes the code use the same settings aas the vendor sdrivers.

Signed-off-by: Hauke Mehrtens 
---
 target/linux/lantiq/dts/amazonse.dtsi  |   3 +-
 target/linux/lantiq/dts/ar9.dtsi   |   6 +-
 target/linux/lantiq/dts/danube.dtsi|   2 +-
 target/linux/lantiq/dts/vr9.dtsi   |   6 +-
 ...MIPS-lantiq-danube-initialize-usb-on-boot.patch |  10 -
 .../patches-4.4/0041-USB-DWC2-add-ltq-params.patch |  75 
 .../linux/lantiq/patches-4.4/0047-poweroff.patch   |   2 +-
 ...2-Add-support-for-Lantiq-ARX-and-XRX-SoCs.patch |  78 
 ...ke-the-lantiq-settings-match-vendor-drive.patch |  53 ++
 .../patches-4.4/0062-USB-DWC2-add-ltq-params.patch |  47 +
 ...65-MIPS-lantiq-improve-USB-initialization.patch | 202 +
 ...x200-add-gphy-clk-src-device-tree-binding.patch |   6 +-
 12 files changed, 395 insertions(+), 95 deletions(-)
 delete mode 100644 
target/linux/lantiq/patches-4.4/0039-MIPS-lantiq-danube-initialize-usb-on-boot.patch
 delete mode 100644 
target/linux/lantiq/patches-4.4/0041-USB-DWC2-add-ltq-params.patch
 create mode 100644 
target/linux/lantiq/patches-4.4/0060-usb-dwc2-Add-support-for-Lantiq-ARX-and-XRX-SoCs.patch
 create mode 100644 
target/linux/lantiq/patches-4.4/0061-USB-DWC2-make-the-lantiq-settings-match-vendor-drive.patch
 create mode 100644 
target/linux/lantiq/patches-4.4/0062-USB-DWC2-add-ltq-params.patch
 create mode 100644 
target/linux/lantiq/patches-4.4/0065-MIPS-lantiq-improve-USB-initialization.patch

diff --git a/target/linux/lantiq/dts/amazonse.dtsi 
b/target/linux/lantiq/dts/amazonse.dtsi
index bce618fed8..2b8ad08140 100644
--- a/target/linux/lantiq/dts/amazonse.dtsi
+++ b/target/linux/lantiq/dts/amazonse.dtsi
@@ -122,11 +122,12 @@
};
 
ifxhcd@E101000 {
-   compatible = "lantiq,ifxhcd-ase";
+   compatible = "lantiq,ase-usb", "lantiq,ifxhcd-ase";
reg = <0xE101000 0x1000
0xE12 0x3f000>;
interrupt-parent = <>;
interrupts = <39>;
+   dr_mode = "host";
status = "disabled";
};
 
diff --git a/target/linux/lantiq/dts/ar9.dtsi b/target/linux/lantiq/dts/ar9.dtsi
index 569f25f02c..2638a4b268 100644
--- a/target/linux/lantiq/dts/ar9.dtsi
+++ b/target/linux/lantiq/dts/ar9.dtsi
@@ -137,20 +137,22 @@
};
 
ifxhcd@E101000 {
-   compatible = "lantiq,ifxhcd-arx100", 
"lantiq,ifxhcd-arx100-dwc2";
+   compatible = "lantiq,arx100-usb", 
"lantiq,ifxhcd-arx100";
reg = <0xE101000 0x1000
0xE12 0x3f000>;
interrupt-parent = <>;
interrupts = <62 91>;
+   dr_mode = "host";
status = "disabled";
};
 
ifxhcd@E106000 {
-   compatible = "lantiq,ifxhcd-arx100-dwc2";
+   compatible = "lantiq,arx100-usb";
reg = <0xE106000 0x1000
0xE1E 0x3f000>;
interrupt-parent = <>;
interrupts = <91>;
+   dr_mode = "host";
status = "disabled";
};
 
diff --git a/target/linux/lantiq/dts/danube.dtsi 
b/target/linux/lantiq/dts/danube.dtsi
index f11787f975..83e85c36a5 100644
--- a/target/linux/lantiq/dts/danube.dtsi
+++ b/target/linux/lantiq/dts/danube.dtsi
@@ -143,7 +143,7 @@
};
 
ifxhcd@E101000 {
-   compatible = "lantiq,ifxhcd-danube-dwc2", 
"lantiq,ifxhcd-danube";
+   compatible = "lantiq,danube-usb", 
"lantiq,ifxhcd-danube";
reg = <0xE101000 0x1000
0xE12 0x3f000>;
interrupt-parent = <>;
diff --git a/target/linux/lantiq/dts/vr9.dtsi b/target/linux/lantiq/dts/vr9.dtsi
index 4810a91c5c..eff4944411 100644
--- a/target/linux/lantiq/dts/vr9.dtsi
+++ b/target/linux/lantiq/dts/vr9.dtsi
@@ -177,19 +177,21 @@
 
ifxhcd@E101000 {
status = "disabled";
-   compatible = "lantiq,ifxhcd-xrx200", 
"lantiq,ifxhcd-xrx200-dwc2";
+   compatible = "lantiq,xrx200-usb", 
"lantiq,ifxhcd-xrx200";
reg = <0xE101000 0x1000
0xE12 0x3f000>;
interrupt-parent = <>;
interrupts = <62 91>;
+   dr_mode = "host";
};
 
ifxhcd@E106000 {
status = "disabled";
-   compatible = "lantiq,ifxhcd-xrx200-dwc2";
+   compatible =

Re: [LEDE-DEV] [PATCH] ar71xx: add support for RB-941-2nD

2017-01-06 Thread Thibaut VARENE

I’m sorry, I’ve just realized there’s one change that I missed in the patch I 
sent, which is necessary for it to work:

Signed-off-by: Thibaut VARENE 
---
 include/image.mk |7 +++
 1 file changed, 7 insertions(+)

diff --git a/include/image.mk b/include/image.mk
index 93c3bbd..1405f46 100644
--- a/include/image.mk
+++ b/include/image.mk
@@ -309,6 +309,13 @@ define Device/InitProfile
   DEVICE_DESCRIPTION = Build firmware images for $$(DEVICE_TITLE)
 endef
 
+define Build/kernel2minor
+   if [ -x $(STAGING_DIR_HOST)/bin/kernel2minor ]; then \
+   $(STAGING_DIR_HOST)/bin/kernel2minor -k $@ -r $@.new $(1); \
+   mv $@.new $@; \
+   fi
+endef
+
 define Device/Init
   DEVICE_NAME := $(1)
   KERNEL:=



> Le 4 janv. 2017 à 23:04, "Thibaut VARENE 
> "@vps.slashdirt.org a écrit :
> 
> From e55aa1ddff1563d582b456807f20c0457fcaed77 Mon Sep 17 00:00:00 2001
> From: Thibaut VARENE 
> Date: Wed, 4 Jan 2017 22:44:54 +0100
> Subject: [PATCH] ar71xx: add support for RB-941-2nD
> 
> Add full support for Mikrotik RB-941-2nD (hAP lite)
> 
> Original patch by Sergey Sergeev  and
> more information is available here:
> https://wiki.openwrt.org/toh/mikrotik/rb941_2nd
> I updated and adapted the patch to apply cleanly to LEDE trunk
> and added proper numbering for the switch ports (matching case
> labels).
> Tested working on actual hardware with the information
> provided in the above webpage. Sysupgrade works.
> 
> Signed-off-by: Thibaut VARENE 
> ---
> target/linux/ar71xx/base-files/etc/board.d/01_leds |   3 +
> .../linux/ar71xx/base-files/etc/board.d/02_network |   4 +
> target/linux/ar71xx/base-files/etc/diag.sh |   2 +-
> target/linux/ar71xx/base-files/lib/ar71xx.sh   |   3 +
> .../ar71xx/base-files/lib/upgrade/platform.sh  |  29 +++-
> target/linux/ar71xx/config-4.4 |   1 +
> .../ar71xx/files/arch/mips/ath79/Kconfig.openwrt   |  10 ++
> target/linux/ar71xx/files/arch/mips/ath79/Makefile |   1 +
> .../ar71xx/files/arch/mips/ath79/mach-rb941.c  | 174 +
> .../linux/ar71xx/files/arch/mips/ath79/machtypes.h |   1 +
> target/linux/ar71xx/image/legacy.mk|  23 +++
> .../linux/ar71xx/mikrotik/profiles/03-norflash.mk  |  16 ++
> 12 files changed, 263 insertions(+), 4 deletions(-)
> create mode 100644 target/linux/ar71xx/files/arch/mips/ath79/mach-rb941.c
> create mode 100644 target/linux/ar71xx/mikrotik/profiles/03-norflash.mk
> 
> diff --git a/target/linux/ar71xx/base-files/etc/board.d/01_leds 
> b/target/linux/ar71xx/base-files/etc/board.d/01_leds
> index c6dcf36..75b5142 100755
> --- a/target/linux/ar71xx/base-files/etc/board.d/01_leds
> +++ b/target/linux/ar71xx/base-files/etc/board.d/01_leds
> @@ -199,6 +199,9 @@ rb-750)
>   ucidef_set_led_switch "port4" "port4" "rb750:green:port4" "switch0" 
> "0x04"
>   ucidef_set_led_switch "port5" "port5" "rb750:green:port5" "switch0" 
> "0x02"
>   ;;
> +rb-941-2nd)
> + ucidef_set_led_timer "act" "act" "rb:green:act" "1000" "1000"
> + ;;
> rb-2011l|\
> rb-2011uas|\
> rb-2011uias|\
> diff --git a/target/linux/ar71xx/base-files/etc/board.d/02_network 
> b/target/linux/ar71xx/base-files/etc/board.d/02_network
> index 8acd214..6fd9601 100755
> --- a/target/linux/ar71xx/base-files/etc/board.d/02_network
> +++ b/target/linux/ar71xx/base-files/etc/board.d/02_network
> @@ -237,6 +237,10 @@ ar71xx_setup_interfaces()
>   dap-2695-a1)
>   ucidef_add_switch "switch0" "0@eth0" "2:lan" "3:wan" "6@eth1"
>   ;;
> + rb-941-2nd)
> + ucidef_add_switch "switch0" \
> + "0@eth0" "1:lan:4" "2:lan:3" "3:lan:2" "4:wan:1"
> + ;;
>   db120|\
>   rb-2011l|\
>   rb-2011uas|\
> diff --git a/target/linux/ar71xx/base-files/etc/diag.sh 
> b/target/linux/ar71xx/base-files/etc/diag.sh
> index d060ccf..75c6c9a 100644
> --- a/target/linux/ar71xx/base-files/etc/diag.sh
> +++ b/target/linux/ar71xx/base-files/etc/diag.sh
> @@ -288,7 +288,7 @@ get_status_led() {
>   rb-912uag-5hpnd)
>   status_led="rb:green:user"
>   ;;
> - rb-951ui-2hnd)
> + rb-951ui-2hnd | rb-941-2nd)
>   status_led="rb:green:act"
>   ;;
>   rb-sxt2n|\
> diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh 
> b/target/linux/ar71xx/base-files/lib/ar71xx.sh
> index 3241100..527112b 100755
> --- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
> +++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
> @@ -827,6 +827,9 @@ ar71xx_board_detect() {
>   *"RouterBOARD 912UAG-5HPnD")
>   name="rb-912uag-5hpnd"
>   ;;
> + *"RouterBOARD 941-2nD")
> + name="rb-941-2nd"
> + ;;
>   *"RouterBOARD 951G-2HnD")
>   name="rb-951g-2hnd"
>   ;;
> diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh 
>

Re: [LEDE-DEV] Fading out PolarSSL

2017-01-06 Thread Ted Hess

On Tue, 2017-01-03 at 17:32 +0100, Steven Barth wrote:
> Hey everyone,
> 
> > 
> > Currently known remaining users of polarssl are:
> > 
> >  * bmx7
> >  * pianod
> >  * shadowsocks-libev-polarssl
> >  * shairport-sync-mini
> >  * shairport-sync-polarssl
> >  * transmission-cli-polarssl
> >  * transmission-daemon-polarssl
> >  * transmission-remote-polarssl
> >  * umurmur-polarssl
> > 
> > 
> > Please provide feedback on which approach you'd prefer and if you'd be
> > affected by the PolarSSL deprecation or not.
> I think for all but the first two from this list, there is a 
> non-polarssl version already packaged.
> Which would mainly leave bmx7 and pianod as main concerns. I think the 
> former used to work with cyassl
> at some point in time and the latter should work with gnutls. Both of 
> which we have, so it might just
> be a minor change to the packaging Makefiles.
> 
> So from my point of view dropping libpolarssl now (with a bit of upfront 
> notice to the maintainers)
> makes more sense than trying to drop a package later which is a bit of 
> unexpected and am not sure if
> it can be effectively announced in a service release and just delays the 
> inevitable.
> 
> 
> Cheers,
> 
> Steven
> 
> ___
> lede-adm mailing list
> lede-...@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-adm

Drop it now.

Speaking for pianod and shairport-sync... I have already updated pianod (which I
still develop) to use mbed TLS and I am currently working with the shairport-
sync developer to replace PolarSSL with mbed TLS this weekend.

/ted

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

Re: [LEDE-DEV] SHA256 hashes for packages

2017-01-06 Thread Hannu Nyman

On 6.1.2017 0:28, Heinrich Schuchardt wrote:
> Hello Hannu,
> why should a variable be called MD5 if it holds an SHA256 hash? That does 
not make any sense.

>
> Could you, please, point me to the thread on the openwrt or lede list that 
discussed this weird idea.

Not sure if that widely discussed in mailing lists in advance, but PKG_MD5SUM 
has accepted also SHA256 hash since January 2016 ( 
https://dev.openwrt.org/changeset/48253/ ) and the first core package was 
converted to use the mixed syntax immediately afterwards by 
https://dev.openwrt.org/changeset/48254 in January 2016.

Quite many packages in the packages feed repo have already been similarly 
converted to use sha256 although the field is named PKG_MD5SUM.

> why should a variable be called MD5 if it holds an SHA256 hash?

You are right, that is confusing. To avoid confusion LEDE has already 
introduced PKG_HASH with lede-project/source@7416d2e . Most core packages in 
LEDE were switched to use sha256 and the new variable with 
lede-project/source@720b992

But as Openwrt has not yet introduced PKG_HASH, we can't use only PKG_HASH in 
the packages feed repo that is common to both.

As Jow already suggested in his answer, one non-confusing alternative is to 
use both PKG_MD5SUM with MD5 hash and PKG_HASH with SHA256 hash. Some 
packages have been committed that way.

> Abusing the MD5 variable with SHA256 hashes will break compatibility with 
older openwrt releases.

To my knowledge the master branch in packages in only target DD/master/trunk 
in Openwrt and master in LEDE. Older release have their own branches like 
for-15.05 etc.

Ps. I had already answered to you in Github, but I only now noticed that you 
had written also this to the mailing lists at the same time.

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

Re: [LEDE-DEV] [PATCH] lantiq: update USB controller handling

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH oldpackage/eventlog oldpackage/syslog-ng3] version bump to latest

Re: [LEDE-DEV] [PATCH oldpackage/eventlog oldpackage/syslog-ng3] version bump to latest

Re: [LEDE-DEV] [PATCH] lantiq: update USB controller handling

Re: [LEDE-DEV] [PATCH] lantiq: update USB controller handling

[LEDE-DEV] [PATCH oldpackage/eventlog oldpackage/syslog-ng3] version bump to latest

[LEDE-DEV] [PATCH] lantiq: update USB controller handling

Re: [LEDE-DEV] [PATCH] ar71xx: add support for RB-941-2nD

Re: [LEDE-DEV] Fading out PolarSSL

Re: [LEDE-DEV] SHA256 hashes for packages

10 matches

Site Navigation

Mail list logo

Footer information