Re: [OpenWrt-Devel] SDK vs. Toolchain+

2016-01-06 Thread Daniel Dickinson 

Hi Felix,

Thank you for this!  I will give it a whirl either before I head of to 
dreamland or tomorrow morning.


Regards,

Daniel

On 06/01/16 01:39 PM, Felix Fietkau wrote:

On 2016-01-06 17:52, Daniel Dickinson wrote:

Hi,

On 06/01/16 05:24 AM, Bastian Bittorf wrote:
  > * Daniel Dickinson  [06.01.2016 11:11]:
  >> Not sure where you got those numbers.  Did you also post the exact
  >> hardware and software configuration, and testing methodology, and how
  >> you did the timing and what numbers 140 is (real command to done
  >
  > check this thread:
  >
https://lists.openwrt.org/pipermail/openwrt-devel/2015-December/037775.html
  >
https://lists.openwrt.org/pipermail/openwrt-devel/2015-December/037856.html

Obviously your idea of cheap, fast hardware is based on the assumption
that one is working on OpenWrt for pay rather than hobby. You're talking
about at least $1200-1600 CAD which is a lot of money these parts, for
the type of hardware you're talking about.

When I did have a job that involved work on openwrt (which I'm not
entirely sure was worth it, for all that I got a couple gigs it wasn't
with open source-minded companies and for that and other reasons was
more frustrating than rewarding, for the most part, given that for
openwrt was something of personal interest and I found the proprietary
business interested tainted it for me, they say never mix business with
pleasure, and for good reason).  I did buy better hardware, but that is
now only decent, not the class of hardware you're talking about in your
email (and while good, wasn't real server class, ever). At the moment
OpenWrt is a hobby for me, so shelling out that kind of money, and
finding a place for such hardware, isn't an option.

You're numbers are pretty bogus for the typical openwrt community
member, although they ought to be importance to those who can justify
that kind of investment as a business expense.

So the work on improving build speed, based on Felix's suggestion is
still definitely something I think is worthwhile for the kind of
situation I am interested in.

So I went ahead and implemented that. Here are the improvements when
there are no kernel config changes (tested on ramips mt7621, where it
already uses the new image building code for everything):

target/compile: 12s -> 8s
target/install: 68s -> 16s

- Felix


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] swconfig: support setting SWITCH_TYPE_LINK attributes

2016-01-06 Thread Rafał Miłecki 
On 30 December 2015 at 12:10, Rafał Miłecki  wrote:
> Supported syntax is inspired by ethtool. Example usage:
> swconfig dev switch0 port 2 set link "duplex half speed 100 autoneg off"

Any comments to this usage/syntax? It doesn't look too nice (this long
quoted string as a value), but swconfig is strongly focused on simple
values. Making swconfig accept something like:
swconfig dev switch0 port 2 set link duplex half speed 100 autoneg off
would require big rewrite of handling arguments in main function.

Moreover swconfig uses magic mapping of UCI options into swconfig
attributes. Thanks to this - with proposed patch - I can simply use:
network.@switch_port[0]=switch_port
network.@switch_port[0].device='switch0'
network.@switch_port[0].port='3'
network.@switch_port[0].link='duplex full speed 10 autoneg on'
and it works without any extra changes.

Making swconfig understand more friendly options, e.g.
network.@switch_port[0].link_duplex
network.@switch_port[0].link_speed
network.@switch_port[0].link_autoneg
would require big changes to swlib_apply_from_uci and swlib_map_settings.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 4/4] a71xx: add support for TP-Link RE450

2016-01-06 Thread Tal Keren 
Add full support for TP-Link RE450.
The wireless SoC is similiar to Archer C7: QCA9558 + QCA9880 (pci).
The ethernet interface is AR8035, but the mdio is connected to the gpio and
the chipset builtin mdio bus isn't used, which is unique (and weird), so the
kernel gpio mdio module is used.
The two ethernet leds are connected to the GPIO, so they are both configured,
one to indicate link status and the other to indicate data transfer.

The generation of the image was added to the image Makefile.
The return value of tplink-safeloader is not ignored anymore (to fail on error)

The result factory image is flashable from the stock web ui.

Signed-off-by: Tal Keren 
---
 target/linux/ar71xx/base-files/etc/board.d/01_leds |   9 +
 .../linux/ar71xx/base-files/etc/board.d/02_network |   1 +
 target/linux/ar71xx/base-files/etc/diag.sh |   3 +
 .../etc/hotplug.d/firmware/11-ath10k-caldata   |   4 +
 target/linux/ar71xx/base-files/lib/ar71xx.sh   |   3 +
 .../ar71xx/base-files/lib/upgrade/platform.sh  |   1 +
 target/linux/ar71xx/config-4.1 |   3 +
 .../ar71xx/files/arch/mips/ath79/Kconfig.openwrt   |  10 ++
 target/linux/ar71xx/files/arch/mips/ath79/Makefile |   1 +
 .../ar71xx/files/arch/mips/ath79/mach-re450.c  | 189 +
 .../linux/ar71xx/files/arch/mips/ath79/machtypes.h |   1 +
 target/linux/ar71xx/generic/profiles/tp-link.mk|  11 ++
 target/linux/ar71xx/image/Makefile |  46 -
 target/linux/ar71xx/mikrotik/config-default|   1 +
 target/linux/ar71xx/nand/config-default|   1 +
 15 files changed, 279 insertions(+), 5 deletions(-)
 create mode 100755 target/linux/ar71xx/files/arch/mips/ath79/mach-re450.c

diff --git a/target/linux/ar71xx/base-files/etc/board.d/01_leds 
b/target/linux/ar71xx/base-files/etc/board.d/01_leds
index cfb42a5..88d1a9c 100755
--- a/target/linux/ar71xx/base-files/etc/board.d/01_leds
+++ b/target/linux/ar71xx/base-files/etc/board.d/01_leds
@@ -398,6 +398,15 @@ qihoo-c301)
ucidef_set_led_wlan "wlan2g" "WLAN2G" "qihoo:red:status" "phy1tpt"
;;
 
+re450)
+   ucidef_set_led_netdev "lan_data" "LAN Data" "tp-link:green:lan_data" 
"eth0" "tx rx"
+   ucidef_set_led_netdev "lan_link" "LAN Link" "tp-link:green:lan_link" 
"eth0" "link"
+   ucidef_set_led_default "wps" "WPS" "tp-link:blue:wps" "0"
+   ucidef_set_led_default "wps_error" "WPS Error" "tp-link:red:wps" "0"
+   ucidef_set_led_wlan "wlan2g" "WLAN 2.4 GHz" "tp-link:blue:wlan2g" 
"phy1tpt"
+   ucidef_set_led_wlan "wlan5g" "WLAN 5 GHz" "tp-link:blue:wlan5g" 
"phy0tpt"
+   ;;
+
 smart-300)
ucidef_set_led_netdev "wan" "WAN" "nc-link:green:wan" "eth0"
ucidef_set_led_switch "lan1" "LAN1" "nc-link:green:lan1" "switch0" 
"0x04"
diff --git a/target/linux/ar71xx/base-files/etc/board.d/02_network 
b/target/linux/ar71xx/base-files/etc/board.d/02_network
index 6b6c6a4..8c16c53 100755
--- a/target/linux/ar71xx/base-files/etc/board.d/02_network
+++ b/target/linux/ar71xx/base-files/etc/board.d/02_network
@@ -340,6 +340,7 @@ rb-912uag-2hpnd |\
 rb-912uag-5hpnd |\
 rb-sxt2n |\
 rb-sxt5n |\
+re450 |\
 rocket-m-xw |\
 tl-mr10u |\
 tl-mr11u |\
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh 
b/target/linux/ar71xx/base-files/etc/diag.sh
index 13a0a98..077a6a9 100644
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -245,6 +245,9 @@ get_status_led() {
rb-sxt5n)
status_led="rb:green:power"
;;
+   re450)
+   status_led="tp-link:blue:system"
+   ;;
routerstation | routerstation-pro)
status_led="ubnt:green:rf"
;;
diff --git 
a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata 
b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 74c3417..88eb10a 100644
--- a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -75,6 +75,10 @@ case "$FIRMWARE" in
ath10kcal_extract "ART" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat 
/sys/class/net/eth0/address) +16)
;;
+   re450)
+   ath10kcal_extract "art" 20480 2116
+   ath10kcal_patch_mac $(macaddr_add $(cat 
/sys/class/net/eth0/address) -2)
+   ;;
esac
;;
 "ath10k/cal-pci-:01:00.0.bin")
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh 
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index 678482e..5853633 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -644,6 +644,9 @@ ar71xx_board_detect() {
*"Qihoo 360 C301")
name="qihoo-c301"
;;
+   *"RE450")
+   name="re450"
+   ;;
*"RouterBOARD 411/A/AH")

[OpenWrt-Devel] [PATCH 2/4] firmware-utils: add support for TP-Link RE450 for tplink-safeload

2016-01-06 Thread Tal Keren 
Change tplink-safeloader to make it simpler to support new devices.
This design seems to fit for all the devices seen so far (CPE510/RE450/Archer
C2600 and similiar devices).
Add check for partition size when creating factory image.

Add the firmware layout of RE450. The firmware layout is different from the
stock layout, since the stock layout didn't have enough space for the kernel.
512KB were moved from the file system to the kerenl partition.
This will work with the OEM firmware since it uses the partition table
specified in the new firmware when flashing it.

Signed-off-by: Tal Keren 
---
 tools/firmware-utils/src/tplink-safeloader.c | 290 ++-
 1 file changed, 195 insertions(+), 95 deletions(-)

diff --git a/tools/firmware-utils/src/tplink-safeloader.c 
b/tools/firmware-utils/src/tplink-safeloader.c
index 77a894b..fb7401f 100644
--- a/tools/firmware-utils/src/tplink-safeloader.c
+++ b/tools/firmware-utils/src/tplink-safeloader.c
@@ -27,8 +27,7 @@
 /*
tplink-safeloader
 
-   Image generation tool for the TP-LINK SafeLoader as seen on
-   TP-LINK Pharos devices (CPE210/220/510/520)
+   Image generation tool for the TP-LINK SafeLoader
 */
 
 
@@ -53,6 +52,8 @@
 #define ALIGN(x,a) ({ typeof(a) __a = (a); (((x) + __a - 1) & ~(__a - 1)); })
 
 
+#define MAX_PARTITIONS 32
+
 /** An image partition table entry */
 struct image_partition_entry {
const char *name;
@@ -67,6 +68,16 @@ struct flash_partition_entry {
uint32_t size;
 };
 
+/** Information requried to build the firmware */
+struct firmware_info {
+   const char *id;
+   const struct flash_partition_entry flash_partitions[MAX_PARTITIONS+1];
+   const char *vendor;
+   const char *support_list;
+   const char *first_sysupgrade_partition;
+   const char *last_sysupgrade_partition;
+};
+
 
 /** The content of the soft-version structure */
 struct __attribute__((__packed__)) soft_version {
@@ -102,45 +113,91 @@ static const uint8_t md5_salt[16] = {
 };
 
 
-/** Vendor information for CPE210/220/510/520 */
-static const char cpe510_vendor[] = "CPE510(TP-LINK|UN|N300-5):1.0\r\n";
-
-
-/**
-The flash partition table for CPE210/220/510/520;
-it is the same as the one used by the stock images.
-*/
-static const struct flash_partition_entry cpe510_partitions[] = {
-   {"fs-uboot", 0x0, 0x2},
-   {"partition-table", 0x2, 0x02000},
-   {"default-mac", 0x3, 0x00020},
-   {"product-info", 0x31100, 0x00100},
-   {"signature", 0x32000, 0x00400},
-   {"os-image", 0x4, 0x17},
-   {"soft-version", 0x1b, 0x00100},
-   {"support-list", 0x1b1000, 0x00400},
-   {"file-system", 0x1c, 0x60},
-   {"user-config", 0x7c, 0x1},
-   {"default-config", 0x7d, 0x1},
-   {"log", 0x7e, 0x1},
-   {"radio", 0x7f, 0x1},
-   {NULL, 0, 0}
+static struct firmware_info boards[] = {
+   {
+   .id = "CPE510",
+
+   /**
+  The flash partition table for CPE210/220/510/520;
+  it is the same as the one used by the stock images.
+   */
+   .flash_partitions = {
+   {"fs-uboot", 0x0, 0x2},
+   {"partition-table", 0x2, 0x02000},
+   {"default-mac", 0x3, 0x00020},
+   {"product-info", 0x31100, 0x00100},
+   {"signature", 0x32000, 0x00400},
+   {"os-image", 0x4, 0x17},
+   {"soft-version", 0x1b, 0x00100},
+   {"support-list", 0x1b1000, 0x00400},
+   {"file-system", 0x1c, 0x60},
+   {"user-config", 0x7c, 0x1},
+   {"default-config", 0x7d, 0x1},
+   {"log", 0x7e, 0x1},
+   {"radio", 0x7f, 0x1},
+   {NULL, 0, 0}
+   },
+
+   /** Vendor information for CPE210/220/510/520 */
+   .vendor = "CPE510(TP-LINK|UN|N300-5):1.0\r\n",
+
+   /**
+  The support list for RE450
+   */
+   .support_list =
+   "SupportList:\r\n"
+   "CPE510(TP-LINK|UN|N300-5):1.0\r\n"
+   "CPE510(TP-LINK|UN|N300-5):1.1\r\n"
+   "CPE520(TP-LINK|UN|N300-5):1.0\r\n"
+   "CPE520(TP-LINK|UN|N300-5):1.1\r\n"
+   "CPE210(TP-LINK|UN|N300-2):1.0\r\n"
+   "CPE210(TP-LINK|UN|N300-2):1.1\r\n"
+   "CPE220(TP-LINK|UN|N300-2):1.0\r\n"
+   "CPE220(TP-LINK|UN|N300-2):1.1\r\n",
+
+   .first_sysupgrade_partition = "os-image",
+
+   .last_sysupgrade_partition = "file-system",
+   }, {
+   .id = "RE450",
+
+   /**
+

[OpenWrt-Devel] [PATCH 3/4] firmware-utils: kernel image generator for TP-Link RE450

2016-01-06 Thread Tal Keren 
The firmware image that is used in TP-Link RE450 (and some more devices from
the RE series) is tplink-safeloader.
In the kernel partition, the kernel is compressed in a regular tp-link
firmware that is just used for booting. Since it is only used for compressing
and booting, only four fields are filled in the header:
Vendor, version, kernel load address and kernel entry point.
mktplinkfw-kernel is a simpler version of mktpolinkfw that generate such
images. It also specifies the hardware id (as it is in the product info
section), so when doing a sysupgrade - the existing code will check for
hardware compatibility.

Signed-off-by: Tal Keren 
---
 tools/firmware-utils/Makefile|   1 +
 tools/firmware-utils/src/mktplinkfw-kernel.c | 352 +++
 2 files changed, 353 insertions(+)
 create mode 100755 tools/firmware-utils/src/mktplinkfw-kernel.c

diff --git a/tools/firmware-utils/Makefile b/tools/firmware-utils/Makefile
index dc922b0..db1c953 100644
--- a/tools/firmware-utils/Makefile
+++ b/tools/firmware-utils/Makefile
@@ -42,6 +42,7 @@ define Host/Compile
$(call cc,mkplanexfw sha1)
$(call cc,mktplinkfw md5)
$(call cc,mktplinkfw2 md5)
+   $(call cc,mktplinkfw-kernel)
$(call cc,tplink-safeloader md5, -Wall)
$(call cc,pc1crypt)
$(call cc,osbridge-crc)
diff --git a/tools/firmware-utils/src/mktplinkfw-kernel.c 
b/tools/firmware-utils/src/mktplinkfw-kernel.c
new file mode 100755
index 000..1565e73
--- /dev/null
+++ b/tools/firmware-utils/src/mktplinkfw-kernel.c
@@ -0,0 +1,352 @@
+/*
+ * Copyright (C) 2009 Gabor Juhos 
+ * Copyright (C) 2016 Tal Keren 
+ *
+ * Stripped down version of the regular tplink firmware that is only used
+ * for compressing and booting the kernel.
+ *
+ * This tool was based on:
+ *   TP-Link WR941 V2 firmware checksum fixing tool.
+ *   Copyright (C) 2008,2009 Wang Jian 
+ *
+ * This program is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License version 2 as published
+ * by the Free Software Foundation.
+ *
+ */
+
+#include 
+#include 
+#include 
+#include 
+#include  /* for unlink() */
+#include 
+#include  /* for getopt() */
+#include 
+#include 
+#include 
+
+#include 
+#include 
+
+#define ALIGN(x,a) ({ typeof(a) __a = (a); (((x) + __a - 1) & ~(__a - 1)); })
+
+#define HEADER_VERSION_V1  0x0100
+
+#define MD5SUM_LEN 16
+
+struct file_info {
+   char*file_name; /* name of the file */
+   uint32_tfile_size;  /* length of the file */
+};
+
+struct fw_header {
+   uint32_tversion;/* header version */
+   charvendor_name[24];
+   charfw_version[36];
+   uint32_thw_id;  /* hardware id */
+   uint32_thw_rev; /* hardware revision */
+   uint32_tunk1;
+   uint8_t md5sum1[MD5SUM_LEN];
+   uint32_tunk2;
+   uint8_t md5sum2[MD5SUM_LEN];
+   uint32_tunk3;
+   uint32_tkernel_la;  /* kernel load address */
+   uint32_tkernel_ep;  /* kernel entry point */
+   uint32_tfw_length;  /* total length of the firmware */
+   uint32_tkernel_ofs; /* kernel data offset */
+   uint32_tkernel_len; /* kernel data length */
+   uint32_trootfs_ofs; /* rootfs data offset */
+   uint32_trootfs_len; /* rootfs data length */
+   uint32_tboot_ofs;   /* bootloader data offset */
+   uint32_tboot_len;   /* bootloader data length */
+   uint16_tver_hi;
+   uint16_tver_mid;
+   uint16_tver_lo;
+   uint8_t pad[354];
+} __attribute__ ((packed));
+
+
+/*
+ * Globals
+ */
+static char *ofname;
+static char *progname;
+static char *vendor = "TP-LINK Technologies";
+static char *version = "ver. 1.0";
+static char *fw_ver = "0.0.0";
+static uint32_t hdr_ver = HEADER_VERSION_V1;
+
+static char *opt_hw_id;
+static uint32_t hw_id = 0;
+static struct file_info kernel_info;
+static uint32_t kernel_la = 0;
+static uint32_t kernel_ep = 0;
+static uint32_t kernel_len = 0;
+
+/*
+ * Message macros
+ */
+#define ERR(fmt, ...) do { \
+   fflush(0); \
+   fprintf(stderr, "[%s] *** error: " fmt "\n", \
+   progname, ## __VA_ARGS__ ); \
+} while (0)
+
+#define ERRS(fmt, ...) do { \
+   int save = errno; \
+   fflush(0); \
+   fprintf(stderr, "[%s] *** error: " fmt ": %s\n", \
+   progname, ## __VA_ARGS__, strerror(save)); \
+} while (0)
+
+#define DBG(fmt, ...) do { \
+   fprintf(stderr, "[%s] " fmt "\n", progname, ## __VA_ARGS__ ); \
+} while (0)
+
+static void usage(int status)
+{
+   FILE *stream = (status != EXIT_SUCCESS) ? stderr : stdout;
+   struct board_info *board;
+
+   fprintf(stream, "Usage: %s [OPTIONS...]\n", progname);

[OpenWrt-Devel] [PATCH 1/4] base-files: add option to specify netdev led mode in configuration generation

2016-01-06 Thread Tal Keren 
This is necessary for controlling leds of RJ45 port, when one indicate the link
status and the other indicate data transfer.

Signed-off-by: Tal Keren 
---
 package/base-files/files/bin/config_generate   | 7 ---
 package/base-files/files/lib/functions/uci-defaults.sh | 2 ++
 2 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/package/base-files/files/bin/config_generate 
b/package/base-files/files/bin/config_generate
index 9218788..4f257e4 100755
--- a/package/base-files/files/bin/config_generate
+++ b/package/base-files/files/bin/config_generate
@@ -257,11 +257,12 @@ generate_led() {
;;
 
netdev)
-   local device
-   json_get_vars device
+   local device mode
+   json_get_vars device mode
+   [ -n "$mode" ] || mode='link tx rx'
uci -q batch <<-EOF
set system.$cfg.trigger='netdev'
-   set system.$cfg.mode='link tx rx'
+   set system.$cfg.mode='$mode'
set system.$cfg.dev='$device'
EOF
;;
diff --git a/package/base-files/files/lib/functions/uci-defaults.sh 
b/package/base-files/files/lib/functions/uci-defaults.sh
index de3f180..c0ff98a 100755
--- a/package/base-files/files/lib/functions/uci-defaults.sh
+++ b/package/base-files/files/lib/functions/uci-defaults.sh
@@ -355,6 +355,7 @@ ucidef_set_led_netdev() {
local name="$2"
local sysfs="$3"
local dev="$4"
+   local mode="$5"
 
json_select_object led
 
@@ -363,6 +364,7 @@ ucidef_set_led_netdev() {
json_add_string type netdev
json_add_string sysfs "$sysfs"
json_add_string device "$dev"
+   [ -n "$mode" ] && json_add_string mode "$mode"
json_select ..
 
json_select ..
-- 
2.6.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 1/1] KernelPackage/usb-net-sr9700: new package

2016-01-06 Thread Heinrich Schuchardt 
Add support for
CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices

Signed-off-by: Heinrich Schuchardt 
---
 package/kernel/linux/modules/usb.mk | 15 +++
 1 file changed, 15 insertions(+)

diff --git a/package/kernel/linux/modules/usb.mk 
b/package/kernel/linux/modules/usb.mk
index a238572..1fdf746 100644
--- a/package/kernel/linux/modules/usb.mk
+++ b/package/kernel/linux/modules/usb.mk
@@ -1315,6 +1315,21 @@ endef
 $(eval $(call KernelPackage,usb-net-rtl8152))
 
 
+define KernelPackage/usb-net-sr9700
+  TITLE:=Support for CoreChip SR9700 ethernet devices
+  KCONFIG:=CONFIG_USB_NET_SR9700
+  FILES:=$(LINUX_DIR)/drivers/$(USBNET_DIR)/sr9700.ko
+  AUTOLOAD:=$(call AutoProbe,sr9700)
+  $(call AddDepends/usb-net)
+endef
+
+define KernelPackage/usb-net-sr9700/description
+ Kernel module for CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices
+endef
+
+$(eval $(call KernelPackage,usb-net-sr9700))
+
+
 define KernelPackage/usb-net-rndis
   TITLE:=Support for RNDIS connections
   KCONFIG:=CONFIG_USB_NET_RNDIS_HOST
-- 
2.1.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Ath10k CT openwrt patches

2016-01-06 Thread Ben Greear 

In case it helps, I've just ported my kernel patches to 4.4.

Only very lightly tested so far...

http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-4.4.dev.y/.git;a=summary

I plan to be adding support for 10.2 CT firmware to this tree...might back-port
it to 4.2 later if that seems useful.

Thanks,
Ben

On 01/06/2016 03:03 AM, Mhlanga Bothin wrote:

Hi Guys,

I am looking for the Candelatech Ath10k kernel patches for openwrt, I was 
wondering if someone could please send them to me?

Thank you in advance,

--
Regards

Mhlanga


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel




--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] Add @APACHE download facility

2016-01-06 Thread Heinrich Schuchardt 
The Apache Software Foundation offers diverse download mirros.

For packaging Apache software a new alias @APACHE is defined.

Signed-off-by: Heinrich Schuchardt 
---
 include/download.mk | 2 +-
 scripts/download.pl | 6 ++
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/include/download.mk b/include/download.mk
index c551647..7b7aa4a 100644
--- a/include/download.mk
+++ b/include/download.mk
@@ -11,7 +11,7 @@ DOWNLOAD_RDEP=$(STAMP_PREPARED) $(HOST_STAMP_PREPARED)
 define dl_method
 $(strip \
   $(if $(2),$(2), \
-$(if $(filter @GNOME/% @GNU/% @KERNEL/% @SF/% @SAVANNAH/% ftp://% http://% 
https://% file://%,$(1)),default, \
+$(if $(filter @APACHE/% @GNOME/% @GNU/% @KERNEL/% @SF/% @SAVANNAH/% 
ftp://% http://% https://% file://%,$(1)),default, \
   $(if $(filter git://%,$(1)),git, \
 $(if $(filter svn://%,$(1)),svn, \
   $(if $(filter cvs://%,$(1)),cvs, \
diff --git a/scripts/download.pl b/scripts/download.pl
index 6f28237..09d492c 100755
--- a/scripts/download.pl
+++ b/scripts/download.pl
@@ -158,6 +158,12 @@ foreach my $mirror (@ARGV) {
for (1 .. 5) {
push @mirrors, "http://downloads.sourceforge.net/$1";;
}
+   } elsif ($mirror =~ /^\@APACHE\/(.+)$/) {
+   push @mirrors, "http://ftp.tudelft.nl/apache/$1";;
+   push @mirrors, "http://apache.openmirror.de/$1";;
+   push @mirrors, "http://mirrors.ocf.berkeley.edu/apache/$1";;
+   push @mirrors, 
"http://mirror.cc.columbia.edu/pub/software/apache/$1";;
+   push @mirrors, "http://ftp.jaist.ac.jp/pub/apache/$1";;
} elsif ($mirror =~ /^\@GNU\/(.+)$/) {
push @mirrors, "http://ftpmirror.gnu.org/$1";;
push @mirrors, "http://ftp.gnu.org/pub/gnu/$1";;
-- 
2.1.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] SDK vs. Toolchain+

2016-01-06 Thread Bastian Bittorf 
* Daniel Dickinson  [06.01.2016 20:11]:
> Obviously your idea of cheap, fast hardware is based on the
> assumption that one is working on OpenWrt for pay rather than hobby.

sorry, i misunderstood and was thinking that it _is_ part of
your business. you are right, it's way too much money for a hobbyist.

bye, bastian.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 2/2] b53: support setting port link state

2016-01-06 Thread Rafał Miłecki 
Signed-off-by: Rafał Miłecki 
---
 .../generic/files/drivers/net/phy/b53/b53_common.c | 40 ++
 1 file changed, 40 insertions(+)

diff --git a/target/linux/generic/files/drivers/net/phy/b53/b53_common.c 
b/target/linux/generic/files/drivers/net/phy/b53/b53_common.c
index 859d8d1..42a1679 100644
--- a/target/linux/generic/files/drivers/net/phy/b53/b53_common.c
+++ b/target/linux/generic/files/drivers/net/phy/b53/b53_common.c
@@ -25,6 +25,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include "b53_regs.h"
 #include "b53_priv.h"
@@ -794,6 +795,42 @@ static int b53_port_get_link(struct switch_dev *dev, int 
port,
 
 }
 
+static int b53_port_set_link(struct switch_dev *dev, int port,
+struct switch_port_link *link)
+{
+   struct b53_device *priv = sw_to_b53(dev);
+
+   if (!priv->ops->phy_write16)
+   return -ENOTSUPP;
+
+   if (link->aneg) {
+   b53_phy_write16(priv, port, MII_BMCR, 0x);
+   b53_phy_write16(priv, port, MII_BMCR, BMCR_ANENABLE | 
BMCR_ANRESTART);
+   } else {
+   u16 bmcr = 0;
+
+   if (link->duplex)
+   bmcr |= BMCR_FULLDPLX;
+
+   switch (link->speed) {
+   case SWITCH_PORT_SPEED_10:
+   break;
+   case SWITCH_PORT_SPEED_100:
+   bmcr |= BMCR_SPEED100;
+   break;
+   case SWITCH_PORT_SPEED_1000:
+   bmcr |= BMCR_SPEED1000;
+   break;
+   default:
+   return -ENOTSUPP;
+   }
+
+   b53_phy_write16(priv, port, MII_BMCR, bmcr);
+   }
+
+   return 0;
+}
+
 static int b53_global_reset_switch(struct switch_dev *dev)
 {
struct b53_device *priv = sw_to_b53(dev);
@@ -1002,6 +1039,7 @@ static const struct switch_dev_ops b53_switch_ops_25 = {
.apply_config = b53_global_apply_config,
.reset_switch = b53_global_reset_switch,
.get_port_link = b53_port_get_link,
+   .set_port_link = b53_port_set_link,
 };
 
 static const struct switch_dev_ops b53_switch_ops_65 = {
@@ -1025,6 +1063,7 @@ static const struct switch_dev_ops b53_switch_ops_65 = {
.apply_config = b53_global_apply_config,
.reset_switch = b53_global_reset_switch,
.get_port_link = b53_port_get_link,
+   .set_port_link = b53_port_set_link,
 };
 
 static const struct switch_dev_ops b53_switch_ops = {
@@ -1048,6 +1087,7 @@ static const struct switch_dev_ops b53_switch_ops = {
.apply_config = b53_global_apply_config,
.reset_switch = b53_global_reset_switch,
.get_port_link = b53_port_get_link,
+   .set_port_link = b53_port_set_link,
 };
 
 struct b53_chip_data {
-- 
1.8.4.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 1/2] b53: add internal API for accessing PHY regs

2016-01-06 Thread Rafał Miłecki 
Signed-off-by: Rafał Miłecki 
---
 .../generic/files/drivers/net/phy/b53/b53_mdio.c | 20 
 .../generic/files/drivers/net/phy/b53/b53_priv.h | 14 ++
 .../generic/files/drivers/net/phy/b53/b53_srab.c | 15 +++
 3 files changed, 49 insertions(+)

diff --git a/target/linux/generic/files/drivers/net/phy/b53/b53_mdio.c 
b/target/linux/generic/files/drivers/net/phy/b53/b53_mdio.c
index 3c25f0e..185c95f 100644
--- a/target/linux/generic/files/drivers/net/phy/b53/b53_mdio.c
+++ b/target/linux/generic/files/drivers/net/phy/b53/b53_mdio.c
@@ -238,6 +238,24 @@ static int b53_mdio_write64(struct b53_device *dev, u8 
page, u8 reg,
return b53_mdio_op(dev, page, reg, REG_MII_ADDR_WRITE);
 }
 
+static int b53_mdio_phy_read16(struct b53_device *dev, int addr, u8 reg,
+  u16 *value)
+{
+   struct mii_bus *bus = dev->priv;
+
+   *value = mdiobus_read(bus, addr, reg);
+
+   return 0;
+}
+
+static int b53_mdio_phy_write16(struct b53_device *dev, int addr, u8 reg,
+   u16 value)
+{
+   struct mii_bus *bus = dev->priv;
+
+   return mdiobus_write(bus, addr, reg, value);
+}
+
 static struct b53_io_ops b53_mdio_ops = {
.read8 = b53_mdio_read8,
.read16 = b53_mdio_read16,
@@ -249,6 +267,8 @@ static struct b53_io_ops b53_mdio_ops = {
.write32 = b53_mdio_write32,
.write48 = b53_mdio_write48,
.write64 = b53_mdio_write64,
+   .phy_read16 = b53_mdio_phy_read16,
+   .phy_write16 = b53_mdio_phy_write16,
 };
 
 static int b53_phy_probe(struct phy_device *phydev)
diff --git a/target/linux/generic/files/drivers/net/phy/b53/b53_priv.h 
b/target/linux/generic/files/drivers/net/phy/b53/b53_priv.h
index 0c4c394..7891238 100644
--- a/target/linux/generic/files/drivers/net/phy/b53/b53_priv.h
+++ b/target/linux/generic/files/drivers/net/phy/b53/b53_priv.h
@@ -36,6 +36,8 @@ struct b53_io_ops {
int (*write32)(struct b53_device *dev, u8 page, u8 reg, u32 value);
int (*write48)(struct b53_device *dev, u8 page, u8 reg, u64 value);
int (*write64)(struct b53_device *dev, u8 page, u8 reg, u64 value);
+   int (*phy_read16)(struct b53_device *dev, int addr, u8 reg, u16 *value);
+   int (*phy_write16)(struct b53_device *dev, int addr, u8 reg, u16 value);
 };
 
 enum {
@@ -299,6 +301,18 @@ static inline int b53_write64(struct b53_device *dev, u8 
page, u8 reg,
return ret;
 }
 
+static inline int b53_phy_read16(struct b53_device *dev, int addr, u8 reg,
+u16 *value)
+{
+   return dev->ops->phy_read16(dev, addr, reg, value);
+}
+
+static inline int b53_phy_write16(struct b53_device *dev, int addr, u8 reg,
+ u16 value)
+{
+   return dev->ops->phy_write16(dev, addr, reg, value);
+}
+
 #ifdef CONFIG_BCM47XX
 
 #include 
diff --git a/target/linux/generic/files/drivers/net/phy/b53/b53_srab.c 
b/target/linux/generic/files/drivers/net/phy/b53/b53_srab.c
index 012daa3..438c6f8 100644
--- a/target/linux/generic/files/drivers/net/phy/b53/b53_srab.c
+++ b/target/linux/generic/files/drivers/net/phy/b53/b53_srab.c
@@ -21,6 +21,7 @@
 #include 
 #include 
 
+#include "b53_regs.h"
 #include "b53_priv.h"
 
 /* command and status register of the SRAB */
@@ -321,6 +322,18 @@ err:
return ret;
 }
 
+static int b53_srab_phy_read16(struct b53_device *dev, int addr, u8 reg,
+  u16 *value)
+{
+   return b53_read16(dev, B53_PORT_MII_PAGE(addr), reg, value);
+}
+
+static int b53_srab_phy_write16(struct b53_device *dev, int addr, u8 reg,
+   u16 value)
+{
+   return b53_write16(dev, B53_PORT_MII_PAGE(addr), reg, value);
+}
+
 static struct b53_io_ops b53_srab_ops = {
.read8 = b53_srab_read8,
.read16 = b53_srab_read16,
@@ -332,6 +345,8 @@ static struct b53_io_ops b53_srab_ops = {
.write32 = b53_srab_write32,
.write48 = b53_srab_write48,
.write64 = b53_srab_write64,
+   .phy_read16 = b53_srab_phy_read16,
+   .phy_write16 = b53_srab_phy_write16,
 };
 
 static int b53_srab_probe(struct platform_device *pdev)
-- 
1.8.4.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] SDK vs. Toolchain+

2016-01-06 Thread Felix Fietkau 
On 2016-01-06 17:52, Daniel Dickinson wrote:
> Hi,
> 
> On 06/01/16 05:24 AM, Bastian Bittorf wrote:
>  > * Daniel Dickinson  [06.01.2016 11:11]:
>  >> Not sure where you got those numbers.  Did you also post the exact
>  >> hardware and software configuration, and testing methodology, and how
>  >> you did the timing and what numbers 140 is (real command to done
>  >
>  > check this thread:
>  > 
> https://lists.openwrt.org/pipermail/openwrt-devel/2015-December/037775.html
>  > 
> https://lists.openwrt.org/pipermail/openwrt-devel/2015-December/037856.html
> 
> Obviously your idea of cheap, fast hardware is based on the assumption 
> that one is working on OpenWrt for pay rather than hobby. You're talking 
> about at least $1200-1600 CAD which is a lot of money these parts, for 
> the type of hardware you're talking about.
> 
> When I did have a job that involved work on openwrt (which I'm not 
> entirely sure was worth it, for all that I got a couple gigs it wasn't 
> with open source-minded companies and for that and other reasons was 
> more frustrating than rewarding, for the most part, given that for 
> openwrt was something of personal interest and I found the proprietary 
> business interested tainted it for me, they say never mix business with 
> pleasure, and for good reason).  I did buy better hardware, but that is 
> now only decent, not the class of hardware you're talking about in your 
> email (and while good, wasn't real server class, ever). At the moment 
> OpenWrt is a hobby for me, so shelling out that kind of money, and 
> finding a place for such hardware, isn't an option.
> 
> You're numbers are pretty bogus for the typical openwrt community 
> member, although they ought to be importance to those who can justify 
> that kind of investment as a business expense.
> 
> So the work on improving build speed, based on Felix's suggestion is 
> still definitely something I think is worthwhile for the kind of 
> situation I am interested in.
So I went ahead and implemented that. Here are the improvements when
there are no kernel config changes (tested on ramips mt7621, where it
already uses the new image building code for everything):

target/compile: 12s -> 8s
target/install: 68s -> 16s

- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] and what is with RB433UL ?

2016-01-06 Thread smilebef 
An other question.

Is there anybody have experience with the RB433UL ?
This board waiting here hopeful for OpenWRT.
The openwrt should run with this board, but i don't have any success.




Am Wed, 6 Jan 2016 17:31:02 +0100
schrieb Damian Kaczkowski :

> I think it's known problem. rb750gl on dd trunk got booting problems
> too. https://dev.openwrt.org/ticket/21379
> But rb750gl case is a little bit worse. It doesn't even boot initramfs
> images.
> 
> 
> On 6 January 2016 at 16:51,  wrote:
> 
> > Is this problem known?
> > The kernel vmlinux.lzma.elf dos not start from nand.
> > wget2nand works fine but the kernel result no answer while booting.
> > It is strange, because tftp with initrd booting fine.
> > This problem is new in trunk.
> > I have no problems with bb and cc.
> >
> > is there a guru for helping?
> > ___
> > openwrt-devel mailing list
> > openwrt-devel@lists.openwrt.org
> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> >  
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] ramips: mtk_soc_eth vs old ralink ethernet driver for the M2M

2016-01-06 Thread Paul Greidanus 
>On Sat, Jan 2, 2016 at 2:45 AM, John Crispin > wrote:
>>* Hi Russel,
** i'll have a look now. [...]
*
>Ethernet appears to be working (no more panics) in r48064, thanks!

I'm seeing the same issues in r48138:



U-Boot for VoCore(based on RT5350)Warning: un-recognized chip ID,
please update bootloader!
.
Version: May 30 2014 20:52:36

Press 'x' to console...


Booting image at bc05 .
   Image Name:   MIPS OpenWrt Linux-4.3
   Created:  2016-01-06  17:19:33 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:1219923 Bytes =  1.2 MB
   Load Address: 8000
   Entry Point:  8000
   Load Kernel:  ...

   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

[0.00] Linux version 4.3.0 (prg3@shell) (gcc version 5.2.0
(OpenWrt GCC 5.2.0 r48014) ) #9 Wed Jan 6 10:18:51 MST 2016
[0.00] SoC Type: Ralink RT5350 id:1 rev:3
[0.00] bootconsole [early0] enabled
[0.00] CPU0 revision is: 0001964c (MIPS 24KEc)
[0.00] MIPS: machine is VoCore
[0.00] Determined physical RAM map:
[0.00]  memory: 0200 @  (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Zone ranges:
[0.00]   Normal   [mem 0x-0x01ff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x01ff]
[0.00] Initmem setup node 0 [mem 0x-0x01ff]
[0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[0.00] Primary data cache 16kB, 4-way, VIPT, no aliases,
linesize 32 bytes
[0.00] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 8128
[0.00] Kernel command line: console=ttyS0,57600
rootfstype=squashfs,jffs2
[0.00] PID hash table entries: 128 (order: -3, 512 bytes)
[0.00] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.00] Writing ErrCtl register=000792b9
[0.00] Readback ErrCtl register=000792b9
[0.00] Memory: 28616K/32768K available (2746K kernel code,
120K rwdata, 536K rodata, 172K init, 191K bss, 4152K reserved, 0K
cma-reserved)
[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] NR_IRQS:256
[0.00] CPU Clock: 360MHz
[0.00] clocksource: systick: mask: 0x max_cycles: 0x,
max_idle_ns: 583261500 ns
[0.00] systick: running - mult: 214748, shift: 32
[0.00] clocksource: MIPS: mask: 0x max_cycles:
0x, max_idle_ns: 10618113593 ns
[0.15] sched_clock: 32 bits at 180MHz, resolution 5ns, wraps
every 11930464253ns
[0.015661] Calibrating delay loop... 239.61 BogoMIPS (lpj=1198080)
[0.090886] pid_max: default: 32768 minimum: 301
[0.100279] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.113352] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.138767] clocksource: jiffies: mask: 0x max_cycles:
0x, max_idle_ns: 1911260446275 ns
[0.158548] pinctrl core: initialized pinctrl subsystem
[0.170269] NET: Registered protocol family 16
[0.224166] rt2880_gpio 1600.gpio: registering 22 gpios
[0.235288] rt2880_gpio 1600.gpio: registering 22 irq handlers
[0.247938] rt2880_gpio 1660.gpio: registering 6 gpios
[0.258859] rt2880_gpio 1660.gpio: registering 6 irq handlers
[0.274174] clocksource: Switched to clocksource MIPS
[0.287044] NET: Registered protocol family 2
[0.297402] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[0.311295] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[0.323880] TCP: Hash tables configured (established 1024 bind 1024)
[0.336761] UDP hash table entries: 256 (order: 0, 4096 bytes)
[0.348384] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[0.361326] NET: Registered protocol family 1
[0.370996] rt-timer 1100.timer: maximum frequency is 3662Hz
[0.385224] futex hash table entries: 256 (order: -1, 3072 bytes)
[0.442865] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[0.454492] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME)
(CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[0.480814] io scheduler noop registered
[0.488620] io scheduler deadline registered (default)
[0.506264] gpio-export gpio-export: 17 gpio(s) exported
[0.517389] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[0.532555] console [ttyS0] disabled
[0.539731] 1c00.uartlite: ttyS0 at MMIO 0x1c00 (irq = 20,
base_baud = 250) is a Palmchip BK-3103
[0.559449] console [ttyS0] enabled
[0.559449] console [ttyS0] enabled
[0.573234] bootconsole [early0] disabled
[0.573234

Re: [OpenWrt-Devel] SDK vs. Toolchain+

2016-01-06 Thread Daniel Dickinson 

Hi,

On 06/01/16 05:24 AM, Bastian Bittorf wrote:
> * Daniel Dickinson  [06.01.2016 11:11]:
>> Not sure where you got those numbers.  Did you also post the exact
>> hardware and software configuration, and testing methodology, and how
>> you did the timing and what numbers 140 is (real command to done
>
> check this thread:
> 
https://lists.openwrt.org/pipermail/openwrt-devel/2015-December/037775.html
> 
https://lists.openwrt.org/pipermail/openwrt-devel/2015-December/037856.html


Obviously your idea of cheap, fast hardware is based on the assumption 
that one is working on OpenWrt for pay rather than hobby. You're talking 
about at least $1200-1600 CAD which is a lot of money these parts, for 
the type of hardware you're talking about.


When I did have a job that involved work on openwrt (which I'm not 
entirely sure was worth it, for all that I got a couple gigs it wasn't 
with open source-minded companies and for that and other reasons was 
more frustrating than rewarding, for the most part, given that for 
openwrt was something of personal interest and I found the proprietary 
business interested tainted it for me, they say never mix business with 
pleasure, and for good reason).  I did buy better hardware, but that is 
now only decent, not the class of hardware you're talking about in your 
email (and while good, wasn't real server class, ever). At the moment 
OpenWrt is a hobby for me, so shelling out that kind of money, and 
finding a place for such hardware, isn't an option.


You're numbers are pretty bogus for the typical openwrt community 
member, although they ought to be importance to those who can justify 
that kind of investment as a business expense.


So the work on improving build speed, based on Felix's suggestion is 
still definitely something I think is worthwhile for the kind of 
situation I am interested in.


Regards,

Daniel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Mikrotik RB411 kernel dos not boot in trunk

2016-01-06 Thread Damian Kaczkowski 
I think it's known problem. rb750gl on dd trunk got booting problems too.
https://dev.openwrt.org/ticket/21379
But rb750gl case is a little bit worse. It doesn't even boot initramfs
images.


On 6 January 2016 at 16:51,  wrote:

> Is this problem known?
> The kernel vmlinux.lzma.elf dos not start from nand.
> wget2nand works fine but the kernel result no answer while booting.
> It is strange, because tftp with initrd booting fine.
> This problem is new in trunk.
> I have no problems with bb and cc.
>
> is there a guru for helping?
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Mikrotik RB411 kernel dos not boot in trunk

2016-01-06 Thread smilebef 
Is this problem known?
The kernel vmlinux.lzma.elf dos not start from nand.
wget2nand works fine but the kernel result no answer while booting.
It is strange, because tftp with initrd booting fine.
This problem is new in trunk.
I have no problems with bb and cc.

is there a guru for helping?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] AE4500 Wifi dropouts

2016-01-06 Thread tapper 

Hi dus any one have time to take a peek at this bug for me pleas?

https://dev.openwrt.org/ticket/21284


Or let me no if it cant be fixt thanks for your time in reading this email.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Ath10k CT openwrt patches

2016-01-06 Thread Mhlanga Bothin 
Hi Guys,

I am looking for the Candelatech Ath10k kernel patches for openwrt, I was
wondering if someone could please send them to me?

Thank you in advance,

-- 
Regards

Mhlanga
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] ca-certificates: update to version 20160104

2016-01-06 Thread Christian Schoenebeck 
- update to latest version 20160104
- remove cpu dependency (PKGARCH:=all)
- set myself as package maintainer

Signed-off-by: Christian Schoenebeck 
---
 package/system/ca-certificates/Makefile | 8 +---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/package/system/ca-certificates/Makefile 
b/package/system/ca-certificates/Makefile
index 18af018..9b6dbd6 100644
--- a/package/system/ca-certificates/Makefile
+++ b/package/system/ca-certificates/Makefile
@@ -1,5 +1,5 @@
 #
-# Copyright (C) 2006-2015 OpenWrt.org
+# Copyright (C) 2006-2016 OpenWrt.org
 #
 # This is free software, licensed under the GNU General Public License v2.
 # See /LICENSE for more information.
@@ -7,11 +7,12 @@
 include $(TOPDIR)/rules.mk
 
 PKG_NAME:=ca-certificates
-PKG_VERSION:=20151214
+PKG_VERSION:=20160104
+PKG_MAINTAINER:=Christian Schoenebeck 
 
 PKG_SOURCE:=$(PKG_NAME)_$(PKG_VERSION).tar.xz
 PKG_SOURCE_URL:=http://ftp.debian.org/debian/pool/main/c/ca-certificates
-PKG_MD5SUM:=2233bfa64af6f58f5eca9735b6742818
+PKG_MD5SUM:=d9665a83d0d3ef8176a38e6aa20458e9
 PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)
 
 PKG_INSTALL:=1
@@ -22,6 +23,7 @@ define Package/ca-certificates
   SECTION:=base
   CATEGORY:=Base system
   TITLE:=System CA certificates
+  PKGARCH:=all
 endef
 
 define Build/Install
-- 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel