Re: [LEDE-DEV] [RFC 1/2] zynq: convert to new image build code

On 29/07/2016 12:01 AM, Jo-Philipp Wich wrote: Convert the Zynq target to use the new image build code in order to fix broken image generation after 9945a1dca5bb6bc522393f7583baf3a64df6ce11 changed the handling of CPIO images. Can you check if you still have the build issue if you enabled the

Re: [LEDE-DEV] [RFC 0/2] zynq: rework image build code

On 29/07/2016 12:01 AM, Jo-Philipp Wich wrote: Since 9945a1dca5bb6bc522393f7583baf3a64df6ce11 "build: remove cpio.gz and tar.gz from regular filesystem types" the Zynq target is failing to generate images on the build server and aborts with the following error: mkimage: Can't open

Re: [LEDE-DEV] [RFC 2/2] zynq: fix maintainer email address

On 29/07/2016 12:01 AM, Jo-Philipp Wich wrote: Signed-off-by: Jo-Philipp Wich --- target/linux/zynq/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/zynq/Makefile b/target/linux/zynq/Makefile index a84f968..47b678d 100644 ---

[LEDE-DEV] [RFC 2/2] zynq: fix maintainer email address

Signed-off-by: Jo-Philipp Wich --- target/linux/zynq/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/zynq/Makefile b/target/linux/zynq/Makefile index a84f968..47b678d 100644 --- a/target/linux/zynq/Makefile +++ b/target/linux/zynq/Makefile

[LEDE-DEV] [RFC 0/2] zynq: rework image build code

Since 9945a1dca5bb6bc522393f7583baf3a64df6ce11 "build: remove cpio.gz and tar.gz from regular filesystem types" the Zynq target is failing to generate images on the build server and aborts with the following error: mkimage: Can't open .../zynq-zc702-rootfs.cpio.gz: No such file or directory

[LEDE-DEV] [RFC 1/2] zynq: convert to new image build code

Convert the Zynq target to use the new image build code in order to fix broken image generation after 9945a1dca5bb6bc522393f7583baf3a64df6ce11 changed the handling of CPIO images. Also remove the misapplied ubifs feature flag since the image generation is not using UBIFS for building FIT images.

Re: [LEDE-DEV] [PATCH 1/4] bugcheck: Add tools to poll for and report certain bugs.

On 07/27/2016 10:13 PM, John Crispin wrote: On 22/07/2016 01:52, gree...@candelatech.com wrote: From: Ben Greear This first release is all about checking for ath10k firmware crashes. Could be extended later for other modules/bugs/etc. the description could be

Re: [LEDE-DEV] [PATCH] ramips: Improve Archer C20i support

Hi Piotr, here we go. I've just sent in a PATCH v2 with the board name as the LED's name. Additionally I've create a patch for the C50 - is there any reason the LEDs of the C50 aren't renamed (yet)? Best regards, P. Wassi > Hello Paul, > > Please use board name instead of manufacturer name

[LEDE-DEV] [PATCH] ramips: Rename TP-Link Archer C50 LEDs

From: P.Wassi Rename LEDs in TP-Link Archer C50 from [manufacturer name] to [board name] ("tp-link" -> "c50") Signed-off-by: P.Wassi --- Change done according to information in https://lists.infradead.org/pipermail/lede-dev/2016-July/002050.html

Re: [LEDE-DEV] [PATCH] ramips: Improve Archer C20i support

Hello Paul, Please use board name instead of manufacturer name for LEDs as it's done in (almost, C50 should be fixed) all other DTS under ramips target. You should also provide full name in the SoB line. --- Cheers, Piotr 2016-07-28 12:10 GMT+02:00 : > From: P.Wassi

[LEDE-DEV] [PATCH] ramips: Improve Archer C20i support

From: P.Wassi Improve / finalise TP-Link Archer C20i support. Signed-off-by: P.Wassi --- This patch adds proper LED and Button support and sets up a correct switch configuration. The only missing thing (which is likely to never be fixed) is the 5GHz phy

Re: [LEDE-DEV] [PATCH] dropbear: Fix append_port in IPv6 case (v2)

On Thu, 2016-07-28 at 07:07 +0200, John Crispin wrote: > > On 09/07/2016 23:55, Laurent GUERBY wrote: > > The new IPPort parameter allows to pass unchanged parameters to dropbear, > > dropbear uses -p [ip6]:port for IPv6 and this was not supported with > > existing scripts. > > > > Fix