[OpenWrt-Devel] folder for snapshot builds missing for ipq806x
Hi! Someone with the needed access rights, please make sure all buildbot targets also have their folder on downloads.openwrt.org Looks like at least ipq806x is missing and cannot upload the packages made: http://buildbot.openwrt.org:8010/builders/ipq806x/builds/17/steps/shell_11/logs/stdio Cheers Daniel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCHv2] scripts/feeds: observe -p flag for preferential feeds
John Crispin blo...@openwrt.org wrote:
On 27/05/2015 18:03, Karl Palsson wrote:
+ my $this_feed_target = lookup_target($feed, $name);
+ $this_feed_target and do {
how about just calling it $target ?
Because even though the method is lookup_target it actually returns a
feed for the target $name.
I could change the method to lookup_feed_for_target too, if that would
help.
Sincerely,
Karl Palsson___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How to track IO usage of internal flash mtd partitions?
2015-05-30 0:50 GMT+03:00 valent.turko...@gmail.com valent.turko...@gmail.com: Awesome news Sergey, will this patch be applied to latest trunk anytime soon so that I can test it? I'm not aware of any plans like that, I wouldn't hold my breath. I'm afraid you'll need to apply the patch yourself for the time being. The number of downloads showed some interest in the matter though. Can you just briefly explain how will it be possible to track erase block count once this patch is applied? Special files named erasecount appear in the sysfs directories corresponding to mtd devices, and contain (surprise) the erase count (since reboot of course). E.g. # find /sys/ -name erasecount | xargs -n 1 grep [0-9] /dev/null /sys/devices/platform/ath79-spi/spi_master/spi0/spi0.0/mtd/mtd0/erasecount:0 /sys/devices/platform/ath79-spi/spi_master/spi0/spi0.0/mtd/mtd1/erasecount:0 /sys/devices/platform/ath79-spi/spi_master/spi0/spi0.0/mtd/mtd2/erasecount:0 /sys/devices/platform/ath79-spi/spi_master/spi0/spi0.0/mtd/mtd3/erasecount:6 /sys/devices/platform/ath79-spi/spi_master/spi0/spi0.0/mtd/mtd4/erasecount:0 /sys/devices/platform/ath79-spi/spi_master/spi0/spi0.0/mtd/mtd5/erasecount:0 Best regards, -- DoubleF ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCHv2] ralink: add support for ap699ge8c2
Actually ignore this patch. After querying a bit more about the device
it seems it's not going to be released to the public in its current
form.
Sorry about the noise.
On 26 May 2015 at 08:45, Cristian Morales Vega crist...@samknows.com wrote:
I can't find any reference online. It's similar (the case looks the
same, but white, different uC) to this one:
http://twsz.com/en/product/109/409.html. TWSZ could obviously use some
help with the names.
Not sure about TWSZ plans. We got it directly from them (I wasn't
involved). But if it's not already, I guess it will appear in the wild
soon. On the worst case people may be interested if only to convert
one of our Whiteboxes into a free router ;-) (please, don't).
On 22 May 2015 at 14:49, John Crispin blo...@openwrt.org wrote:
Hi,
what board is this ? the name looks weird.
John
On 14/05/2015 15:17, Cristian Morales Vega wrote:
Signed-off-by: Cristian Morales Vega crist...@samknows.com
---
.../linux/ramips/base-files/etc/board.d/02_network | 5 +
target/linux/ramips/base-files/lib/ramips.sh | 3 +
.../ramips/base-files/lib/upgrade/platform.sh | 1 +
target/linux/ramips/dts/AP699GE8C2.dts | 112
+
target/linux/ramips/image/Makefile | 6 +-
target/linux/ramips/mt7621/profiles/ap699ge8c2.mk | 18
6 files changed, 144 insertions(+), 1 deletion(-)
create mode 100644 target/linux/ramips/dts/AP699GE8C2.dts
create mode 100644 target/linux/ramips/mt7621/profiles/ap699ge8c2.mk
diff --git a/target/linux/ramips/base-files/etc/board.d/02_network
b/target/linux/ramips/base-files/etc/board.d/02_network
index 24e1ba8..ee6aab0 100755
--- a/target/linux/ramips/base-files/etc/board.d/02_network
+++ b/target/linux/ramips/base-files/etc/board.d/02_network
@@ -116,6 +116,7 @@ ramips_setup_interfaces()
;;
3g-6200n | \
+ ap699ge8c2 | \
ai-br100 | \
dir-610-a1 | \
dir-300-b7 | \
@@ -268,6 +269,10 @@ ramips_setup_macs()
local wan_mac=
case $board in
+ ap699ge8c2)
+ wan_mac=$(mtd_get_mac_binary factory 57350)
+ ;;
+
br-6475nd)
lan_mac=$(cat /sys/class/net/eth0/address)
wan_mac=$(mtd_get_mac_binary devdata 7)
diff --git a/target/linux/ramips/base-files/lib/ramips.sh
b/target/linux/ramips/base-files/lib/ramips.sh
index 616f4a1..c1b7898 100755
--- a/target/linux/ramips/base-files/lib/ramips.sh
+++ b/target/linux/ramips/base-files/lib/ramips.sh
@@ -397,6 +397,9 @@ ramips_board_detect() {
*Mediatek MT7628AN evaluation board)
name=mt7628
;;
+ *TWSZ AP699GE8C2)
+ name=ap699ge8c2
+ ;;
*)
name=generic
;;
diff --git a/target/linux/ramips/base-files/lib/upgrade/platform.sh
b/target/linux/ramips/base-files/lib/upgrade/platform.sh
index 17b456b..b79cca8 100755
--- a/target/linux/ramips/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ramips/base-files/lib/upgrade/platform.sh
@@ -25,6 +25,7 @@ platform_check_image() {
all0256n | \
all5002 | \
all5003 | \
+ ap699ge8c2 | \
ar725w | \
asl26555 | \
awapn2403 | \
diff --git a/target/linux/ramips/dts/AP699GE8C2.dts
b/target/linux/ramips/dts/AP699GE8C2.dts
new file mode 100644
index 000..7157962
--- /dev/null
+++ b/target/linux/ramips/dts/AP699GE8C2.dts
@@ -0,0 +1,112 @@
+/dts-v1/;
+
+/include/ mt7621.dtsi
+
+/ {
+ compatible = mediatek,mt7621-eval-board, mediatek,mt7621-soc;
+ model = TWSZ AP699GE8C2;
+
+ memory@0 {
+ device_type = memory;
+ reg = 0x0 0x400;
+ };
+
+ chosen {
+ bootargs = console=ttyS0,57600;
+ };
+
+ palmbus@1E00 {
+ spi@b00 {
+ status = okay;
+
+ m25p80@0 {
+ #address-cells = 1;
+ #size-cells = 1;
+ compatible = mx25l6405d;
+ reg = 0 0;
+ linux,modalias = m25p80;
+ spi-max-frequency = 1000;
+
+ partition@0 {
+ label = u-boot;
+ reg = 0x0 0x3;
+ read-only;
+ };
+
+ partition@3 {
+ label = u-boot-env;
+ reg = 0x3 0x1;
+ read-only;
+ };
+
+ factory: partition@4 {
+ label = factory;
+ reg = 0x4 0x1;
+
Re: [OpenWrt-Devel] [PATCH] odhcp6c: script: only call firewall, if installed
Is that okay with you as well https://dev.openwrt.org/changeset/45867 ? Cheers, Steven ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] odhcp6c: script: only call firewall, if installed
* Steven Barth cy...@openwrt.org [01.06.2015 10:46]: Is that okay with you as well https://dev.openwrt.org/changeset/45867 ? it's ok for me, but IMHO not the proper way, because you are hiding errors, if there are any... bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH RFC] brcmfmac: register wiphy(s) during module_init
On 1 June 2015 at 00:08, Rafał Miłecki zaj...@gmail.com wrote: @@ -440,6 +441,7 @@ static void brcmf_fw_request_nvram_done(const struct firmware *fw, void *ctx) } fwctx-done(fwctx-dev, fwctx-code, nvram, nvram_length); + complete(fwctx-completion); kfree(fwctx); return; Hey Rafał, it's unsafe to call complete and free the struct right after. Do it smarter. ___ 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 compex wpj531
tftpboot 0x8050 openwrt-ar71xx-generic-wpj531-16M-squashfs-sysupgrade.bin
erase 0x9f03 +$filesize
erase 0x9f68 +1
cp.b $fileaddr 0x9f03 $filesize
---
v2:
fix indentation with spaces
refresh patch
Signed-off-by: Christian Mehlis christ...@m3hlis.de
---
target/linux/ar71xx/base-files/etc/diag.sh | 3 +
.../ar71xx/base-files/etc/uci-defaults/02_network | 4 +
target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 +
.../ar71xx/base-files/lib/upgrade/platform.sh | 1 +
target/linux/ar71xx/config-3.18| 1 +
.../ar71xx/files/arch/mips/ath79/mach-wpj531.c | 136 +
target/linux/ar71xx/generic/profiles/compex.mk | 10 ++
target/linux/ar71xx/image/Makefile | 3 +
.../610-MIPS-ath79-openwrt-machines.patch | 24 +++-
9 files changed, 179 insertions(+), 6 deletions(-)
create mode 100644 target/linux/ar71xx/files/arch/mips/ath79/mach-wpj531.c
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
index 0553251..d64a5be 100644
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -308,6 +308,9 @@ get_status_led() {
wpj344)
status_led=wpj344:green:status
;;
+ wpj531)
+ status_led=wpj531:green:sig3
+ ;;
wpj558)
status_led=wpj558:green:sig3
;;
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
index f5c6865..5f0d302 100644
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
@@ -368,6 +368,10 @@ wpj344)
ucidef_add_switch_vlan switch0 2 0t 2
;;
+wpj531)
+ ucidef_set_interfaces_lan_wan eth0 eth1
+ ;;
+
wpj558)
ucidef_set_interfaces_lan_wan eth0.1 eth0.2
ucidef_add_switch switch0 1 1
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index d5dd561..bf18bb7 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -813,6 +813,9 @@ ar71xx_board_detect() {
*WPJ344)
name=wpj344
;;
+ *WPJ531)
+ name=wpj531
+ ;;
*WPJ558)
name=wpj558
;;
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
index 3dbd91c..ade47fb 100755
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -229,6 +229,7 @@ platform_check_image() {
rocket-m-xw | \
nanostation-m-xw | \
rw2458n | \
+ wpj531 | \
wndap360 | \
wpj344 | \
wzr-hp-g300nh2 | \
diff --git a/target/linux/ar71xx/config-3.18 b/target/linux/ar71xx/config-3.18
index 543b77e..9a7ed7f 100644
--- a/target/linux/ar71xx/config-3.18
+++ b/target/linux/ar71xx/config-3.18
@@ -139,6 +139,7 @@ CONFIG_ATH79_MACH_WNR2200=y
CONFIG_ATH79_MACH_WP543=y
CONFIG_ATH79_MACH_WPE72=y
CONFIG_ATH79_MACH_WPJ344=y
+CONFIG_ATH79_MACH_WPJ531=y
CONFIG_ATH79_MACH_WPJ558=y
CONFIG_ATH79_MACH_WRT160NL=y
CONFIG_ATH79_MACH_WRT400N=y
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-wpj531.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-wpj531.c
new file mode 100644
index 000..bc13d70
--- /dev/null
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-wpj531.c
@@ -0,0 +1,136 @@
+/*
+ * Compex WPJ531 board support
+ *
+ * Copyright (c) 2012 Qualcomm Atheros
+ * Copyright (c) 2012 Gabor Juhos juh...@openwrt.org
+ *
+ * Permission to use, copy, modify, and/or distribute this software for any
+ * purpose with or without fee is hereby granted, provided that the above
+ * copyright notice and this permission notice appear in all copies.
+ *
+ * THE SOFTWARE IS PROVIDED AS IS AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+ * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+ * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+ * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+ * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ *
+ */
+
+#include linux/irq.h
+#include linux/platform_device.h
+#include linux/ar8216_platform.h
+
+#include asm/mach-ath79/ar71xx_regs.h
+
+#include pci.h
+#include common.h
+#include dev-ap9x-pci.h
+#include dev-gpio-buttons.h
+#include dev-eth.h
+#include dev-leds-gpio.h
+#include dev-m25p80.h
+#include dev-usb.h
+#include dev-wmac.h
+#include machtypes.h
+
+#define WPJ531_GPIO_LED_SIG114
+#define WPJ531_GPIO_LED_SIG215
Re: [OpenWrt-Devel] [PATCH 1/2] ipq806x: move stmmac support in the kernel binary
On 30/05/2015 10:51, Jonas Gorski wrote: Hi, On Sat, May 30, 2015 at 3:11 AM, Mathieu Olivari math...@codeaurora.org wrote: Ethernet GMAC is built-in the SoC, so there is no need to enable it as a module. We'll just assume we need it. That's what is done for other platform where this driver is used so it'll make things more consistent. ... @@ -366,6 +368,10 @@ CONFIG_SPI_MASTER=y CONFIG_SPI_QUP=y CONFIG_SPMI=y CONFIG_SPMI_MSM_PMIC_ARB=y +# CONFIG_STMMAC_DA is not set The kmod version had this enabled - is this change intentional? Jonas config STMMAC_DA bool STMMAC DMA arbitration scheme default n ---help--- Selecting this option, rx has priority over Tx (only for Giga Ethernet device). By default, the DMA arbitration scheme is based on Round-robin (rx:tx priority is 1:1). to me this option sounds like it should be off. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info
Hi Aleksander, On Wed, May 27, 2015 at 9:20 PM, Aleksander Wałęski olewa...@gmail.com wrote: add --enable-debug-prints=err to ltq-vdsl-app and change enable-debug-prints to err in ltq-vdsl-vr9. ... Additionally, I added --disable-dsl-ceoc to ltq-vdsl-app since CEOC is disabled in API by default anyway. Thanks for the explanation. Here's the updated patch (I didn't have time to test if myself yet though): [0] Again, can someone with ADSL line test what parameters vdsl_cpe_control actually needs to operate with newest driver and firmware version (from W9980)? I can test it this weekend on an Annex B ADSL connection. So I will test with firmware 1e472dad0eda88281af7c00cd3f49fcc29d4fa83 or 186b5406e6511c97d997b48f5e0ec5ad3f62600d (see [1]). Regards, Martin [0] https://gist.github.com/xdarklight/2986587133d97892a4b3 [1] https://xdarklight.github.io/lantiq-xdsl-firmware-info/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx: How to integrate UniFi AP Outdoor Plus HSR?
Hi Kirill, An Unifi specific user space daemon listens to scan and channel change events via netlink (will check next weekend if channel change is broadcasted reliably) and tune the filter via sysfs interface accordingly like hsr.c tried. I like this idea because in this case it'll be much easier to correct problems or add changes. I cannot get events for userspace triggered channel changes from nl80211, there seems no way to realize my userspace daemon idea other than by ugly polling. So your driver patch is clearly the way to go. I'll test with chaos calmer but I have no doubt that it will work. Care to push it for inclusion? PS: I've started working on the wiki page http://wiki.openwrt.org/toh/ubiquiti/unifi_outdoorplus that I hope to move to supported soon ;-) I have a couple photos of pcb (one with annotated serial port), can send them if you need. Please, do so or just include them into the wiki page. Stefan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx: How to integrate UniFi AP Outdoor Plus HSR?
On 2015-05-27 22:48, Stefan Rompf wrote: Hi Kirill, So I made a patch for atheros driver and it works. A signal level on different frequencies is more or less equal and seems adequate (about -30 dbm if a client within a meter from ap). so you reverse engineered the timer values, the response format and the 's' command I had planned looking at next weekend. Very cool work! Now that talking to the HSR seems mostly solved, this makes me think about OpenWrt integration. Currently I see two possibities: Integration into the kernel driver like your latest patch does. Caveat: The build process seems to assume that all routers in the ar71xx/generic target share the same set of kernel modules. So patching and compiling yourself is no problem, but a working image on downloads.openwrt.org is not feasible as every router would get the HSR driver. Correct me if I am wrong. Or making ath9k expose the gpio and driving from user space. A generic patch for ath9k to register its gpio pins via the standard gpio subsystem. This should go upstream to the kernel and may prove usable for other access points to. An Unifi specific user space daemon listens to scan and channel change events via netlink (will check next weekend if channel change is broadcasted reliably) and tune the filter via sysfs interface accordingly like hsr.c tried. Caveat: Changing ath9k driver is possibly stuff for Designated Driver. May be the user space component can fall back to bit banging for Chaos Calmer. What do you think? What do OpenWrt core developers think? I'd prefer exposing gpio and driving from userspace. I think deferring this to user space might mess up timings during fast active scans. I'd prefer to have a callback in ath9k_platform.h that allows the platform code to provide a hook which implements this. That way the changes to ath9k stay very small, and the code is still quite simple. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info
Thanks for answer. I cannot unfortunately test new patch right away, because I sort of put this device in production but if it is only compilation flags that changed that I am sure it works. I suspected some kind of memory leak, because driver control process is quite heavy on memory but it does not seem to grow any larger than about 7MB (4 days uptime, steady size for at least 2 days). As for firmware: you got me interested when you mentioned Annex B. I was sure that W9980 was multi-annex and that its firmware should support this, but I was wrong. TD-W9980B seems to be made to address this. There isn't very much information on it on TP-LINK website, but I was able to google it http://www.tplink.com/be/products/details/?model=TD-W9980B (Belgian section, but website is in English). There is firmware update available for it, but strangely, only on German website http://www.tp-link.de/support/download/?model=TD-W9980Bversion=V1 Extraction procedure is exactly the same as for regular TD-W9980. Details of firmware file inside: filename: xcpe_573E16_571502_ISDN.bin version: 5.7.3.E.1.6-5.7.1.5.0.2 sha1sum: 83c2b3d7e980d4f20e85ba3e9d6f557752006ec9 filesize: 904516 Firmware1: PLATFORM: 5 PLATFORM_STR: VRX200 APPLICATION_TYPE: 6 APPLICATION_TYPE_STR: VDSL over IDSN VERSION_STR: 7.3.E RELEASE_STATUS: 1 RELEASE_STATUS_STR: Pre-Release Firmware2: PLATFORM: 5 PLATFORM_STR: VRX200 APPLICATION_TYPE: 2 APPLICATION_TYPE_STR: ADSL Annex B VERSION_STR: 7.1.5 RELEASE_STATUS: 0 RELEASE_STATUS_STR: Release Difference between this and 186b5406e6511c97d997b48f5e0ec5ad3f62600d seem to be Vectoring support for VDSL (ADSL firmware version number is the same). I was expecting only Annex difference, but this firmware may be specifically tweaked for Germany (# for DT/Germany market in vdsl.scr). I guess ADSL over ISDN is not very popular elsewhere. On Mon, Jun 1, 2015 at 11:32 PM, Martin Blumenstingl martin.blumensti...@googlemail.com wrote: Hi Aleksander, On Wed, May 27, 2015 at 9:20 PM, Aleksander Wałęski olewa...@gmail.com wrote: add --enable-debug-prints=err to ltq-vdsl-app and change enable-debug-prints to err in ltq-vdsl-vr9. ... Additionally, I added --disable-dsl-ceoc to ltq-vdsl-app since CEOC is disabled in API by default anyway. Thanks for the explanation. Here's the updated patch (I didn't have time to test if myself yet though): [0] Again, can someone with ADSL line test what parameters vdsl_cpe_control actually needs to operate with newest driver and firmware version (from W9980)? I can test it this weekend on an Annex B ADSL connection. So I will test with firmware 1e472dad0eda88281af7c00cd3f49fcc29d4fa83 or 186b5406e6511c97d997b48f5e0ec5ad3f62600d (see [1]). Regards, Martin [0] https://gist.github.com/xdarklight/2986587133d97892a4b3 [1] https://xdarklight.github.io/lantiq-xdsl-firmware-info/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
