date:20160904

Re: [LEDE-DEV] [RFC 3/7] image: pass device blocksize to padjffs2

2016-09-04 Thread Mathias Kresin


05.09.2016 04:02, Yousong Zhou:

On 3 September 2016 at 16:52, Mathias Kresin  wrote:

At the moment the padding steps are hardcoded. Especially images for
devices with a 4K sector size can be unnecessarily bloated using the
hardcoded padding steps.

It has been observed that 192Kb of padding was added to the image of a
4MB device, albeit due to the 4K sector size the minimum required extra
padding for the jffs2 rootfs_data is 20Kb.

In worst case it means that the image-size check could fail albeit
there is enough space for all selected packages

For device build code not exposing the blocksize, use the hardcoded
padding further on.

Signed-off-by: Mathias Kresin 
---
 include/image-commands.mk | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/include/image-commands.mk b/include/image-commands.mk
index 3b9ea3c..76e42ab 100644
--- a/include/image-commands.mk
+++ b/include/image-commands.mk
@@ -131,7 +131,8 @@ define Build/pad-to
 endef

 define Build/pad-rootfs
-   $(STAGING_DIR_HOST)/bin/padjffs2 $@ $(1) 4 8 16 64 128 256
+   $(STAGING_DIR_HOST)/bin/padjffs2 $@ $(1) \
+   $(if $(BLOCKSIZE),$(BLOCKSIZE:%k=%),4 8 16 64 128 256)
 endef



Searching through the code, there are a lot places where BLOCKSIZE is
defined with KiB as the unit suffix or without unit at all (in bytes)


Hey Yousong,

thanks a lot for having a look at this.

In all cases the unit suffix is KiB, the BLOCKSIZE is passed to 
append-ubi (and further to scripts/ubinize-image.sh => ubinize) and 
never to pad-rootfs. For some reasons ubinize uses the unit suffixes 
KiB, MiB and GiB (or no unit for bytes).


I've already a patch in my local tree to unify the unit suffix used in 
BLOCKSIZE to k and change it back to KiB in append-ubi. This way the 
BLOCKSIZE can be reused at a few places.


But before pushing this further I would like to ensure that I'm doing it 
the right way and don't introduce hackish code.


The cases where the BLOCKSIZE is used without unit are also unrelated. 
The block size is passed to dd, genext2fs or ubinize.


Mathias

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH 0/3] Add support for Cisco Meraki Z1

2016-09-04 Thread Chris Blake

This patch group adds support for the Cisco Meraki Z1 Teleworker Gateway unit.
More info can be found at https://wiki.openwrt.org/toh/meraki/z1

Cc: Christian Lamparter 
Signed-off-by: Chris Blake 

Chris Blake (1):
  ar71xx: add support for Cisco Meraki Z1 Cloud Managed Teleworker
Gateway

Christian Lamparter (2):
  firmware-utils mkmerakifw-old: firmware generator for Z1
  kernel: owl-loader for delayed Atheros ath9k fixup

 package/kernel/owl-loader/Makefile |  59 
 package/kernel/owl-loader/src/Makefile |   1 +
 package/kernel/owl-loader/src/owl-loader.c | 246 ++
 target/linux/ar71xx/base-files/etc/board.d/01_leds |   4 +
 .../linux/ar71xx/base-files/etc/board.d/02_network |   6 +
 target/linux/ar71xx/base-files/etc/diag.sh |   3 +
 .../etc/hotplug.d/firmware/10-ath9k-eeprom |  20 ++
 .../etc/uci-defaults/03_network-switchX-migration  |   1 +
 target/linux/ar71xx/base-files/lib/ar71xx.sh   |   3 +
 .../base-files/lib/preinit/05_set_iface_mac_ar71xx |   4 +
 .../ar71xx/base-files/lib/upgrade/merakinand.sh|  61 +++-
 .../ar71xx/base-files/lib/upgrade/platform.sh  |   6 +-
 target/linux/ar71xx/config-4.4 |   1 +
 .../ar71xx/files/arch/mips/ath79/Kconfig.openwrt   |  12 +
 target/linux/ar71xx/files/arch/mips/ath79/Makefile |   1 +
 .../linux/ar71xx/files/arch/mips/ath79/mach-z1.c   | 164 +
 .../linux/ar71xx/files/arch/mips/ath79/machtypes.h |   1 +
 target/linux/ar71xx/image/nand.mk  |  23 ++
 .../818-MIPS-ath79-add-nu801-led-driver.patch  |   2 +-
 tools/firmware-utils/Makefile  |   1 +
 tools/firmware-utils/src/mkmerakifw-old.c  | 369 +
 21 files changed, 969 insertions(+), 19 deletions(-)
 create mode 100644 package/kernel/owl-loader/Makefile
 create mode 100644 package/kernel/owl-loader/src/Makefile
 create mode 100644 package/kernel/owl-loader/src/owl-loader.c
 create mode 100644 target/linux/ar71xx/files/arch/mips/ath79/mach-z1.c
 create mode 100644 tools/firmware-utils/src/mkmerakifw-old.c

--
2.7.4

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH 2/3] kernel: owl-loader for delayed Atheros ath9k fixup

2016-09-04 Thread Chris Blake

From: Christian Lamparter 

Some devices (like the Cisco Meraki Z1 Cloud Managed Teleworker Gateway)
need to be able to initialize the PCIe wifi device. Normally, this is done
during the early stages of booting linux, because the necessary init code
is read from the memory mapped SPI and passed to pci_enable_ath9k_fixup.
However,this isn't possible for devices which have the init code for the
Atheros chip stored on NAND in an UBI volume. Hence, this module can be
used to initialze the chip when the user-space is ready to extract the
init code.

Martin Blumenstingl made a few fixes and added support for lantiq:
kernel: owl-loader: add support for OWL emulation PCI devices
kernel: owl-loader: don't re-scan the bus when ath9k_pci_fixup failed
kernel: owl-loader: use dev_* instead of pr_* logging functions
kernel: owl-loader: auto-generate the eeprom filename as fallback
kernel: owl-loader: add a debug message when swapping the eeprom data
kernel: owl-loader: add missing newlines in log messages
kernel: owl-loader: add support for the lantiq platform

These patches have been integrated. Thanks!

Signed-off-by: Martin Blumenstingl 
Signed-off-by: Christian Lamparter 
---
 package/kernel/owl-loader/Makefile |  59 +++
 package/kernel/owl-loader/src/Makefile |   1 +
 package/kernel/owl-loader/src/owl-loader.c | 246 +
 3 files changed, 306 insertions(+)
 create mode 100644 package/kernel/owl-loader/Makefile
 create mode 100644 package/kernel/owl-loader/src/Makefile
 create mode 100644 package/kernel/owl-loader/src/owl-loader.c

diff --git a/package/kernel/owl-loader/Makefile 
b/package/kernel/owl-loader/Makefile
new file mode 100644
index 000..b6c58de
--- /dev/null
+++ b/package/kernel/owl-loader/Makefile
@@ -0,0 +1,59 @@
+#
+# Copyright (C) 2016 OpenWrt.org
+#
+# This is free software, licensed under the GNU General Public License v2.
+# See /LICENSE for more information.
+#
+
+include $(TOPDIR)/rules.mk
+include $(INCLUDE_DIR)/kernel.mk
+
+PKG_NAME:=owl-loader
+PKG_RELEASE:=1
+
+include $(INCLUDE_DIR)/package.mk
+
+define KernelPackage/owl-loader
+  SUBMENU:=Network Support
+  TITLE:=Owl loader for initializing Atheros PCI(e) Wifi chips
+  DEPENDS:=@PCI_SUPPORT +kmod-ath9k
+  FILES:=$(PKG_BUILD_DIR)/owl-loader.ko
+  AUTOLOAD:=$(call AutoProbe,owl-loader)
+  KCONFIG:=
+endef
+
+define KernelPackage/owl-loader/description
+  Kernel module that helps to initialize certain Qualcomm
+  Atheros' PCI(e) Wifi chips, which have the init data
+  (which contains the PCI device ID for example) stored
+  together with the calibration data in the file system.
+
+  This is necessary for devices like the Cisco Meraki Z1.
+endef
+
+EXTRA_KCONFIG:= \
+   CONFIG_OWL_LOADER=m
+
+EXTRA_CFLAGS:= \
+   $(patsubst CONFIG_%, -DCONFIG_%=1, $(patsubst %=m,%,$(filter 
%=m,$(EXTRA_KCONFIG \
+   $(patsubst CONFIG_%, -DCONFIG_%=1, $(patsubst %=y,%,$(filter 
%=y,$(EXTRA_KCONFIG \
+
+MAKE_OPTS:= \
+   ARCH="$(LINUX_KARCH)" \
+   CROSS_COMPILE="$(TARGET_CROSS)" \
+   SUBDIRS="$(PKG_BUILD_DIR)" \
+   EXTRA_CFLAGS="$(EXTRA_CFLAGS)" \
+   $(EXTRA_KCONFIG)
+
+define Build/Prepare
+   mkdir -p $(PKG_BUILD_DIR)
+   $(CP) ./src/* $(PKG_BUILD_DIR)/
+endef
+
+define Build/Compile
+   $(MAKE) -C "$(LINUX_DIR)" \
+   $(MAKE_OPTS) \
+   modules
+endef
+
+$(eval $(call KernelPackage,owl-loader))
diff --git a/package/kernel/owl-loader/src/Makefile 
b/package/kernel/owl-loader/src/Makefile
new file mode 100644
index 000..6b58276
--- /dev/null
+++ b/package/kernel/owl-loader/src/Makefile
@@ -0,0 +1 @@
+obj-${CONFIG_OWL_LOADER}   += owl-loader.o
diff --git a/package/kernel/owl-loader/src/owl-loader.c 
b/package/kernel/owl-loader/src/owl-loader.c
new file mode 100644
index 000..30340da
--- /dev/null
+++ b/package/kernel/owl-loader/src/owl-loader.c
@@ -0,0 +1,246 @@
+/*
+ * Initialize Owl Emulation Devices
+ *
+ * Copyright (C) 2016 Christian Lamparter 
+ * Copyright (C) 2016 Martin Blumenstingl 
+ *
+ * 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.
+ *
+ * Some devices (like the Cisco Meraki Z1 Cloud Managed Teleworker Gateway)
+ * need to be able to initialize the PCIe wifi device. Normally, this is done
+ * during the early stages of booting linux, because the necessary init code
+ * is read from the memory mapped SPI and passed to pci_enable_ath9k_fixup.
+ * However,this isn't possible for devices which have the init code for the
+ * Atheros chip stored on NAND. Hence, this module can be used to initialze
+ * the chip when the user-space is ready to extract the init code.
+ */
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+
+struct owl_ctx {
+   struct completion eeprom_load;
+};
+
+#define EEPROM_FILENAME_LEN 100
+
+#define AR5416_EE

[LEDE-DEV] [PATCH 3/3] ar71xx: add support for Cisco Meraki Z1 Cloud Managed Teleworker Gateway

2016-09-04 Thread Chris Blake

This patch adds support for Cisco's Z1.
Detailed instructions for the flashing the device can
be found in the OpenWrt wiki:


Signed-off-by: Chris Blake 
---
 target/linux/ar71xx/base-files/etc/board.d/01_leds |   4 +
 .../linux/ar71xx/base-files/etc/board.d/02_network |   6 +
 target/linux/ar71xx/base-files/etc/diag.sh |   3 +
 .../etc/hotplug.d/firmware/10-ath9k-eeprom |  20 +++
 .../etc/uci-defaults/03_network-switchX-migration  |   1 +
 target/linux/ar71xx/base-files/lib/ar71xx.sh   |   3 +
 .../base-files/lib/preinit/05_set_iface_mac_ar71xx |   4 +
 .../ar71xx/base-files/lib/upgrade/merakinand.sh|  61 ++--
 .../ar71xx/base-files/lib/upgrade/platform.sh  |   6 +-
 target/linux/ar71xx/config-4.4 |   1 +
 .../ar71xx/files/arch/mips/ath79/Kconfig.openwrt   |  12 ++
 target/linux/ar71xx/files/arch/mips/ath79/Makefile |   1 +
 .../linux/ar71xx/files/arch/mips/ath79/mach-z1.c   | 164 +
 .../linux/ar71xx/files/arch/mips/ath79/machtypes.h |   1 +
 target/linux/ar71xx/image/nand.mk  |  23 +++
 .../818-MIPS-ath79-add-nu801-led-driver.patch  |   2 +-
 16 files changed, 293 insertions(+), 19 deletions(-)
 create mode 100644 target/linux/ar71xx/files/arch/mips/ath79/mach-z1.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 cf05859..7551455 100755
--- a/target/linux/ar71xx/base-files/etc/board.d/01_leds
+++ b/target/linux/ar71xx/base-files/etc/board.d/01_leds
@@ -813,6 +813,10 @@ wzr-hp-g300nh)
ucidef_set_led_usbdev "usb" "USB" "buffalo:blue:usb" "1-1"
;;
 
+z1)
+   ucidef_set_led_netdev "wlan1" "WLAN1" "z1:blue:tricolor0" "wlan1"
+   ;;
+
 zbt-we1526)
ucidef_set_led_netdev "wan" "WAN" "zbt-we1526:green:wan" "eth1"
ucidef_set_led_switch "lan1" "LAN1" "zbt-we1526:green:lan1" "switch0" 
"0x10"
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 f185e05..76ed5c2 100755
--- a/target/linux/ar71xx/base-files/etc/board.d/02_network
+++ b/target/linux/ar71xx/base-files/etc/board.d/02_network
@@ -539,6 +539,12 @@ wndr3700)
ucidef_add_switch_port_attr "switch0" 5 led 2
;;
 
+z1)
+   ucidef_set_interfaces_lan_wan "eth0" "eth1"
+   ucidef_add_switch "switch0" \
+   "0@eth0" "1:lan:1" "2:lan:2" "3:lan:3" "4:lan:4" "5:wan"
+   ;;
+
 *)
ucidef_set_interfaces_lan_wan "eth0" "eth1"
;;
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh 
b/target/linux/ar71xx/base-files/etc/diag.sh
index 69ef609..6ce49b0 100644
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -426,6 +426,9 @@ get_status_led() {
wrt160nl)
status_led="wrt160nl:blue:wps"
;;
+   z1)
+   status_led="z1:green:tricolor0"
+   ;;
zbt-we1526)
status_led="zbt-we1526:green:status"
;;
diff --git 
a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom 
b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
index 3b0229d..3141625 100644
--- a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
+++ b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
@@ -73,6 +73,16 @@ case "$FIRMWARE" in
ath9k_eeprom_extract "caldata" 4096 2048
ath9k_patch_firmware_mac $(mtd_get_mac_binary caldata 0)
;;
+   z1)
+   . /lib/upgrade/nand.sh
+
+   if [ -n "$(nand_find_volume ubi0 caldata)" ]; then
+   ath9k_ubi_eeprom_extract "caldata" 4096 2048
+   else
+   ath9k_eeprom_extract "origcaldata" 4096 2048
+   fi
+   ath9k_patch_firmware_mac $(macaddr_add $(mtd_get_mac_binary_ubi 
board-config 102) +2)
+   ;;
*)
ath9k_eeprom_die "board $board is not supported yet"
;;
@@ -100,6 +110,16 @@ case "$FIRMWARE" in
ath9k_eeprom_extract "caldata" 20480 2048
ath9k_patch_firmware_mac $(mtd_get_mac_binary caldata 12)
;;
+   z1)
+   . /lib/upgrade/nand.sh
+
+   if [ -n "$(nand_find_volume ubi0 caldata)" ]; then
+   ath9k_ubi_eeprom_extract "caldata" 86016 4096
+   else
+   ath9k_eeprom_extract "origcaldata" 86016 4096
+   fi
+   ath9k_patch_firmware_mac $(macaddr_add $(mtd_get_mac_binary_ubi 
board-config 102) +3)
+   ;;
*)
ath9k_eeprom_die "board $board is not supported yet"
;;
diff --git 
a/target/linux/ar71xx/base-files/etc/uci-defaults/03_network-switchX-migration 
b/target/linux/ar71xx/base-files/etc/uci-def

[LEDE-DEV] [PATCH 1/3] firmware-utils mkmerakifw-old: firmware generator for Z1

2016-09-04 Thread Chris Blake

From: Christian Lamparter 

This patch adds firmware generation tool for Cisco's Z1

Signed-off-by: Christian Lamparter 
---
 tools/firmware-utils/Makefile |   1 +
 tools/firmware-utils/src/mkmerakifw-old.c | 369 ++
 2 files changed, 370 insertions(+)
 create mode 100644 tools/firmware-utils/src/mkmerakifw-old.c

diff --git a/tools/firmware-utils/Makefile b/tools/firmware-utils/Makefile
index f4a5222..803ada4 100644
--- a/tools/firmware-utils/Makefile
+++ b/tools/firmware-utils/Makefile
@@ -74,6 +74,7 @@ define Host/Compile
$(call cc,dgn3500sum)
$(call cc,edimax_fw_header, -Wall)
$(call cc,mkmerakifw sha1, -Wall)
+   $(call cc,mkmerakifw-old, -Wall)
$(call cc,jcgimage, -lz -Wall)
 endef
 
diff --git a/tools/firmware-utils/src/mkmerakifw-old.c 
b/tools/firmware-utils/src/mkmerakifw-old.c
new file mode 100644
index 000..01b9b31
--- /dev/null
+++ b/tools/firmware-utils/src/mkmerakifw-old.c
@@ -0,0 +1,369 @@
+/*
+ * Copyright (C) 2015 Thomas Hebb 
+ * Copyright (C) 2016 Christian Lamparter 
+ *
+ * The format of the header this tool generates was first documented by
+ * Chris Blake  in a shell script of the
+ * same purpose. I have created this reimplementation at his request. The
+ * original script can be found at:
+ * 
+ *
+ * Support for the old header format, which is used by the Cisco Z1 AP
+ * has been reverse engineered from the nandloader's nand_load_bk function.
+ * The original code is part of Cisco's GPL code and can be found at:
+ * 
+ *
+ * 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 
+#include 
+#include 
+#include 
+#include 
+
+#define PADDING_BYTE   0xff
+
+#define HDR_LENGTH 0x0020
+#define HDR_OFF_MAGIC1 0
+#define HDR_OFF_LOAD_ADDR  4
+#define HDR_OFF_IMAGELEN   8
+#define HDR_OFF_ENTRY  12
+#define HDR_OFF_CHECKSUM   16
+#define HDR_OFF_FILLER020
+#define HDR_OFF_FILLER124
+#define HDR_OFF_FILLER228
+
+struct board_info {
+   char *id;
+   char *description;
+   uint32_t magic;
+   uint32_t imagelen;
+   uint32_t load_addr;
+   uint32_t entry;
+};
+
+/*
+ * Globals
+ */
+static char *progname;
+static bool strip_padding;
+
+static char *board_id;
+static const struct board_info *board;
+
+static const struct board_info boards[] = {
+   {
+   .id = "z1",
+   .description= "Meraki Z1 Access Point",
+   .magic  = 0x4d495053,
+   .imagelen   = 0x007e,
+   .load_addr  = 0x8006,
+   .entry  = 0x8006
+   }, {
+   /* terminating entry */
+   }
+};
+
+/*
+ * 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 "\n", \
+   progname, ## __VA_ARGS__, strerror(save)); \
+} while (0)
+
+static const struct board_info *find_board(const char *id)
+{
+   const struct board_info *ret;
+   const struct board_info *board;
+
+   ret = NULL;
+   for (board = boards; board->id != NULL; board++) {
+   if (strcasecmp(id, board->id) == 0) {
+   ret = board;
+   break;
+   }
+   }
+
+   return ret;
+}
+
+static void usage(int status)
+{
+   FILE *stream = (status != EXIT_SUCCESS) ? stderr : stdout;
+   const struct board_info *board;
+
+   fprintf(stream, "Usage: %s [OPTIONS...]\n", progname);
+   fprintf(stream,
+"\n"
+"Options:\n"
+"  -B   create image for the board specified with \n"
+"  -iread kernel image from the file \n"
+"  -owrite output to the file \n"
+"  -s  strip padding from the end of the image\n"
+"  -h  show this screen\n"
+   );
+
+   fprintf(stream, "\nBoards:\n");
+   for (board = boards; board->id != NULL; board++)
+   fprintf(stream, "  %-16s%s\n", board->id, board->description);
+
+   exit(status);
+}
+
+static void writel(unsigned char *buf, size_t offset, uint32_t value)
+{
+   value = htobe32(value);
+   memcpy(buf + offset, &value, sizeof(uint32_t));
+}
+
+static const uint32_t crc32_table[] = {
+   0x, 0x77073096, 0xee0e612c, 0x990951ba,
+   0x076dc419, 0x706af48f, 0xe963a535, 0x9e6495a3,
+   0x0edb8832, 0x79dcb8a4, 0xe0d5e91e, 0x97d2d988,
+   0x09b64c2b, 0x7eb17cbd, 0xe7b82d07, 0x90bf1d91,
+

Re: [LEDE-DEV] [RFC 3/7] image: pass device blocksize to padjffs2

2016-09-04 Thread Yousong Zhou

On 3 September 2016 at 16:52, Mathias Kresin  wrote:
> At the moment the padding steps are hardcoded. Especially images for
> devices with a 4K sector size can be unnecessarily bloated using the
> hardcoded padding steps.
>
> It has been observed that 192Kb of padding was added to the image of a
> 4MB device, albeit due to the 4K sector size the minimum required extra
> padding for the jffs2 rootfs_data is 20Kb.
>
> In worst case it means that the image-size check could fail albeit
> there is enough space for all selected packages
>
> For device build code not exposing the blocksize, use the hardcoded
> padding further on.
>
> Signed-off-by: Mathias Kresin 
> ---
>  include/image-commands.mk | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/image-commands.mk b/include/image-commands.mk
> index 3b9ea3c..76e42ab 100644
> --- a/include/image-commands.mk
> +++ b/include/image-commands.mk
> @@ -131,7 +131,8 @@ define Build/pad-to
>  endef
>
>  define Build/pad-rootfs
> -   $(STAGING_DIR_HOST)/bin/padjffs2 $@ $(1) 4 8 16 64 128 256
> +   $(STAGING_DIR_HOST)/bin/padjffs2 $@ $(1) \
> +   $(if $(BLOCKSIZE),$(BLOCKSIZE:%k=%),4 8 16 64 128 256)
>  endef
>

Searching through the code, there are a lot places where BLOCKSIZE is
defined with KiB as the unit suffix or without unit at all (in bytes)

yousong

>  define Build/pad-offset
> --
> 2.7.4
>
>
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH 1/4] ar71xx: switch to 24kc

2016-09-04 Thread Felix Fietkau

On 2016-09-04 22:59, Milan Knížek wrote:
> What is the reason we don't tune CPU_TYPE to 74kc for ar71xx?
Last time I checked, it hurt 24kc/34kc devices more than it helped 74kc
devices.

- Felix


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH 1/4] ar71xx: switch to 24kc

2016-09-04 Thread Milan Knížek


What is the reason we don't tune CPU_TYPE to 74kc for ar71xx?

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH v2] imx6: enable ARM crypto acceleration

2016-09-04 Thread Felix Fietkau

On 2016-09-01 16:10, Koen Vandeputte wrote:
Next time, please make sure your changes have a proper Signed-off-by.
I forgot to check for that before I pushed the change.

- Felix

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [RFC 3/7] image: pass device blocksize to padjffs2

[LEDE-DEV] [PATCH 0/3] Add support for Cisco Meraki Z1

[LEDE-DEV] [PATCH 2/3] kernel: owl-loader for delayed Atheros ath9k fixup

[LEDE-DEV] [PATCH 3/3] ar71xx: add support for Cisco Meraki Z1 Cloud Managed Teleworker Gateway

[LEDE-DEV] [PATCH 1/3] firmware-utils mkmerakifw-old: firmware generator for Z1

Re: [LEDE-DEV] [RFC 3/7] image: pass device blocksize to padjffs2

Re: [LEDE-DEV] [PATCH 1/4] ar71xx: switch to 24kc

Re: [LEDE-DEV] [PATCH 1/4] ar71xx: switch to 24kc

Re: [LEDE-DEV] [PATCH v2] imx6: enable ARM crypto acceleration

9 matches

Site Navigation

Mail list logo

Footer information