Re: [OpenWrt-Devel] [PATCH 1/1] GL AR150 AR300 Domino patches

2015-11-06 Thread Felix Fietkau
On 2015-11-06 08:01, alz...@gmail.com wrote: > From: alzhao > > --- > .../ar71xx/base-files/etc/uci-defaults/01_leds | 12 ++ > .../ar71xx/base-files/etc/uci-defaults/02_network | 8 ++ > target/linux/ar71xx/base-files/lib/ar71xx.sh | 9 ++ > .../ar71xx/base-files/lib/upgrade/pla

Re: [OpenWrt-Devel] uci delete doesn't match documentation

2015-11-06 Thread Yousong Zhou
On 5 November 2015 at 22:44, Karl Palsson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I'm trying to work out _a_ way of ensuring that a UCI config file > has a given section type with a given name. > > While trying to test out the various methods, I've been deleting > files from /

Re: [OpenWrt-Devel] [PATCH 1/1] GL AR150 AR300 Domino patches

2015-11-06 Thread alzhao
I can make the patch for trunk separately. But I observed that for CC1505, patches are still updated after release. Can we merge the patches to CC1505 as well. As a lot of people prefer a stable release rather than trunk. On Fri, Nov 6, 2015 at 4:54 PM, Felix Fietkau wrote: > On 2015-11-06 08:01

Re: [OpenWrt-Devel] [PATCH 1/1] GL AR150 AR300 Domino patches

2015-11-06 Thread Felix Fietkau
On 2015-11-06 11:18, alzhao wrote: > I can make the patch for trunk separately. But I observed that for > CC1505, patches are still updated after release. Can we merge the > patches to CC1505 as well. As a lot of people prefer a stable release > rather than trunk. I don't know if we're going to bac

Re: [OpenWrt-Devel] [PATCH] include/image.mk: use KERNEL_SUFFIX in Device/Build/initramfs

2015-11-06 Thread Felix Fietkau
On 2015-11-05 18:34, Alexey Brodkin wrote: > In case if we're interested in generation of non-binary images > (for example if we want images to be valid .elfs - and that's what we > want for ARC now) we have to instruct Device/Build/initramfs target to > use input file with some extension (in case

Re: [OpenWrt-Devel] [PATCH 2/2 v3] linux: add support of Synopsys ARC770-based boards

2015-11-06 Thread Jonas Gorski
Hi Alexey, On Thu, Nov 5, 2015 at 8:39 PM, Alexey Brodkin wrote: > Hi Jonas, > > On Thu, 2015-11-05 at 20:04 +0100, Jonas Gorski wrote: >> Hi Alexey, >> >> On Thu, Nov 5, 2015 at 7:14 PM, Alexey Brodkin >> wrote: >> > Hi Jonas, >> > >> > On Wed, 2015-11-04 at 20:22 +0300, Alexey Brodkin wrote: >

Re: [OpenWrt-Devel] Enable BPF JIT by default?

2015-11-06 Thread Helmut Schaa
On Thu, Nov 5, 2015 at 5:56 PM, John Crispin wrote: > On 05/11/2015 17:54, Helmut Schaa wrote: >> Since lots of architectures now support BPF JIT would it make sense to >> enable it by default for all openwrt builds? >> Any opinions on that? > > can you grab some stats so we can compare kernel siz

Re: [OpenWrt-Devel] Enable BPF JIT by default?

2015-11-06 Thread Felix Fietkau
On 2015-11-06 13:44, Helmut Schaa wrote: > On Thu, Nov 5, 2015 at 5:56 PM, John Crispin wrote: >> On 05/11/2015 17:54, Helmut Schaa wrote: >>> Since lots of architectures now support BPF JIT would it make sense to >>> enable it by default for all openwrt builds? >>> Any opinions on that? >> >> can

[OpenWrt-Devel] Netifd: are the protocol-based prefixes still needed for interface names?

2015-11-06 Thread Hannu Nyman
Netifd (or the protocol defintions) add a prefix like "br-", "6in4-", "pppoe-" etc. to names of interfaces with selected protocols and bridge interfaces. Example: 6in4-tunnel interface "sixxs" gets created in the system as "6in4-sixxs". https://dev.openwrt.org/browser/trunk/package/network/ipv6

[OpenWrt-Devel] STAGING_DIR vs. --sysroot

2015-11-06 Thread RĂ¼diger , Christoph
Hi folks, I'm wondering a bit why the OpenWrt toolchains rely on a set STAGING_DIR environment variable. I haven't found any documentation on this except "You have to set it". Examining the source tree of gcc didn't show me any STAGING_DIR occurrence. It seems to be used only in the specs file.

Re: [OpenWrt-Devel] STAGING_DIR vs. --sysroot

2015-11-06 Thread Felix Fietkau
On 2015-11-06 15:24, RĂ¼diger, Christoph wrote: > Hi folks, > > I'm wondering a bit why the OpenWrt toolchains rely on a set > STAGING_DIR environment variable. I haven't found any documentation on > this except "You have to set it". Examining the source tree of gcc > didn't show me any STAGING_DIR

[OpenWrt-Devel] [PATCH v3 1/2] include/image.mk: Introduce generic option to wrap kernel into JFFS2

2015-11-06 Thread Benjamin Berg
Some devices require the kernel to be in a JFFS2 file system. Make the support for this more generic so that it can be used by other devices. Signed-off-by: Benjamin Berg --- include/image.mk | 15 +++ target/linux/ar71xx/image/Makefile | 19 +++ 2 f

[OpenWrt-Devel] [PATCH v3 2/2] ar71xx: Add support for ZyXEL NBG6616.

2015-11-06 Thread Benjamin Berg
Signed-off-by: Benjamin Berg --- target/linux/ar71xx/base-files/etc/diag.sh | 5 +- .../etc/hotplug.d/firmware/11-ath10k-caldata | 2 + .../ar71xx/base-files/etc/uci-defaults/01_leds | 17 ++- .../ar71xx/base-files/etc/uci-defaults/02_network | 1 + target/linux/ar71xx/b

[OpenWrt-Devel] [PATCH v3 0/2] Patches to add support fo rNBG6616

2015-11-06 Thread Benjamin Berg
Hi, so here another iteration of the patches. The biggest change is to use paddjffs2 for the kernel image as suggested by Felix and to move other boards to use the same mechanism to build the kernel. Other than that, just a tiny bugfix to include usb trigger support. Benjamin ___

Re: [OpenWrt-Devel] [PATCH v3 1/2] include/image.mk: Introduce generic option to wrap kernel into JFFS2

2015-11-06 Thread Felix Fietkau
On 2015-11-06 17:25, Benjamin Berg wrote: > Some devices require the kernel to be in a JFFS2 file system. Make the > support for this more generic so that it can be used by other devices. > > Signed-off-by: Benjamin Berg > --- > include/image.mk | 15 +++ > target/l

Re: [OpenWrt-Devel] [PATCH v3 1/2] include/image.mk: Introduce generic option to wrap kernel into JFFS2

2015-11-06 Thread Benjamin Berg
On Fr, 2015-11-06 at 17:46 +0100, Felix Fietkau wrote: > On 2015-11-06 17:25, Benjamin Berg wrote: > > Some devices require the kernel to be in a JFFS2 file system. Make the > > support for this more generic so that it can be used by other devices. > > > > Signed-off-by: Benjamin Berg > > --- > >

[OpenWrt-Devel] [PATCH] ramips: minor fixes for mt7621 profiles

2015-11-06 Thread Daniel Golle
* remove references to non-existing kmod-usb3-mt7621 * ZTB WG2626 doesn't have an RTC (thanks to Piotr Dymacz!) Signed-off-by: Daniel Golle --- target/linux/ramips/mt7621/profiles/misc.mk | 2 +- target/linux/ramips/mt7621/profiles/zbt.mk | 4 +--- 2 files changed, 2 insertions(+), 4 deletion

[OpenWrt-Devel] [PATCH 0/2] imx6: Ventana: add nand squashfs+ubifs support

2015-11-06 Thread Tim Harvey
This series adds NAND ubi squqashfs+ubifs support for the Gateworks Ventana boards. Tim Harvey (2): imx6: kernel: add UBI_BLOCK support imx6: convert ventana images to squashfs+ubifs overlay target/linux/imx6/config-4.1| 2 +- target/linux/imx6/image/Makefile| 2

[OpenWrt-Devel] [PATCH 1/2] imx6: kernel: add UBI_BLOCK support

2015-11-06 Thread Tim Harvey
UBI_BLOCK support is needed for mounting squashfs over UBI Signed-off-by: Tim Harvey --- target/linux/imx6/config-4.1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/imx6/config-4.1 b/target/linux/imx6/config-4.1 index 18a26d6..52544a7 100644 --- a/target/linux/i

[OpenWrt-Devel] [PATCH 2/2] imx6: convert ventana images to squashfs+ubifs overlay

2015-11-06 Thread Tim Harvey
Replace the ventana ubi images from a single rootfs volume containing the rootfs as well as kernel+dtbs in the boot/ subdir to a multi-volume ubi containing kernel+dtbs+bootscript in 'root' ubifs volume, rootfs in 'rootfs' squasfs volume, and rootfs_data an empty ubifs volume. At the same time mov

[OpenWrt-Devel] [PATCH] CC: ramips: Backport support for ZBT WG2626

2015-11-06 Thread L. D. Pinney
Backport of r47351 Signed-off-by: L. D. Pinney --- target/linux/ramips/base-files/etc/board.d/01_leds | 5 +++ target/linux/ramips/base-files/etc/board.d/02_network | 3 +- target/linux/ramips/base-files/etc/diag.sh | 3 ++ target/linux/ramips/base-files/lib/ramips.sh

[OpenWrt-Devel] [PATCH 0/7] kirkwood: revamp Linksys EA3500 & EA4500 support

2015-11-06 Thread Claudio Leite
This patch set reworks support for the Linksys EA3500 and EA4500, integrating significant amounts of code from the WRT1900AC port. Previously these two routers were supported by flashing from the bootloader and setting new boot commands. They can now be flashed from the Linksys factory firmware an

[OpenWrt-Devel] [PATCH 1/7] kirkwood: enable squashfs-on-ubiblock support

2015-11-06 Thread Claudio Leite
Signed-off-by: Claudio Leite --- target/linux/kirkwood/Makefile| 2 +- target/linux/kirkwood/config-3.18 | 2 +- target/linux/kirkwood/config-4.3 | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/target/linux/kirkwood/Makefile b/target/linux/kirkwood/Makefile index 2fe1c

[OpenWrt-Devel] [PATCH 2/7] kirkwood: match factory partitions on EA[34]500

2015-11-06 Thread Claudio Leite
Linksys uses a dual firmware layout, where the bootloader will switch to the other stored image when one fails to boot three consecutive times. In order to make this firmware compatible with the factory images and the stock bootloader we must match this layout. Signed-off-by: Claudio Leite ---

[OpenWrt-Devel] [PATCH 3/7] kirkwood: find active Linksys root partition

2015-11-06 Thread Claudio Leite
This is imported verbatim from the mvebu WRT1900AC port. It picks up the current boot partition from the kernel command line, then renames that partition "ubi" so that it auto-mounts. Signed-off-by: Claudio Leite --- target/linux/kirkwood/config-3.18 | 1 + target/linux/kirkwo

[OpenWrt-Devel] [PATCH 4/7] kirkwood: generate factory images for Linksys EA[34]500

2015-11-06 Thread Claudio Leite
This is done with the new image generation system. It also generates a sysupgrade.tar image. These images only support squashfs-on-UBI in their present form. Signed-off-by: Claudio Leite --- target/linux/kirkwood/image/Makefile | 45 +++- 1 file changed, 39 inser

[OpenWrt-Devel] [PATCH 5/7] kirkwood: support Linksys boot counter on EA[34]500

2015-11-06 Thread Claudio Leite
This is done with existing code from the WRT1900AC port. It makes sure the "auto_recovery" bootloader option is set, and resets the s_env boot counter after a successful boot. This gives users without a serial console connection some measure of safety. Signed-off-by: Claudio Leite --- package/s

[OpenWrt-Devel] [PATCH 6/7] kirkwood: support sysupgrade on Linksys EA[34]500

2015-11-06 Thread Claudio Leite
This automatically writes to the alternate firmware partition (on Linksys's dual firmware layout) using code borrowed from the WRT1900AC port. Signed-off-by: Claudio Leite --- .../kirkwood/base-files/lib/upgrade/linksys.sh | 79 ++ .../kirkwood/base-files/lib/upgrade/plat

[OpenWrt-Devel] [PATCH 7/7] kirkwood: add diag LED on Linksys EA3500

2015-11-06 Thread Claudio Leite
Signed-off-by: Claudio Leite --- target/linux/kirkwood/base-files/etc/diag.sh | 3 +++ 1 file changed, 3 insertions(+) diff --git a/target/linux/kirkwood/base-files/etc/diag.sh b/target/linux/kirkwood/base-files/etc/diag.sh index 716e6c9..89d4655 100755 --- a/target/linux/kirkwood/base-files/et