[OpenWrt-Devel] [PATCH, usbmode] Extend StandardEject sequence to include LUN 1

Also sending the eject command to LUN 1 is required for some D-Link devices. Signed-off-by: Benjamin Berg Signed-off-by: René van Weert --- switch.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/switch.c b/switch.c index b283561..587a2af 100644 --- a/switch.c +++ b/switch.c

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

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. > > > > S

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

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 ___

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

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

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

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

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

On Mo, 2015-11-02 at 20:49 +0100, Felix Fietkau wrote: > On 2015-11-02 20:33, Benjamin Berg wrote: > > Some devices like the NBG6616 and NBG6617 expect the kernel to be > > in a JFFS2 partition. This macro allows wrapping the kernel so that > > a normal squashfs+jffs partitio

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

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

[OpenWrt-Devel] ZyXEL NBG6616 and jffs2 kernel partition support

Hi, wasn't aware of the ongoing work to build the images in parallel, so here another respin of the patch. There is now a patch which first adds support to build a JFFS2 partition just for the kernel. The second patch is the same as before modified to use the new parallel image build system. Ben

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

Some devices like the NBG6616 and NBG6617 expect the kernel to be in a JFFS2 partition. This macro allows wrapping the kernel so that a normal squashfs+jffs partition can be used for the rest of the firmware. Signed-off-by: Benjamin Berg --- include/image.mk | 15 +++ 1 file changed

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

Signed-off-by: Benjamin Berg --- Thanks for the feedback. This revision of the patch changes the zyxel LED name to nbg6X16 for both the nbg6616 and nbg6716. I have also adapted the order in different places. Also modified is the comment about the missing factory image that should now include

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

Signed-off-by: Benjamin Berg --- target/linux/ar71xx/base-files/etc/diag.sh | 3 + .../etc/hotplug.d/firmware/11-ath10k-caldata | 2 + .../ar71xx/base-files/etc/uci-defaults/01_leds | 7 ++ .../ar71xx/base-files/etc/uci-defaults/02_network | 2 +- target/linux/ar71xx