Re: [OpenWrt-Devel] [PATCH] base-files: Use the same LED timing as before for preinit_regular.

On 29 December 2014 at 08:12, Vittorio G (VittGam) wrote: > On 26 December 2014 at 09:53, Rafał Miłecki wrote: >> >> On 26 December 2014 at 09:51, Rafał Miłecki wrote: >>> >>> On 25 December 2014 at 02:28, Vittorio G (VittGam) >>> wrote: Signed-off-by: Vittorio Gambaletta d

Re: [OpenWrt-Devel] [PATCH] base-files: Use the same LED timing as before for preinit_regular.

Il 29.12.2014 09:04 Rafał Miłecki ha scritto: 1) I think that most OpenWrt users, like me, are accustomed to see a led pattern of 200ms. I thought it was a bad flash or something else bad when I've seen that 500ms blinking... Is there any reason for that? Was 200ms ever used or documented by

[OpenWrt-Devel] Please test ep93xx with kernel 3.14

I added support for kernel 3.14 for the ep93xx target [0] in trunk, but I do not have any hardware to test this, the commit was only compile tested. If you have some hardware that is supported by the ep93xx target please build an image with kernel 3.14 and test it on your device. If this image boo

[OpenWrt-Devel] [PATCH] base-files: led input trigger error message if kernel module is not loaded

Hi, I use a custom made image (for our local wifi community) with a TL-WDR4300. Recently I disabled the config line CONFIG_PACKAGE_kmod-ledtrig-usbdev. The absence of this module causes a bootup error message: root@AP-1-203:/etc/rc.d# /etc/init.d/led start setting up led USB1 sh: write error:

[OpenWrt-Devel] [PATCH] Comgt: Add option to ignore ioctl errors

Some Huawei mobile broadband sticks utilizing the NCM protocol expose the control channel as a cdc-wdm device node instead of a virtual serial port. This device node does not support the serial port ioctls. Add command line option to not check whether ioctls are successful so that AT commands can a

[OpenWrt-Devel] Please test mpc52xx with kernel 3.14

I added support for kernel 3.14 for the mpc52xx target [0] in trunk, but I do not have any hardware to test this, the commit was only compile tested. If you have some hardware that is supported by the mpc52xx target please build an image with kernel 3.14 and test it on your device. If this image b

[OpenWrt-Devel] Please test mpc83xx with kernel 3.14

I added support for kernel 3.14 for the mpc83xx target [0] in trunk, but I do not have any hardware to test this, the commit was only compile tested. If you have some hardware that is supported by the mpc83xx target please build an image with kernel 3.14 and test it on your device. If this image b

[OpenWrt-Devel] [PATCH 2/3] e2fsprogs: package dumpe2fs, e2freefrag, filefrag, debugfs

Signed-off-by: Maxim Storchak diff --git a/package/utils/e2fsprogs/Makefile b/package/utils/e2fsprogs/Makefile index 09c4833..969f0d6 100644 --- a/package/utils/e2fsprogs/Makefile +++ b/package/utils/e2fsprogs/Makefile @@ -67,6 +67,30 @@ $(call Package/e2fsprogs) DEPENDS:= +e2fsprogs endef

[OpenWrt-Devel] [PATCH 1/3] e2fsprogs: bump release

Signed-off-by: Maxim Storchak diff --git a/package/utils/e2fsprogs/Makefile b/package/utils/e2fsprogs/Makefile index b91c957..09c4833 100644 --- a/package/utils/e2fsprogs/Makefile +++ b/package/utils/e2fsprogs/Makefile @@ -10,7 +10,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=e2fsprogs PKG_VERSION

[OpenWrt-Devel] [PATCH 3/3] e2fsprogs: symlink e2fsck to fsck.ext{2, 3, 4}, and tune2fs to findfs

Signed-off-by: Maxim Storchak diff --git a/package/utils/e2fsprogs/Makefile b/package/utils/e2fsprogs/Makefile index 969f0d6..a2ce999 100644 --- a/package/utils/e2fsprogs/Makefile +++ b/package/utils/e2fsprogs/Makefile @@ -148,6 +148,9 @@ define Package/e2fsprogs/install $(LN) mke2fs $(1)

[OpenWrt-Devel] [PATCH] feeds.conf.default: add dlan feed

Since mcs814x/dLAN-USB-Extender profile refers to some packages in this feed, we should list it here. Signed-off-by: Michael Heimpold --- feeds.conf.default |1 + 1 file changed, 1 insertion(+) diff --git a/feeds.conf.default b/feeds.conf.default index 208342c..16f07d0 100644 --- a/feeds.co

[OpenWrt-Devel] [PATCH] ar71xx: add support for the UniFi AP Outdoor Plus

Signed-off-by: Matthias Schiffer --- target/linux/ar71xx/base-files/etc/diag.sh | 3 ++ target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 ++ .../ar71xx/base-files/lib/upgrade/platform.sh | 2 + target/linux/ar71xx/image/Makefile | 3 +- .../610-MIPS-ath79-op

[OpenWrt-Devel] [PATCH] kernel: bridge: multicast: backport a few more fixes for 3.10

The following patches unfortunately didn't hit the kernel stable branches yet, therefore cherrypicking them for OpenWRT here: * bridge: fix netfilter/NF_BR_LOCAL_OUT for own, locally generated queries * bridge: multicast: enable snooping on general queries only * bridge: multicast: add sanity chec

Re: [OpenWrt-Devel] [PATCH] ar71xx: add support for the UniFi AP Outdoor Plus

Does the new kernel / ath9k address the RF Filter on this board? I came up with an old patch for this board, but whenever I changed the channel inside OpenWRT the signal would just disappear. The RF Filter has to be toggled somehow ( I assume it's a GPIO of some sort ). I am just curious on how it

Re: [OpenWrt-Devel] [PATCH] ar71xx: add support for the UniFi AP Outdoor Plus

I had read the mails regarding the issue and I've asked about it in #openwrt-devel (but didn't get an answer yet). I didn't try changing the channel though as I'm in a very noisy environment (WLAN-wise) at the moment, so I can't really do any proper testing. If it's only a GPIO issue, I could look

[OpenWrt-Devel] netifd: network reload ignores country change

I got wrong country set and couldn't use channels 12/13. So I set: wireless.radio1.country=pl however calling /etc/init.d/network reload didn't do anything. It seems netifd doesn't notice country change. -- Rafał ___ openwrt-devel mailing list openwrt-d