Re: [OpenWrt-Devel] [PATCH 0/3] ar71xx: fix imagenames for some TPlink units

2016-03-04 Thread John Crispin
On 05/03/2016 03:57, Sven Roederer wrote: > Am Thursday 25 February 2016, 09:07:22 schrieb John Crispin: >> i am also pretty sure that the wiki was not updated as per my >> request to the last series. > > Hi, I'm back now after some hardware outage ... > > Thanks for applying the patches; I

Re: [OpenWrt-Devel] [PATCH 0/3] ar71xx: fix imagenames for some TPlink units

2016-03-04 Thread Sven Roederer
Am Thursday 25 February 2016, 09:07:22 schrieb John Crispin: > i am also pretty sure that the wiki was not updated as per my > request to the last series. Hi, I'm back now after some hardware outage ... Thanks for applying the patches; I just finished updating the Wiki. What are the chances

[OpenWrt-Devel] [PATCH v3 06/11] base-files: change type of adsl and vdsl to dsl only

2016-03-04 Thread Hauke Mehrtens
Instead of having two different types adsl and vdsl just create one dsl type. This way we can use the same luci code for adsl and vdsl and the config parameters are not so different. Signed-off-by: Hauke Mehrtens --- package/base-files/files/bin/config_generate | 2 +- 1 file

[OpenWrt-Devel] [PATCH v3 05/11] ltq-vdsl-app: make the dsl_control application stop cleanly

2016-03-04 Thread Hauke Mehrtens
I am not calling dsl_cmd because I want to ignore the lock, quit should also be send when someone else is accessing it. I saw that some other call was stuck here and all following calls were stuck in the dsl_cmd lock. Signed-off-by: Hauke Mehrtens ---

[OpenWrt-Devel] [PATCH v3 08/11] ltq-vdsl-app: sync annex option between from ADSL package

2016-03-04 Thread Hauke Mehrtens
The detailed annex option were only available in the danube DSL app including the activation of G.992.2 Annex A (ADSL Lite). This is now also added to the vdsl app for the vrx200. Signed-off-by: Hauke Mehrtens --- .../network/config/ltq-vdsl-app/files/dsl_control | 44

[OpenWrt-Devel] [PATCH v3 11/11] lantiq: print profile name in dsl lucistat

2016-03-04 Thread Hauke Mehrtens
Signed-off-by: Hauke Mehrtens --- target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh b/target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh index

[OpenWrt-Devel] [PATCH v3 10/11] ltq-vdsl-app: do not set the reserved bit 4 in the xTSE 8

2016-03-04 Thread Hauke Mehrtens
I do not know if this causes any problems now, but we should not set it, because it is reserved. Some more recent versions of the Lantiq DSL API driver and Control is checking if only valid bits are set. Signed-off-by: Hauke Mehrtens ---

[OpenWrt-Devel] [PATCH v3 09/11] ltq-vdsl-app: make it possible to configure ADSL/VDSL independently

2016-03-04 Thread Hauke Mehrtens
There are some cases where ISPs are running ATM over VDSL or PTM over ADSL, this is not the common case, but these cases exist. Make it possible to configure OpenWrt for such cases by adding a new config option line_mode. Signed-off-by: Hauke Mehrtens ---

[OpenWrt-Devel] [PATCH v3 04/11] lantiq: add dsl firmware to default packages

2016-03-04 Thread Hauke Mehrtens
Signed-off-by: Hauke Mehrtens --- target/linux/lantiq/xrx200/profiles/lantiq.mk | 4 ++-- target/linux/lantiq/xrx200/profiles/tplink.mk | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/target/linux/lantiq/xrx200/profiles/lantiq.mk

[OpenWrt-Devel] [PATCH v3 07/11] ltq-adsl-app: sync annex option between from VDSL package

2016-03-04 Thread Hauke Mehrtens
The adsl control app missed the activation of annex M and annex L in the Annex A part, this now activates everything the firmware supports. In Annex L type only the wide US (Mask1) was activated, now also the narrow US (Mask2) version gets activated. In addition annex J was also added.

[OpenWrt-Devel] [PATCH v3 03/11] lantiq: do not set default firmware file

2016-03-04 Thread Hauke Mehrtens
We are now shipping a DSL firmware, do not set it by default to some file name. Signed-off-by: Hauke Mehrtens --- package/base-files/files/lib/functions/uci-defaults.sh | 6 ++ target/linux/lantiq/base-files/etc/board.d/02_network | 2 +- 2 files changed, 3 insertions(+),

[OpenWrt-Devel] [PATCH v3 02/11] ltq-vdsl-app: load the vrx200 firmware or patch it

2016-03-04 Thread Hauke Mehrtens
This checks for the VRX firmware provided in the OpenWrt package. Signed-off-by: Hauke Mehrtens --- package/network/config/ltq-vdsl-app/Makefile | 2 +- .../network/config/ltq-vdsl-app/files/dsl_control | 42 ++ 2 files changed, 43 insertions(+), 1

[OpenWrt-Devel] [PATCH v3 01/11] dsl-vrx200-firmware-xdsl: create Lantiq vrx200 firmware patches

2016-03-04 Thread Hauke Mehrtens
Instead of having two big binaries only add one binary and then a patch to create the other one when needed at runtime. This is easier to handle in one Makeifle for both firmware files. Signed-off-by: Hauke Mehrtens --- .../lantiq/dsl-vrx200-firmware-xdsl-a/Makefile | 47

[OpenWrt-Devel] [PATCH v3 00/11] Lantiq dsl improvements

2016-03-04 Thread Hauke Mehrtens
This was tested on a TP-Link vr200v connected to a Deutsche Telekom line. Some testes with a Danube based device would be nice. changes since v2: * added some comments to the code Hauke Mehrtens (11): dsl-vrx200-firmware-xdsl: create Lantiq vrx200 firmware patches ltq-vdsl-app: load the

[OpenWrt-Devel] [PATCH v2 2/2] ipvsadm: OpenWrt configuration

2016-03-04 Thread Mauro Mozzarelli
8< This ipvsadm package contains: - uci ipvs sample configuration file - ipvsadm service startup/shutdown script - scheduler checking real servers' availability and re-configuring ipvs tables accordingly Dependencies: - ipvs kernel modules - ipvsadm tool Signed-off-by: Mauro

[OpenWrt-Devel] [PATCH v2 1/2] ipvsadm

2016-03-04 Thread Mauro Mozzarelli
8< This package contains: - ipvsadm utility to configure IP VS tables, virtual and real servers Dependencies: - ipvs kernel modules configuration (patch previously posted) Signed-off-by: Mauro Mozzarelli 8< diff --git

[OpenWrt-Devel] [PATCH 4/4] brcm2708: add Raspberry Pi 3 support

2016-03-04 Thread Álvaro Fernández Rojas
Signed-off-by: Álvaro Fernández Rojas --- target/linux/brcm2708/Makefile | 8 +- .../brcm2708/base-files/etc/board.d/02_network | 5 +- target/linux/brcm2708/base-files/etc/diag.sh | 7 +- target/linux/brcm2708/base-files/etc/inittab |

[OpenWrt-Devel] [PATCH 2/4] brcm2708-gpu-fw: update to latest version

2016-03-04 Thread Álvaro Fernández Rojas
mation. @@ -8,13 +8,13 @@ include $(TOPDIR)/rules.mk include $(INCLUDE_DIR)/kernel.mk PKG_NAME:=brcm2708-gpu-fw -PKG_REV:=98e801605b31a5d7a4c36de5cb1d0e33ce95e8ab -PKG_VERSION:=20151214 +PKG_REV:=30fe8178d61c1ff9bc168edaafdbcb101aa6245e +PKG_VERSION:=20160304 PKG_RELEASE:=1 PKG_SOURCE:=$(P

[OpenWrt-Devel] [PATCH 1/4] include: add Cortex-A53 CPU_TYPE

2016-03-04 Thread Álvaro Fernández Rojas
Signed-off-by: Álvaro Fernández Rojas --- include/target.mk | 1 + 1 file changed, 1 insertion(+) diff --git a/include/target.mk b/include/target.mk index dbb6327..76fbd99 100644 --- a/include/target.mk +++ b/include/target.mk @@ -237,6 +237,7 @@ ifeq ($(DUMP),1)

[OpenWrt-Devel] [PATCH 0/4] Add Raspberry Pi 3 support

2016-03-04 Thread Álvaro Fernández Rojas
These patches add basic Raspberry Pi 3 support. Bootlog: https://gist.github.com/Noltari/92f51259c9d18506192b#file-bcm2710_rpi3-log Known issues: 1) No ARMv8 64 bit support. More info: https://github.com/raspberrypi/firmware/issues/550 2) UART0 is connected to BCM43430 (Bluetooth), which

[OpenWrt-Devel] [PATCH] openvpn: add support for X.509 name options

2016-03-04 Thread Jeffery To
x509-username-field was added in OpenVPN 2.2, and verify-x509-name was added in 2.3. This fixes ticket #18807. Signed-off-by: Jeffery To --- package/network/services/openvpn/files/openvpn.init | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [OpenWrt-Devel] Request for Feedback - prplwrt Software Support Program - initial draft

2016-03-04 Thread Eric Schultz
Saverio, No problem, I'm happy to clarify. prplwrt is a working group in prpl Foundation, which is a membership organization focusing on open source and industry. prplwrt in particular has the following mission: "The mission of the prplwrt PEG is to enable close collaboration between users,

Re: [OpenWrt-Devel] USB Hotplug

2016-03-04 Thread John Crispin
On 04/03/2016 17:50, Baptiste Clenet wrote: > We don't use the current tree but a version from November. > You're talking about this changeset: > https://dev.openwrt.org/changeset/48749 > > I will apply it and let you know if it is better. > >>> >> yep, try adding that one please and see if

Re: [OpenWrt-Devel] USB Hotplug

2016-03-04 Thread Baptiste Clenet
2016-03-04 16:57 GMT+01:00 John Crispin : > > > On 04/03/2016 16:43, John Crispin wrote: >> >> >> On 04/03/2016 16:42, alzhao wrote: >>> Hi john, >>> can you specify which patch? I want to check. >>> On Fri, 4 Mar 2016 at 23:34, John Crispin >>

Re: [OpenWrt-Devel] USB Hotplug

2016-03-04 Thread John Crispin
On 04/03/2016 16:43, John Crispin wrote: > > > On 04/03/2016 16:42, alzhao wrote: >> Hi john, >> can you specify which patch? I want to check. >> On Fri, 4 Mar 2016 at 23:34, John Crispin > > wrote: >> >> >> >> On 04/03/2016 15:07, alzhao

Re: [OpenWrt-Devel] USB Hotplug

2016-03-04 Thread John Crispin
On 04/03/2016 16:42, alzhao wrote: > Hi john, > can you specify which patch? I want to check. > On Fri, 4 Mar 2016 at 23:34, John Crispin > wrote: > > > > On 04/03/2016 15:07, alzhao wrote: > > Did you develop the board by yourself?

Re: [OpenWrt-Devel] USB Hotplug

2016-03-04 Thread alzhao
Hi john, can you specify which patch? I want to check. On Fri, 4 Mar 2016 at 23:34, John Crispin wrote: > > > On 04/03/2016 15:07, alzhao wrote: > > Did you develop the board by yourself? Generally this is a hardware > > problem, like wrong resistors. After the system boot

Re: [OpenWrt-Devel] USB Hotplug

2016-03-04 Thread John Crispin
On 04/03/2016 15:07, alzhao wrote: > Did you develop the board by yourself? Generally this is a hardware > problem, like wrong resistors. After the system boot the USB cannot > supply enough power to the drive. > > > On Fri, 4 Mar 2016 at 21:57, Baptiste Clenet

Re: [OpenWrt-Devel] USB Hotplug

2016-03-04 Thread alzhao
Did you develop the board by yourself? Generally this is a hardware problem, like wrong resistors. After the system boot the USB cannot supply enough power to the drive. On Fri, 4 Mar 2016 at 21:57, Baptiste Clenet wrote: > Hi, > > I run OpenWRT on a mt7688 board, if I

[OpenWrt-Devel] USB Hotplug

2016-03-04 Thread Baptiste Clenet
Hi, I run OpenWRT on a mt7688 board, if I plug a pendrive before the boot, it is detected and I can store data on it. However, after the board has finished booting, if I plug the pendrive, I can't detect it, the LED on the pendrive switch on and off after a 1/2 sec. Should I include something

[OpenWrt-Devel] [PATCH] ramips: add support for Planex MZK-WDPR.

2016-03-04 Thread YuheiOKAWA
add support for Planex MZK-WDPR. MZK-WDPR(MZK-WDPR-R01) is internet radio tuner. This patch is "network board" in MZK-WDPR. LCD board is non OpenWrt Platform. Signed-off-by: YuheiOKAWA --- .../linux/ramips/base-files/etc/board.d/02_network | 1 +

Re: [OpenWrt-Devel] Request for Feedback - prplwrt Software Support Program - initial draft

2016-03-04 Thread Saverio Proto
Wow, I received your email on so many mailing lists that I could not stop from answering. Could you please give some context about what is prplwrt ? I have been working with OpenWrt since 2006 and it is the first time I hear about prplwrt. The website did not help, and all this people are

[OpenWrt-Devel] [PATCH netifd] device: Support setting autoneg, speed and duplex

2016-03-04 Thread ben
From: Ben Kelly Adds configuration attributes for auto negotiation on/off, link speed and duplex. Uses ethtool ioctls to modify link settings. Some net drivers will not accept ethtool operations until after the IFF_UP interface flag is set, so these ioctls are being called from

[OpenWrt-Devel] Proposal: change buildbot's build failure logic to be less restrictive regarding packages from feeds

2016-03-04 Thread Hannu Nyman
We have seen several times in the past few months that one non-essential package from feeds fails to build and stops the whole buildbot build. Yesterday it was python-cffi, but it has been ola, ltq-vmmc etc. It seems strange to me that non-essential packages from feeds, which by definition

Re: [OpenWrt-Devel] RT5350 board issues.

2016-03-04 Thread Frédéric Konrad
Hi John, Thanks for your answer! On 04/03/2016 10:18, John Crispin wrote: > On 04/03/2016 10:09, Frédéric Konrad wrote: >> Ping? >> >> Any idea for this? Or just a clue so I can fix that? >> (I don't have much experience with ralink mips stuff) >> Using a vanilla kernel seems to boot fine BTW..

Re: [OpenWrt-Devel] RT5350 board issues.

2016-03-04 Thread John Crispin
On 04/03/2016 10:09, Frédéric Konrad wrote: > Ping? > > Any idea for this? Or just a clue so I can fix that? > (I don't have much experience with ralink mips stuff) > Using a vanilla kernel seems to boot fine BTW.. > > Thanks, > Fred > you are using a kernel that has no dtb. you will need to

Re: [OpenWrt-Devel] RT5350 board issues.

2016-03-04 Thread Frédéric Konrad
Ping? Any idea for this? Or just a clue so I can fix that? (I don't have much experience with ralink mips stuff) Using a vanilla kernel seems to boot fine BTW.. Thanks, Fred On 01/03/2016 12:19, Frederic Konrad wrote: > Hi everybody, > > I'm a openwrt newbie and I've some issues running

[OpenWrt-Devel] [PATCH] [packages] opkg: Fix handling of sha256sums for conffiles

2016-03-04 Thread Michal Hrusecky
MD5s are shorter than SHA256, so reading buffer has to be bigger to read the whole hash. Signed-off-by: Michal Hrusecky --- package/system/opkg/Makefile | 2 +- package/system/opkg/patches/230-drop_md5_support.patch | 14 ++ 2 files