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

On 08/09/2016 23:58, Christian Lamparter wrote: > So yes, if it needs to go in a different location, that would be fine. > Based on your suggestion, I think the owl-loader.c code can be moved to: > target/linux/generic/files/drivers/net/wireless/ath9k/owl-loader.c > > and the module definition f

Re: [LEDE-DEV] [PATCH ubox] getrandom: Define SYS_getrandom if no definition exists

On 18/09/2016 02:13, Florian Fainelli wrote: > Le 17/09/2016 à 16:49, Etienne Champetier a écrit : >> Hi Florian, >> >> What is your use case? > > Pre-built toolchain which ships with kernel headers 3.8 at the moment. > >> If you run it on kernel less than 3.17 this will then fail at run time .

Re: [LEDE-DEV] [PATCH firewall3] utils.h: Avoid name clashes for setbit/delbit/hasbit

Hi Florian, merged into the fw3 repo. i did not update the package in lede yet. first want to talk to jow if current head of that repo is production ready. John On 02/09/2016 04:10, Florian Fainelli wrote: > Rename to fw3_{set,del,has}bit to avoid name clashes with sys/param.h: > > /opt

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

On Sun, Sep 18, 2016 at 2:01 PM, John Crispin wrote: > > > On 08/09/2016 23:58, Christian Lamparter wrote: >> So yes, if it needs to go in a different location, that would be fine. >> Based on your suggestion, I think the owl-loader.c code can be moved to: >> target/linux/generic/files/drivers/net

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

On 18/09/2016 14:17, Martin Blumenstingl wrote: > On Sun, Sep 18, 2016 at 2:01 PM, John Crispin wrote: >> >> >> On 08/09/2016 23:58, Christian Lamparter wrote: >>> So yes, if it needs to go in a different location, that would be fine. >>> Based on your suggestion, I think the owl-loader.c code c

[LEDE-DEV] merging the layerscape target

Hi all, i have just spent some time reviewing the layerscape PR [1] and started a full build of it. its starting to look good and i cannot see any blockers. if anyone has any hold on this please let me know in the next couple of days. if i dont get any vetos i will merge it. John [1] htt

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

On Sunday, September 18, 2016 2:19:33 PM CEST John Crispin wrote: > On 18/09/2016 14:17, Martin Blumenstingl wrote: > > On Sun, Sep 18, 2016 at 2:01 PM, John Crispin wrote: > >> On 08/09/2016 23:58, Christian Lamparter wrote: > >>> So yes, if it needs to go in a different location, that would be f

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

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

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

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 V2 changes, as requested: * Move owl-loader to package/kernel/linux/modules/other V1 discussions are at http://lists.infradead.org/pipermail/led

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

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

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

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/

[LEDE-DEV] mcs814x (Moschip MCS814x): update to kernel 4.4, please test

Hi, I updated the mcs814x target to kernel 4.4 in this branch: https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 If you have any device supported by this target please test it and report back if the mcs814x target is still working with kernel 4.4 like with

[LEDE-DEV] ar7 (TI AR7): update to kernel 4.4, please test

Hi, I updated the ar7 target to kernel 4.4 in this branch: https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 If you have any device supported by this target please test it and report back if the ar7 target is still working with kernel 4.4 like with the old

[LEDE-DEV] rb532 (Mikrotik RouterBoard 532): update to kernel 4.4, please test

Hi, I updated the rb532 target to kernel 4.4 in this branch: https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 If you have any device supported by this target please test it and report back if the rb532 target is still working with kernel 4.4 like with the

[LEDE-DEV] ppc44x (AMCC/IBM PPC44x): update to kernel 4.4, please test

Hi, I updated the ppc44x target to kernel 4.4 in this branch: https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 If you have any device supported by this target please test it and report back if the ppc44x target is still working with kernel 4.4 like with th

[LEDE-DEV] xburst (Ingenic XBurst): update to kernel 4.4, please test

Hi, I updated the xburst target to kernel 4.4 in this branch: https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4 If you have any device supported by this target please test it and report back if the xburst target is still working with kernel 4.4 like with th

Re: [LEDE-DEV] [PATCH ubox] getrandom: Define SYS_getrandom if no definition exists

Le 18/09/2016 à 12:06, Etienne Champetier a écrit : > (Answering from my phone with gmail so this email is in HTML and will > get bounced by the ML) > > Le 18 sept. 2016 14:03, "John Crispin" > a écrit : >> >> >> >> On 18/09/2016 02:13, Florian Fainelli wrote: >> > Le 17/

[LEDE-DEV] hostapd: 420-indicate-features.patch

Hi, 420-indicate-features.patch doesn't work for hostapd full. The Makefile in hostapd-full/hostapd--xx-xx/hostapd doesn't define IEEE8021X_EAPOL or IEEE80211N depend on configuration. Luci usese 'hostapd -veap' to check if an external radius server is supported. It will be evaluate only, if

[LEDE-DEV] [PATCH] ath10k-firmware: move to firmware section in buildroot

This patch moves the ath10k firmware packages to the firmware submenu in the buildroot, where it belongs. Signed-off-by: Stijn Segers --- package/firmware/ath10k-firmware/Makefile | 20 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/package/firmware/ath10k-fi

[LEDE-DEV] [PATCH v2 1/2] ath10k-firmware: update the qca988x firmware to 10.2.4.70.54

Use firmware version 10.2.4.70.54 from kvalo's git repository. The old version (even though it's version number is greater) is an old version from September 2015. Using only the firmware versions from kvalo's git repo is recommended, because those are tested by QCA's internal QCA. The QCA988X dire

[LEDE-DEV] [PATCH v2 0/2] update QCA988X ath10k-firmware to the latest version

According to Kalle Valo (on the OpenWrt mailing list, see [0]) only firmware binaries from his repository are tested by QCA's internal QA team. Additionally he pointed out that the version used in LEDE so far is from September 2015, despite having a newer version number than the current "stable" v

[LEDE-DEV] [PATCH v2 2/2] ar71xx: Do not use a hardcoded ath10k firmware mac address

ar71xx has an init-script for special devices where the ath10k OTP calibration data is stored on the PCIe card's EEPROM (and thus can only be read by ath10k). Unfortunately the OTP data uses the default mac address (= all devices come with the same mac address, which leads to problems when you have

Re: [LEDE-DEV] [PATCH v2 2/2] ar71xx: Do not use a hardcoded ath10k firmware mac address

On Sun, Sep 18, 2016 at 11:29 PM, Martin Blumenstingl wrote: > ar71xx has an init-script for special devices where the ath10k OTP > calibration data is stored on the PCIe card's EEPROM (and thus can only > be read by ath10k). Unfortunately the OTP data uses the default mac > address (= all devices

[LEDE-DEV] [PATCH] busybox: update to version 1.25.0

cd config ../convert_menuconfig.pl .../build_dir/target-*/busybox-1.25.0 cd .. ./convert_defaults.pl < .../build_dir/target-*/busybox-1.25.0/.config > Config-defaults.in Signed-off-by: Hauke Mehrtens --- package/utils/busybox/Config-defaults.in | 169 + package/uti