Re: [OpenWrt-Devel] [PATCH] swconfig: support setting SWITCH_TYPE_LINK attributes

2016-01-13 Thread Florian Fainelli
On Jan 13, 2016 10:07 PM, "Stefan Rompf"  wrote:
>
> Hi,
>
> On Montag, 11. Januar 2016 23:45:39 Rafał Miłecki wrote:
>
> > > Any comments to this usage/syntax? It doesn't look too nice (this long
> > > quoted string as a value), but swconfig is strongly focused on simple
> > > values.
> >
> > One more RFC... anyone?
>
> I am not an OpenWRT core developer so I cannot comment on the niceness of
the
> interface ;-) The string does not allow to specify combinations like
autoneg
> on, advertise 10 and 1000, but not 100, but that would be a very esoteric
use
> case and it is about configuring a switch port and not an ethernet tester.
> IMHO for the normal use case, it allows to specify everything that is
needed.
>
> So for me it's all right.

Same here, does not really bother me to go through several command lines to
get the desired settings.

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


Re: [OpenWrt-Devel] [PATCH] swconfig: support setting SWITCH_TYPE_LINK attributes

2016-01-13 Thread Stefan Rompf
Hi,

On Montag, 11. Januar 2016 23:45:39 Rafał Miłecki wrote:

> > Any comments to this usage/syntax? It doesn't look too nice (this long
> > quoted string as a value), but swconfig is strongly focused on simple
> > values.
> 
> One more RFC... anyone?

I am not an OpenWRT core developer so I cannot comment on the niceness of the 
interface ;-) The string does not allow to specify combinations like autoneg 
on, advertise 10 and 1000, but not 100, but that would be a very esoteric use 
case and it is about configuring a switch port and not an ethernet tester. 
IMHO for the normal use case, it allows to specify everything that is needed.

So for me it's all right.

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


[OpenWrt-Devel] Patchwork registration issues

2016-01-13 Thread Daniel Dickinson
Patchwork failed to send confirmation email to my email address, for the 
account cshore AND there is not password reset option, nor means to 
re-request confirmation email AND it won't let me register an already 
registered email address AND I can't login because the account is 
'inactive' (probably because 'not confirmed').


Regards,

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


[OpenWrt-Devel] [PATCH] ar71xx: add support for Netgear WPN824N

2016-01-13 Thread Hartmut Knaack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Add support for Netgear WPN824N.
Hardware specs:
  * AR7240, 4 LAN ports, 1 WAN port
  * AR9285 WLAN
  * 32 MB RAM
  * 4 MB Flash
  * 16 LEDs (LAN, WAN and Power/Status contain two LEDs for dual color
effect)
  * 3 Buttons (not supported)

Signed-off-by: Hartmut Knaack 
- ---
Development Thread: https://forum.openwrt.org/viewtopic.php?id=30388
Wiki Page: https://wiki.openwrt.org/toh/netgear/wpn824n

Any suggestions about a better default configuration of the LAN/WAN LEDs,
to make use of their second color, are highly appreciated.
- ---
 target/linux/ar71xx/base-files/etc/board.d/01_leds |  20 +++-
 .../linux/ar71xx/base-files/etc/board.d/02_network |   3 +-
 target/linux/ar71xx/base-files/etc/diag.sh |   3 +-
 target/linux/ar71xx/base-files/lib/ar71xx.sh   |   3 +
 .../lib/preinit/05_set_preinit_iface_ar71xx|   1 +
 .../ar71xx/base-files/lib/upgrade/platform.sh  |   3 +-
 .../ar71xx/files/arch/mips/ath79/Kconfig.openwrt   |   2 +-
 .../ar71xx/files/arch/mips/ath79/mach-wnr2000-v3.c | 124 -
 .../linux/ar71xx/files/arch/mips/ath79/machtypes.h |   1 +
 target/linux/ar71xx/generic/profiles/netgear.mk|  10 ++
 target/linux/ar71xx/image/Makefile |   1 +
 .../files/drivers/mtd/mtdsplit/mtdsplit_uimage.c   |   2 +
 12 files changed, 166 insertions(+), 7 deletions(-)

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 cfb42a5..151eac2 100755
- --- a/target/linux/ar71xx/base-files/etc/board.d/01_leds
+++ b/target/linux/ar71xx/base-files/etc/board.d/01_leds
@@ -684,7 +684,25 @@ wnr2000-v4)
ucidef_set_led_switch "lan3" "LAN3" "netgear:amber:lan3" "switch0" 
"0x08"
ucidef_set_led_switch "lan4" "LAN4" "netgear:amber:lan4" "switch0" 
"0x10"
ucidef_set_led_usbdev "usb" "USB" "netgear:amber:status" "1-1"
- -;;
+   ;;
+
+wpn824n)
+   ucidef_set_led_netdev "wan-amber" "WAN (amber)" "netgear:amber:wan" 
"eth0"
+   ucidef_set_led_wlan "wlan" "WLAN" "netgear:blue:wlan" "phy0tpt"
+   ucidef_set_led_switch "lan1amber" "LAN1 (amber)" "netgear:amber:lan1" 
"switch0" "0x02"
+   ucidef_set_led_switch "lan2amber" "LAN2 (amber)" "netgear:amber:lan2" 
"switch0" "0x04"
+   ucidef_set_led_switch "lan3amber" "LAN3 (amber)" "netgear:amber:lan3" 
"switch0" "0x08"
+   ucidef_set_led_switch "lan4amber" "LAN4 (amber)" "netgear:amber:lan4" 
"switch0" "0x10"
+   ucidef_set_led_default "lan1green" "LAN1 (green)" "netgear:green:lan1" 
"0"
+   ucidef_set_led_default "lan2green" "LAN2 (green)" "netgear:green:lan2" 
"0"
+   ucidef_set_led_default "lan3green" "LAN3 (green)" "netgear:green:lan3" 
"0"
+   ucidef_set_led_default "lan4green" "LAN4 (green)" "netgear:green:lan4" 
"0"
+   ucidef_set_led_default "wan-green" "WAN (green)" "netgear:green:wan" "0"
+   ucidef_set_led_default "wps1" "WPS1" "netgear:blue:wps1" "0"
+   ucidef_set_led_default "wps2" "WPS2" "netgear:blue:wps2" "0"
+   ucidef_set_led_default "status" "STATUS" "netgear:amber:status" "0"
+   ucidef_set_led_default "test" "TEST" "netgear:amber:test" "0"
+   ;;
 
 wzr-hp-ag300h)
ucidef_set_led_default "diag" "DIAG" "buffalo:red:diag" "0"
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 6b6c6a4..ed568b8 100755
- --- a/target/linux/ar71xx/base-files/etc/board.d/02_network
+++ b/target/linux/ar71xx/base-files/etc/board.d/02_network
@@ -226,7 +226,8 @@ wnr2000-v3 |\
 wnr2000-v4 |\
 wnr2200 |\
 wnr612-v2 |\
- -wnr1000-v2)
+wnr1000-v2 |\
+wpn824n)
ucidef_set_interfaces_lan_wan "eth1" "eth0"
ucidef_add_switch "switch0" \
"0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "4@eth1" # XXX: confirm!
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh 
b/target/linux/ar71xx/base-files/etc/diag.sh
index 13a0a98..c0e73ad 100644
- --- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -370,7 +370,8 @@ get_status_led() {
wnr2000 | \
wnr2200 |\
wnr612-v2 |\
- - wnr1000-v2)
+   wnr1000-v2 |\
+   wpn824n)
status_led="netgear:green:power"
;;
wp543)
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh 
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index 678482e..34d5741 100755
- --- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -974,6 +974,9 @@ ar71xx_board_detect() {
*"WNR1000 V2")
name="wnr1000-v2"
;;
+   *WPN824N)
+   name="wpn824n"
+   ;;
*WRT160NL)
name="wrt160nl"
;;
diff --git 
a/target/linux/ar71xx/base-files/lib/preinit/05_set_preinit_iface_ar71xx 
b/target/linux/ar71xx/base-files/lib/preinit/05_set_preinit_iface_ar71xx
index

Re: [OpenWrt-Devel] lantiq: Initial linux 4.4 support (with SPI problems)

2016-01-13 Thread Daniel Schwierzeck
Hi Martin,

Am Mittwoch, den 13.01.2016, 20:23 +0100 schrieb Martin Blumenstingl:
> Hi John,
> 
> On Mon, Jan 11, 2016 at 3:25 PM, Martin Blumenstingl
>  wrote:
> > Here's the kernel log from the TD-W8970: 
> > https://paste.kde.org/pia7p73i9
> > I have debugged it and split_tplink_kernel gets 0x2 as offset
> > and
> > 0x7A as size (which looks correct). However, when mtd_read
> > tries to
> > read the magic bytes it only gets 0x.
> I found out that reverting this upstream commit makes SPI work again:
> [0]
> 
> Then I had a deeper look at our SPI driver - that's where I need some
> help from you.

could you retry with the attached driver? 

It is a complete rewrite with DT support and runs against the UGW-6.1.1
kernel. Unfortunately I hadn't time yet to adapt and test it with
OpenWRT. Maybe you want to volunteer for that ;)

The driver works on xRX200 with following DT bindings:

xrx200.dtsi:
fpi {
...
spi: spi@e100800 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "lantiq,xrx200-spi";
reg = <0xe100800 0x100>;
interrupt-parent = <&icu0>;
interrupts = <22 23 24 25>;
interrupt-names = "spi_rx", "spi_tx", "spi_err",
"spi_frm";

status = "disabled";
};
...
};


board.dts:

&gpio {
...
pins_spi_default: pins_spi_default {
spi_in {
lantiq,groups = "spi_din";
lantiq,function = "spi";
};
spi_out {
lantiq,groups = "spi_dout", "spi_clk",
"spi_cs4";
lantiq,function = "spi";
lantiq,output = <1>;
};
};
...
};

&spi {
pinctrl-names = "default";
pinctrl-0 = <&pins_spi_default>;

status = "ok";

m25p80@4 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "spansion,m25p80";
reg = <4>;
spi-max-frequency = <2500>;
};
};

-- 
- Daniel
>From 0175fc559debc22fe8d17e9b8ffd1452e0a4667d Mon Sep 17 00:00:00 2001
From: Daniel Schwierzeck 
Date: Tue, 16 Dec 2014 15:40:32 +0100
Subject: [PATCH 1/2] spi: add support for Lantiq SPI controller

Signed-off-by: Daniel Schwierzeck 
---
 drivers/spi/Kconfig  |7 +
 drivers/spi/Makefile |1 +
 drivers/spi/spi-lantiq.c | 1089 ++
 3 files changed, 1097 insertions(+)
 create mode 100644 drivers/spi/spi-lantiq.c

diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index bc36db5..af8aaf1 100755
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfig
@@ -266,6 +266,13 @@ config SPI_FSL_ESPI
 	  From MPC8536, 85xx platform uses the controller, and all P10xx,
 	  P20xx, P30xx,P40xx, P50xx uses this controller.
 
+config SPI_LANTIQ
+	tristate "Lantiq SPI controller"
+	depends on LANTIQ && (SOC_TYPE_XWAY || SOC_FALCON)
+	help
+	  This driver supports the Lantiq SPI controller in master
+	  mode.
+
 config SPI_OC_TINY
 	tristate "OpenCores tiny SPI"
 	depends on GPIOLIB
diff --git a/drivers/spi/Makefile b/drivers/spi/Makefile
index 658f181..f981db9 100755
--- a/drivers/spi/Makefile
+++ b/drivers/spi/Makefile
@@ -36,6 +36,7 @@ obj-$(CONFIG_SPI_FSL_SPI)		+= spi-fsl-spi.o
 obj-$(CONFIG_SPI_GPIO)			+= spi-gpio.o
 obj-$(CONFIG_SPI_GPIO_OLD)		+= spi_gpio_old.o
 obj-$(CONFIG_SPI_IMX)			+= spi-imx.o
+obj-$(CONFIG_SPI_LANTIQ)		+= spi-lantiq.o
 obj-$(CONFIG_SPI_LM70_LLP)		+= spi-lm70llp.o
 obj-$(CONFIG_SPI_MPC512x_PSC)		+= spi-mpc512x-psc.o
 obj-$(CONFIG_SPI_MPC52xx_PSC)		+= spi-mpc52xx-psc.o
diff --git a/drivers/spi/spi-lantiq.c b/drivers/spi/spi-lantiq.c
new file mode 100644
index 000..03c730d
--- /dev/null
+++ b/drivers/spi/spi-lantiq.c
@@ -0,0 +1,1089 @@
+/*
+ * Copyright (C) 2011-2015 Daniel Schwierzeck 
+ *
+ * This program is free software; you can distribute 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 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+
+#include 
+
+#define SPI_RX_IRQ_NAME		"spi_rx"
+#define SPI_TX_IRQ_NAME		"spi_tx"
+#define SPI_ERR_IRQ_NAME	"spi_err"
+#define SPI_FRM_IRQ_NAME	"spi_frm"
+
+#define SPI_CLC			0x00
+#define SPI_PISEL		0x04
+#define SPI_ID			0x08
+#define SPI_CON			0x10
+#define SPI_STAT		0x14
+#define SPI_WHBSTATE		0x18
+#define SPI_TB			0x20
+#define SPI_RB			0x24
+#define SPI_RXFCON		0x30
+#define SPI_TXFCON		0x34
+#define SPI_FSTAT		0x38
+#define SPI_BRT			0x40
+#define SPI_BRSTAT		0x44
+#define SPI_SFCON		0x60
+#define SPI_SFSTAT		0x64
+#define SPI_GPOCON		0x70
+#define SPI_GPOSTAT		0x74
+#define SPI_FPGO		0x78
+#define SPI_RXREQ		0x80
+#define SPI_RXCNT	

Re: [OpenWrt-Devel] lantiq: Initial linux 4.4 support (with SPI problems)

2016-01-13 Thread Martin Blumenstingl
Hi John,

On Mon, Jan 11, 2016 at 3:25 PM, Martin Blumenstingl
 wrote:
> Here's the kernel log from the TD-W8970: https://paste.kde.org/pia7p73i9
> I have debugged it and split_tplink_kernel gets 0x2 as offset and
> 0x7A as size (which looks correct). However, when mtd_read tries to
> read the magic bytes it only gets 0x.
I found out that reverting this upstream commit makes SPI work again: [0]

Then I had a deeper look at our SPI driver - that's where I need some
help from you.
Before the mentioned commit the call-graph for each spi_transfer
looked like this:
1) ltq_spi_setup_transfer(spi, transfer)
2) ltq_spi_chipselect(spi, BITBANG_CS_ACTIVE)
3) ndelay(100)
4) ltq_spi_txrx_bufs(spi, transfer)
5) ndelay(100)
6) ltq_spi_chipselect(spi, BITBANG_CS_INACTIVE)
7) ndelay(100)

After the mentioned commit the call-graph looks like this:
1) ltq_spi_chipselect(spi, BITBANG_CS_ACTIVE)
2) ltq_spi_setup_transfer(spi, transfer)
3) ltq_spi_txrx_bufs(spi, transfer)
4) ndelay(100)
5) ltq_spi_chipselect(spi, BITBANG_CS_INACTIVE)
6) ndelay(100)
7) ...more unrelated delays...
8) ndelay(100)
9) ltq_spi_chipselect(spi, BITBANG_CS_ACTIVE)
10) ndelay(100)

Currently ltq_spi_chipselect contains the code to leave configuration
mode and to set up the "per transfer" settings (like speed and "bits
per word") whenever it's called with BITBANG_CS_ACTIVE.
Once it's called with BITBANG_CS_INACTIVE it enters configuration mode again.
I first thought that I could simply solve this by moving the "per
transfer setup" from ltq_spi_chipselect to ltq_spi_setup_transfer (you
can find the patch here: [1]), but that resulted in broken SPI (even
with the the above commit reverted):
[0.930215] m25p80 spi32766.3: unrecognized JEDEC id bytes: ff, ff, ff

Do you still remember if there is anything special that has to be
taken care of when modifying the
bits_per_word/clockmode/speed/chipselect registers?
I compared our SPI driver to the SSC (Synchronous Serial Controller)
driver from UGW 5.4 (I don't have anything newer) but I could not find
anything related.


Martin


[0] 
https://github.com/torvalds/linux/commit/0037686596832572bbca05ab168d9884d7d704c1
[1] https://paste.kde.org/pbmykthnc
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] [PATCH] scripts/metadata: Allow to select which profiles to build

2016-01-13 Thread Daniel Dickinson
Sorry, I wasn clear I guess.  I mean I'm not clear on how or if other 
targets use the 'Default' profile to select building all images for that 
target.  That is, my question is whether ar71xx is the only target for 
which the Default profile selects building all available images.


Regards,

Daniel

On 13/01/16 12:26 PM, Felix Fietkau wrote:

On 2016-01-13 18:04, Daniel Dickinson wrote:

Hi,

I'm looking at the 'Default' profiles in architectures and as far as I
can tell the only architecture that currently uses Default to mean
'build all profiles for this arch-subtarget'.  Is that correct.

I've seen other 00-default.mk profiles by on most archs this seems to be
used as a generic profile rather than as a way to select more than one.

Is that actually correct, or am I just missing how e.g. brcm63xx selects
more than than one profile in response to the default profile (I use
that example because it has both a default and generic profiles, but I
don't see how default builds more than single image).

Sometimes there are subtle differences, e.g. on ar71xx it does not
include ath10k which is only needed by a few devices.

- Felix


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


Re: [OpenWrt-Devel] Can drop LXC tar.gz patch from patchwork

2016-01-13 Thread John Crispin


On 13/01/2016 18:10, Daniel Dickinson wrote:
> As per Felix's suggestion I have implemented a detection of 'in lxc'
> logic and modified base-files and busybox sysntpd script to use that
> check to avoid actions inappropriate for an LXC guest, and to act
> normally otherwise.  The patch still needs to be tested as an LXC guest,
> but causes no misbehaviour in the non-LXC case.
> 

you can do that yourself once you created an account. it will allow you
to modify patches sent by your email addr.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] [PATCH] scripts/metadata: Allow to select which profiles to build

2016-01-13 Thread Felix Fietkau
On 2016-01-13 18:04, Daniel Dickinson wrote:
> Hi,
> 
> I'm looking at the 'Default' profiles in architectures and as far as I 
> can tell the only architecture that currently uses Default to mean 
> 'build all profiles for this arch-subtarget'.  Is that correct.
> 
> I've seen other 00-default.mk profiles by on most archs this seems to be 
> used as a generic profile rather than as a way to select more than one.
> 
> Is that actually correct, or am I just missing how e.g. brcm63xx selects 
> more than than one profile in response to the default profile (I use 
> that example because it has both a default and generic profiles, but I 
> don't see how default builds more than single image).
Sometimes there are subtle differences, e.g. on ar71xx it does not
include ath10k which is only needed by a few devices.

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


[OpenWrt-Devel] Can drop LXC tar.gz patch from patchwork

2016-01-13 Thread Daniel Dickinson
As per Felix's suggestion I have implemented a detection of 'in lxc' 
logic and modified base-files and busybox sysntpd script to use that 
check to avoid actions inappropriate for an LXC guest, and to act 
normally otherwise.  The patch still needs to be tested as an LXC guest, 
but causes no misbehaviour in the non-LXC case.


Regards,

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


Re: [OpenWrt-Devel] [PATCH] scripts/metadata: Allow to select which profiles to build

2016-01-13 Thread Daniel Dickinson

Hi,

I'm looking at the 'Default' profiles in architectures and as far as I 
can tell the only architecture that currently uses Default to mean 
'build all profiles for this arch-subtarget'.  Is that correct.


I've seen other 00-default.mk profiles by on most archs this seems to be 
used as a generic profile rather than as a way to select more than one.


Is that actually correct, or am I just missing how e.g. brcm63xx selects 
more than than one profile in response to the default profile (I use 
that example because it has both a default and generic profiles, but I 
don't see how default builds more than single image).


Any clarity on this?

Regards,

Daniel

On 11/01/16 08:35 AM, Felix Fietkau wrote:

On 2016-01-11 06:16, open...@daniel.thecshore.com wrote:

From: Daniel Dickinson 

Certain platforms have large numbers of possible images, and it can be
desirable to build neither all images nor only a single image,
therefore this patch makes selecting target profiles a menu instead of a
single choice, which allows the user to build a specific subset of all
possible images for a target.

Signed-off-by: Daniel Dickinson 
---
  scripts/metadata.pl | 32 +---
  1 file changed, 29 insertions(+), 3 deletions(-)

diff --git a/scripts/metadata.pl b/scripts/metadata.pl
index 48b1b7a..4487d26 100755
--- a/scripts/metadata.pl
+++ b/scripts/metadata.pl
@@ -275,8 +275,7 @@ EOF
  print <{conf}_$profile->{id}
bool "$profile->{name}"
depends on TARGET_$target->{conf}
+EOF
+
+   if (not (($profile->{id} eq 'Default') || 
($profile->{id} eq 'Minimal'))) {
+   print <{conf}_Default
+   default n if TARGET_$target->{conf}_Minimal
+EOF

I like the idea of allowing the user to select multiple profiles.
However, there also needs to be a clean and simple way to select a
single profile without going through the list and deselecting everything.
Also, I don't like hardcoded profile names in metadata.pl, a better
approach would be to have a flag as part of a profile that indicates
that it's not a device profile.

- Felix


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


Re: [OpenWrt-Devel] [PATCH] ar71xx: check for stuck DMA on AR724x & fix sirq storm after recovery

2016-01-13 Thread Felix Fietkau
Hi Conn,

On 2016-01-10 05:20, Conn O'Griofa wrote:
> Hi Felix,
> 
> It appears that my hunch was correct, and both are necessary. The
> following patch works 100% fine; when the dma stuck condition occurs,
> recovery now completes without any link adjust or any other output
> from the kernel log*. The tx timeout condition is also avoided thanks
> to checking for stuck dma, internet connectivity remains stable, and
> the sirq storm never triggers. It looks like your patch, with my
> additions, solves the timeout issue perfectly on my device.
> 
> One issue I'd like to bring to your attention: with my changes,
> ag71xx_fast_reset is now called for every chipset as part of the
> ag71xx_hw_enable function. Prior to this, it was only called during a
> link adjust on the ar724x chipsets, but now it's going to be called
> by the ar91xx series, too.
> 
> If ag71xx_fast_reset is not suitable for use on the ar91xx series,
> the patch is going to need changes (and isolating ag71xx_fast_reset
> to ar724x in ag71xx_hw_enable may not be sufficient for the new
> ag71xx_restart_work_func to operate properly on ar91xx chips). But if
> it is suitable for all chipsets, perhaps it would be a good idea to
> call ag71xx_fast_reset for all chipsets in ag71xx_link_adjust, too?
> 
> Conn
> 
> *When testing on my device, I added some debug to log the dma stuck
> condition, just to ensure the problem was actually being triggered
> during testing.
I did some further debugging and created some test cases to trigger DMA
stuck detection and issue a device restart.
I committed fixes in r48227 and r48228 which work quite well for me.
Please test latest trunk on your device.

Thanks,

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


[OpenWrt-Devel] The state of mwl8k

2016-01-13 Thread tapper
Hi is any router using the mwl8k driver werth bothring with? I have the 
chance to get my hands on a EA4500 thoughts?

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


[OpenWrt-Devel] [PATCH v4] [packages]: linuxptp: Add package

2016-01-13 Thread Wojciech Dubowik
Linuxptp is a user space software implementation of IEEE 1588
Precision Time Protocol standard.

v4: Don't compile on uclibc

Signed-off-by: Wojciech Dubowik 
---
 net/linuxptp/Makefile   | 50 +
 net/linuxptp/patches/001-musl-fix.patch | 12 
 2 files changed, 62 insertions(+)
 create mode 100644 net/linuxptp/Makefile
 create mode 100644 net/linuxptp/patches/001-musl-fix.patch

diff --git a/net/linuxptp/Makefile b/net/linuxptp/Makefile
new file mode 100644
index 000..2d9d3a8
--- /dev/null
+++ b/net/linuxptp/Makefile
@@ -0,0 +1,50 @@
+#
+# Copyright (C) 2015 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:=linuxptp
+PKG_VERSION:=20151118
+PKG_RELEASE:=1
+PKG_REV:=999c86f4a9da4bf4508b3a69289f58166ed18a55
+
+PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
+PKG_SOURCE_URL:=git://git.code.sf.net/p/linuxptp/code
+PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION)
+PKG_SOURCE_VERSION:=$(PKG_REV)
+PKG_SOURCE_PROTO:=git
+PKG_MD5SUM:=
+
+include $(INCLUDE_DIR)/package.mk
+
+define Package/linuxptp
+  SECTION:=net
+  CATEGORY:=Network
+  SUBMENU:=Time Synchronization
+  TITLE:=Linux Precision Time Protocol (PTP) daemon
+  URL:=http://linuxptp.sourceforge.net/
+  DEPENDS:=@!USE_UCLIBC +librt
+endef
+
+define Package/linuxptp/description
+ The PTP daemon (PTPd) implements version 2 of the Precision Time Protocol 
(PTP)
+ as defined by the IEEE 1588-2008 standard.
+ PTP was developed to provide very precise time coordination of LAN connected
+ computers.
+endef
+
+define Package/linuxptp/install
+   $(INSTALL_DIR) $(1)/usr/sbin
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/hwstamp_ctl $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/phc2sys $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/phc_ctl $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/pmc $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/ptp4l $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/timemaster $(1)/usr/sbin/
+endef
+
+$(eval $(call BuildPackage,linuxptp))
diff --git a/net/linuxptp/patches/001-musl-fix.patch 
b/net/linuxptp/patches/001-musl-fix.patch
new file mode 100644
index 000..41302c7
--- /dev/null
+++ b/net/linuxptp/patches/001-musl-fix.patch
@@ -0,0 +1,12 @@
+Index: linuxptp-20151118/raw.c
+===
+--- linuxptp-20151118.orig/raw.c   2016-01-08 13:39:56.0 +0100
 linuxptp-20151118/raw.c2016-01-13 09:16:51.951784148 +0100
+@@ -20,7 +20,6 @@
+ #include 
+ #include 
+ #include 
+-#include 
+ #include 
+ #include 
+ #include 
-- 
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] [packages] linuxptp: Add package

2016-01-13 Thread John Crispin


On 13/01/2016 12:25, Felix Fietkau wrote:
> On 2016-01-13 12:05, John Crispin wrote:
>>
>>
>> On 13/01/2016 12:03, Felix Fietkau wrote:
>>> On 2016-01-13 08:50, John Crispin wrote:


 On 13/01/2016 08:47, Wojciech Dubowik wrote:
> ++#if defined(__UCLIBC__)
> ++/* This syscall is not defined in uClibc 0.93.2 */
> ++#include 
> ++static int clock_adjtime(clockid_t id, struct timex *tx)
> ++{
> ++return syscall(__NR_clock_adjtime, id, tx);
> ++}
> ++#endif
> ++

 on ppc we are already on musl. i dont think we need to add patches for
 a libc that we do not support anymore. could you resend the patch with
 the uclibc patches removed please ?
>>> Actually... We do have one target that still relies on uClibc - and this
>>> package is not ppc specific.
>>>
>>> - Felix
>>
>> which target and does it have a ptp HW ?
> ARC770. At the moment it's virtual, not sure if we will see HW with PTP
> support. Since uClibc fixes are already there, we might as well keep
> them (assuming they work with uClibc-ng). If not, we should at least
> have a dependency on !USE_UCLIBC.
> 
> - Felix
> 

i can live with a !USE_UCLIBC dependency

@Wojciech: could you send the patch a 4th time with the dependency added
? sorry for the hassle ...


John

___
> 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] [packages] linuxptp: Add package

2016-01-13 Thread Felix Fietkau
On 2016-01-13 12:05, John Crispin wrote:
> 
> 
> On 13/01/2016 12:03, Felix Fietkau wrote:
>> On 2016-01-13 08:50, John Crispin wrote:
>>>
>>>
>>> On 13/01/2016 08:47, Wojciech Dubowik wrote:
 ++#if defined(__UCLIBC__)
 ++/* This syscall is not defined in uClibc 0.93.2 */
 ++#include 
 ++static int clock_adjtime(clockid_t id, struct timex *tx)
 ++{
 ++ return syscall(__NR_clock_adjtime, id, tx);
 ++}
 ++#endif
 ++
>>>
>>> on ppc we are already on musl. i dont think we need to add patches for
>>> a libc that we do not support anymore. could you resend the patch with
>>> the uclibc patches removed please ?
>> Actually... We do have one target that still relies on uClibc - and this
>> package is not ppc specific.
>> 
>> - Felix
> 
> which target and does it have a ptp HW ?
ARC770. At the moment it's virtual, not sure if we will see HW with PTP
support. Since uClibc fixes are already there, we might as well keep
them (assuming they work with uClibc-ng). If not, we should at least
have a dependency on !USE_UCLIBC.

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


Re: [OpenWrt-Devel] [PATCH] [packages] linuxptp: Add package

2016-01-13 Thread John Crispin


On 13/01/2016 12:03, Felix Fietkau wrote:
> On 2016-01-13 08:50, John Crispin wrote:
>>
>>
>> On 13/01/2016 08:47, Wojciech Dubowik wrote:
>>> ++#if defined(__UCLIBC__)
>>> ++/* This syscall is not defined in uClibc 0.93.2 */
>>> ++#include 
>>> ++static int clock_adjtime(clockid_t id, struct timex *tx)
>>> ++{
>>> ++  return syscall(__NR_clock_adjtime, id, tx);
>>> ++}
>>> ++#endif
>>> ++
>>
>> on ppc we are already on musl. i dont think we need to add patches for
>> a libc that we do not support anymore. could you resend the patch with
>> the uclibc patches removed please ?
> Actually... We do have one target that still relies on uClibc - and this
> package is not ppc specific.
> 
> - Felix

which target and does it have a ptp HW ?

> ___
> 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] [packages] linuxptp: Add package

2016-01-13 Thread Felix Fietkau
On 2016-01-13 08:50, John Crispin wrote:
> 
> 
> On 13/01/2016 08:47, Wojciech Dubowik wrote:
>> ++#if defined(__UCLIBC__)
>> ++/* This syscall is not defined in uClibc 0.93.2 */
>> ++#include 
>> ++static int clock_adjtime(clockid_t id, struct timex *tx)
>> ++{
>> ++   return syscall(__NR_clock_adjtime, id, tx);
>> ++}
>> ++#endif
>> ++
> 
> on ppc we are already on musl. i dont think we need to add patches for
> a libc that we do not support anymore. could you resend the patch with
> the uclibc patches removed please ?
Actually... We do have one target that still relies on uClibc - and this
package is not ppc specific.

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


Re: [OpenWrt-Devel] [PATCH] mac80211: add 'channel_list' option for channel list restriction

2016-01-13 Thread Leonardo Brondani Schenkel
On 13/01/2016 10:37, Felix Fietkau wrote:
> On 2016-01-13 10:25, Leonardo Brondani Schenkel wrote:
> The feature is already implemented (see two lines above the one you
> added here). This change is not necessary.

My apologies. It was an oversight. I actually implemented this for CC
(it was not there) and merged it to trunk but I missed that it was
implemented (slightly different) in trunk.

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


Re: [OpenWrt-Devel] [PATCH] mac80211: add 'channel_list' option for channel list restriction

2016-01-13 Thread Felix Fietkau
On 2016-01-13 10:25, Leonardo Brondani Schenkel wrote:
> # HG changeset patch
> # User Leonardo Brondani Schenkel 
> # Date 1452674412 -3600
> #  Wed Jan 13 09:40:12 2016 +0100
> # Node ID ec9c6531ce00d10f7fa0e947d65dfc1acdb09551
> # Parent  3b05804d46b9e73181278a407be5e9ac3c572941
> mac80211: add 'channel_list' option for channel list restriction
?

> This options allows restricting automatic channel scan to the provided list.
> It is equivalent to hostapd 'chanlist' parameter. Quoting hostapd.conf:
> 
> # Channel list restriction. This option allows hostapd to select one of the
> # provided channels when a channel should be automatically selected.
> # Channel list can be provided as range using hyphen ('-') or individual
> # channels can be specified by space (' ') seperated values
> # Default: all channels allowed in selected hw_mode
> #chanlist=100 104 108 112 116
> #chanlist=1 6 11-13
> 
> Signed-off-by: Leonardo Brondani Schenkel 
> 
> diff --git a/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh 
> b/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
> --- a/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
> +++ b/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
> @@ -17,6 +17,7 @@
>  drv_mac80211_init_device_config() {
>   hostapd_common_add_device_config
>  
> + config_add_string channel_list
>   config_add_string path phy 'macaddr:macaddr'
>   config_add_string hwmode
>   config_add_int beacon_int chanbw frag rts
> @@ -92,7 +93,7 @@
>   [ "$auto_channel" -gt 0 ] && channel=acs_survey
>   [ "$auto_channel" -gt 0 ] && json_get_values channel_list channels
>  
> - json_get_vars noscan ht_coex
> + json_get_vars channel_list noscan ht_coex
>   json_get_values ht_capab_list ht_capab
>  
>   ieee80211n=1
> @@ -305,6 +306,7 @@
>  ${channel:+channel=$channel}
>  ${channel_list:+chanlist=$channel_list}
>  ${noscan:+noscan=$noscan}
> +${channel_list:+chanlist=$channel_list}
The feature is already implemented (see two lines above the one you
added here). This change is not necessary.

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


Re: [OpenWrt-Devel] [PATCH 1/1] use NTP server received via DHCP

2016-01-13 Thread Amine Aouled Hamed
Apologies, I was working with an old fork of Openwrt.
another version (hopefully the last) will be sent soon.

Regards,
Amine.

On Tue, Jan 12, 2016 at 10:20 AM, Bastian Bittorf 
wrote:

> * amine ahd  [12.01.2016 10:08]:
> > ---
> >  package/utils/busybox/Makefile |  3 ++
> >  package/utils/busybox/files/sysntpd| 26 ++-
> >  package/utils/busybox/files/sysntpd.hotplug| 53
> ++
> >  3 files changed, 80 insertions(+), 2 deletions(-)
> >  create mode 100755 package/utils/busybox/files/sysntpd.hotplug
>
> also it does not apply:
>
> bastian@X301:~/software/openwrt$ curl -s
> https://patchwork.ozlabs.org/patch/566411/mbox/ | git apply --check
> error: patch failed: package/utils/busybox/Makefile:112
> error: package/utils/busybox/Makefile: patch does not apply
>
> bye, bastian
>



-- 

Amine Hamed | Software Engineer



Ocedo GmbH | Hirschstrasse 7 | 76133 Karlsruhe | Germany

Email aha...@ocedo.com




REGISTERED OFFICE: KARLSRUHE | DISTRICT COURT: MANNHEIM | REGISTER NUMBER:
HRB 717873
MANAGING DIRECTOR: MARKUS HENNIG|JAN HICHERT
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] [PATCH v3] [packages] linuxptp: Add package

2016-01-13 Thread Wojciech Dubowik
Linuxptp is a user space software implementation of IEEE 1588
Precision Time Protocol standard.

v3: Remove offending UCLIBC references

Signed-off-by: Wojciech Dubowik 
---
 net/linuxptp/Makefile   | 51 +
 net/linuxptp/patches/001-musl-fix.patch | 12 
 2 files changed, 63 insertions(+)
 create mode 100644 net/linuxptp/Makefile
 create mode 100644 net/linuxptp/patches/001-musl-fix.patch

diff --git a/net/linuxptp/Makefile b/net/linuxptp/Makefile
new file mode 100644
index 000..f0c9c9d
--- /dev/null
+++ b/net/linuxptp/Makefile
@@ -0,0 +1,51 @@
+#
+# Copyright (C) 2015 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:=linuxptp
+PKG_VERSION:=20151118
+PKG_RELEASE:=1
+PKG_REV:=999c86f4a9da4bf4508b3a69289f58166ed18a55
+
+#PKG_BUILD_DIR:=$(KERNEL_BUILD_DIR)/$(PKG_NAME)-$(BUILD_VARIANT)/$(PKG_NAME)-$(PKG_VERSION)
+PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
+PKG_SOURCE_URL:=git://git.code.sf.net/p/linuxptp/code
+PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION)
+PKG_SOURCE_VERSION:=$(PKG_REV)
+PKG_SOURCE_PROTO:=git
+PKG_MD5SUM:=
+
+include $(INCLUDE_DIR)/package.mk
+
+define Package/linuxptp
+  SECTION:=net
+  CATEGORY:=Network
+  SUBMENU:=Time Synchronization
+  TITLE:=Linux Precision Time Protocol (PTP) daemon
+  URL:=http://linuxptp.sourceforge.net/
+  DEPENDS:=+librt
+endef
+
+define Package/linuxptp/description
+ The PTP daemon (PTPd) implements version 2 of the Precision Time Protocol 
(PTP)
+ as defined by the IEEE 1588-2008 standard.
+ PTP was developed to provide very precise time coordination of LAN connected
+ computers.
+endef
+
+define Package/linuxptp/install
+   $(INSTALL_DIR) $(1)/usr/sbin
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/hwstamp_ctl $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/phc2sys $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/phc_ctl $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/pmc $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/ptp4l $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/timemaster $(1)/usr/sbin/
+endef
+
+$(eval $(call BuildPackage,linuxptp))
diff --git a/net/linuxptp/patches/001-musl-fix.patch 
b/net/linuxptp/patches/001-musl-fix.patch
new file mode 100644
index 000..41302c7
--- /dev/null
+++ b/net/linuxptp/patches/001-musl-fix.patch
@@ -0,0 +1,12 @@
+Index: linuxptp-20151118/raw.c
+===
+--- linuxptp-20151118.orig/raw.c   2016-01-08 13:39:56.0 +0100
 linuxptp-20151118/raw.c2016-01-13 09:16:51.951784148 +0100
+@@ -20,7 +20,6 @@
+ #include 
+ #include 
+ #include 
+-#include 
+ #include 
+ #include 
+ #include 
-- 
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 v2] [packages]: linuxptp: Add package

2016-01-13 Thread John Crispin


On 13/01/2016 09:00, Wojciech Dubowik wrote:
> diff --git a/net/linuxptp/patches/001-musl-fix.patch 
> b/net/linuxptp/patches/001-musl-fix.patch
> new file mode 100644
> index 000..618a958
> --- /dev/null
> +++ b/net/linuxptp/patches/001-musl-fix.patch
> @@ -0,0 +1,14 @@
> +Index: linuxptp-20150608/raw.c
> +===
> +--- linuxptp-20150608.orig/raw.c 2015-07-07 15:02:17.0 +0200
>  linuxptp-20150608/raw.c  2015-07-09 08:54:30.222883143 +0200
> +@@ -20,7 +20,9 @@
> + #include 
> + #include 
> + #include 
> ++#if defined(__UCLIBC__)
> + #include 
> ++#endif
> + #include 
> + #include 
> + #include 
> -- 1.9.1

i have to be really annoying and point out that there is still one left
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] [PATCH v2] [packages]: linuxptp: Add package

2016-01-13 Thread Wojciech Dubowik
Linuxptp is a user space software implementation of IEEE 1588
Precision Time Protocol standard.

V2: Removed uClibc patches

Signed-off-by: Wojciech Dubowik 
---
 net/linuxptp/Makefile   | 51 +
 net/linuxptp/patches/001-musl-fix.patch | 14 +
 2 files changed, 65 insertions(+)
 create mode 100644 net/linuxptp/Makefile
 create mode 100644 net/linuxptp/patches/001-musl-fix.patch

diff --git a/net/linuxptp/Makefile b/net/linuxptp/Makefile
new file mode 100644
index 000..f0c9c9d
--- /dev/null
+++ b/net/linuxptp/Makefile
@@ -0,0 +1,51 @@
+#
+# Copyright (C) 2015 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:=linuxptp
+PKG_VERSION:=20151118
+PKG_RELEASE:=1
+PKG_REV:=999c86f4a9da4bf4508b3a69289f58166ed18a55
+
+#PKG_BUILD_DIR:=$(KERNEL_BUILD_DIR)/$(PKG_NAME)-$(BUILD_VARIANT)/$(PKG_NAME)-$(PKG_VERSION)
+PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
+PKG_SOURCE_URL:=git://git.code.sf.net/p/linuxptp/code
+PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION)
+PKG_SOURCE_VERSION:=$(PKG_REV)
+PKG_SOURCE_PROTO:=git
+PKG_MD5SUM:=
+
+include $(INCLUDE_DIR)/package.mk
+
+define Package/linuxptp
+  SECTION:=net
+  CATEGORY:=Network
+  SUBMENU:=Time Synchronization
+  TITLE:=Linux Precision Time Protocol (PTP) daemon
+  URL:=http://linuxptp.sourceforge.net/
+  DEPENDS:=+librt
+endef
+
+define Package/linuxptp/description
+ The PTP daemon (PTPd) implements version 2 of the Precision Time Protocol 
(PTP)
+ as defined by the IEEE 1588-2008 standard.
+ PTP was developed to provide very precise time coordination of LAN connected
+ computers.
+endef
+
+define Package/linuxptp/install
+   $(INSTALL_DIR) $(1)/usr/sbin
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/hwstamp_ctl $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/phc2sys $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/phc_ctl $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/pmc $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/ptp4l $(1)/usr/sbin/
+   $(INSTALL_BIN) $(PKG_BUILD_DIR)/timemaster $(1)/usr/sbin/
+endef
+
+$(eval $(call BuildPackage,linuxptp))
diff --git a/net/linuxptp/patches/001-musl-fix.patch 
b/net/linuxptp/patches/001-musl-fix.patch
new file mode 100644
index 000..618a958
--- /dev/null
+++ b/net/linuxptp/patches/001-musl-fix.patch
@@ -0,0 +1,14 @@
+Index: linuxptp-20150608/raw.c
+===
+--- linuxptp-20150608.orig/raw.c   2015-07-07 15:02:17.0 +0200
 linuxptp-20150608/raw.c2015-07-09 08:54:30.222883143 +0200
+@@ -20,7 +20,9 @@
+ #include 
+ #include 
+ #include 
++#if defined(__UCLIBC__)
+ #include 
++#endif
+ #include 
+ #include 
+ #include 
-- 
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel