Re: [LEDE-DEV] [PATCH] ipq806x: Add nand boot support for ipq40xx AP-DK04.1-C1

2017-05-05 Thread Matthew McClintock
On Fri, May 5, 2017 at 12:00 PM, John Crispin wrote: > On 05/05/17 17:49, Ram Chandra Jangir wrote: >> >> This change add nand boot support for IPQ40xx based >> AP-DK04.1-C1 board using ubi image, also add sysupgrage >> support for AP-DK04.1-C1 and generates a sysupgrade.tar >> image. >> >> Testin

[LEDE-DEV] [PATCH] build: add V=e option for extended build info

2017-06-16 Thread Matthew McClintock
ds to see what actually failed without having to re-run -j1 V=s when the issue may not occur at all. Signed-off-by: Matthew McClintock --- include/verbose.mk | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/include/verbose.mk b/include/verbose.mk index b7e43f7430..fe5c4

Re: [LEDE-DEV] [PATCH] build: add V=e option for extended build info

2017-06-18 Thread Matthew McClintock
On Sat, Jun 17, 2017 at 7:35 AM, Felix Fietkau wrote: > On 2017-06-16 20:58, Matthew McClintock wrote: >> This will output when a job starts and stops: >> >> $ make -j24 V=e >> [ snip ] >> make[3] -C package/network/config/firewall compile >> mak

Re: [LEDE-DEV] [PATCH] uboot-envtools: Add support for IPQ806x AP148 and DB149

2017-06-27 Thread Matthew McClintock
On Mon, Jun 26, 2017 at 6:55 AM, Ram Chandra Jangir wrote: > IPQ806x AP148 and DB149 boards didn't have the UCI ubootenv > section initialized, so the usage of fw_printenv required manual > configuration. With this change, the "fw_printenv" and "fw_setenv" > command will automatically work on NOR

Re: [LEDE-DEV] IPv6 link locals, vlans and bridging

2017-08-25 Thread Matthew McClintock
On Fri, Aug 25, 2017 at 8:16 AM, Kevin Darbyshire-Bryant wrote: > Here's a 'fun' one that I'm trying to work who is doing what incorrectly. > > For 'reasons' I have a number of tagged vlan ethernet interfaces. I also > have a similar number of wifi interfaces. These vlan ethernet interfaces > an

Re: [LEDE-DEV] [RFC 2/3] ipq: Don't force selection of the IPQ4019 firmware.

2017-11-14 Thread Matthew McClintock
What ever came of this? Did something upstream or in LEDE/OpenWrt resolve what files should be loaded from where? -M On Sat, Nov 4, 2017 at 11:38 AM, Ben Greear wrote: > > > On 11/04/2017 08:14 AM, Christian Lamparter wrote: >> >> On Friday, November 3, 2017 8:15:00 PM CET Ben Greear wrote: >>>

Re: [LEDE-DEV] [PATCH 1/4] firmware: ath10k-firmware: update QCA4019 firmware to 10.4-3.2.1-00058

2017-11-20 Thread Matthew McClintock
On Mon, Nov 20, 2017 at 10:53 AM, Christian Lamparter wrote: > On Monday, November 20, 2017 9:45:28 AM CET Matthew McClintock wrote: >> Did you get ath10k working on ipq4019? > > Yes, I managed to upstream the wifi dts changes some time ago and they > all have been accepted. In

Re: [LEDE-DEV] [PATCH 1/4] firmware: ath10k-firmware: update QCA4019 firmware to 10.4-3.2.1-00058

2017-11-20 Thread Matthew McClintock
On Mon, Nov 20, 2017 at 2:59 PM, Christian Lamparter wrote: > On Monday, November 20, 2017 11:23:18 AM CET Matthew McClintock wrote: >> On Mon, Nov 20, 2017 at 10:53 AM, Christian Lamparter >> wrote: >> > On Monday, November 20, 2017 9:45:28 AM CET Matthew McClintock

Re: [LEDE-DEV] [PATCH 1/4] firmware: ath10k-firmware: update QCA4019 firmware to 10.4-3.2.1-00058

2017-12-20 Thread Matthew McClintock
On Tue, Nov 21, 2017 at 9:06 AM, Roman Yeryomin wrote: >>> >>> 2. the pre-cal-ahb-a80.wifi.bin and pre-cal-ahb-a00.wifi.bin >>>don't get loaded or the pre-cal* data is shifted/trimmed/mangled/bad. >>> >>> For 2. you should check if the firmware hotplug 11-ath10k-caldata script >>> is c

Re: [LEDE-DEV] LEDE layerscape hangs with squash rootfs on QSPI flash

2017-12-20 Thread Matthew McClintock
On Sun, Dec 17, 2017 at 9:20 PM, Y.b. Lu wrote: > Hi, > > (Resent the email since HTML format email was rejected by mailing list...) > > Has anyone seen below issue when LEDE started up. The system would hang when > created jffs2 area. > This issue occurred on QSPI flash on layerscape like ls1046

Re: [LEDE-DEV] [PATCH 1/4] firmware: ath10k-firmware: update QCA4019 firmware to 10.4-3.2.1-00058

2017-12-21 Thread Matthew McClintock
On Thu, Dec 21, 2017 at 11:36 AM, Roman Yeryomin wrote: > On 2017-12-20 23:35, Matthew McClintock wrote: >> >> On Tue, Nov 21, 2017 at 9:06 AM, Roman Yeryomin wrote: >>>>> >>>>> >>>>> 2. the pre-cal-ahb-a80.wifi.bin and pre-cal-a

Re: [LEDE-DEV] ipq806x Netgear R7500 uboot

2018-01-17 Thread Matthew McClintock
On Wed, Jan 17, 2018 at 4:28 AM, Thomas Reifferscheid wrote: > Hi, I've lost my original uboot environment settings and would like to ask > for your help. > Since it's been a while from when I was playing with the hardware the uboot > env is all messed up and I'd like to start over from scratch. >

Re: [LEDE-DEV] QCA Dakota support

2016-11-07 Thread Matthew McClintock
On Mon, Nov 7, 2016 at 3:49 PM, Christian Mehlis wrote: > Dakota kernel support done by QCA is public here: > https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?h=release/collard_cc_cs&id=2e6acfb58dceee5baf746a9ed37a8efbad8a7626 For a little bit cleaner tree's take a look here:

Re: [LEDE-DEV] QCA Dakota support

2016-11-12 Thread Matthew McClintock
On Fri, Nov 11, 2016 at 5:03 PM, Christian Mehlis wrote: > Hi Matthew, > > I took your patches to my tree. They are for Linux 4.7, so I tried to make > Lede build with that Linux version. > I ran into some trouble with musl+netifd (fixed it). Now compat-wireless > seems to expect an older Kernel:

Re: [LEDE-DEV] QCA Dakota support

2016-11-21 Thread Matthew McClintock
That doesn't seem related to my changes. I was building with OpenWrt CC release I believe and a really stripped down rootfs/kernel for bring up. Maybe look for newer GCC fixups? -M On Mon, Nov 21, 2016 at 7:57 AM, Christian Mehlis wrote: > Hi Christian, > > I found your repo/branch. I think you

Re: [LEDE-DEV] QCA Dakota support

2016-11-21 Thread Matthew McClintock
On Mon, Nov 21, 2016 at 7:11 PM, Christian Lamparter wrote: > On Monday, November 21, 2016 2:57:59 PM CET Christian Mehlis wrote: >> I found your repo/branch. I think you did a great job! Unfortunately I >> can't compile your staging branch: >> >> [ 4%] Building C object CMakeFiles/netifd.dir/sys

[LEDE-DEV] ubus network restart issue?

2017-01-16 Thread Matthew McClintock
All, I've seen a pretty easy to reproduce ubus issue related to network restart. I've tested this on various releases include the recently release LEDE branch as well as OpenWrt CC. I've also tested on more than one target and with various delays including as long as 2 minutes. Before: root@lede

Re: [LEDE-DEV] QCA Dakota support

2017-02-17 Thread Matthew McClintock
Cool, still personally missing a Dakota board myself. Maybe I'll get one soon. -M On Fri, Feb 17, 2017 at 9:29 AM, John Crispin wrote: > > > On 17/02/2017 15:46, Christian Lamparter wrote: >> On Monday, October 31, 2016 10:38:18 PM CET Christian Mehlis wrote: >>> Hi, >>> >>> is there someone wor

Re: [LEDE-DEV] QCA Dakota support

2017-03-08 Thread Matthew McClintock
Most of the support for the SoC should be in place, the various Dakota boards dk0{1,4,7}-c{1,2,3,4} are very similar. You could look at the device tree's on codeaurora.org to compare the differences from a supported platform and this variant. -M On Wed, Mar 8, 2017 at 2:47 AM, K.Mani wrote: > I

Re: [LEDE-DEV] QCA Dakota support

2017-03-09 Thread Matthew McClintock
ispin wrote: > Hi Matthew, > > can you point me at the tree to use on codeaurora ? i am also looking for > the AP145 dts file. this is ipq8062 based > > John > > > > On 08/03/17 15:49, Matthew McClintock wrote: >> >> Most of the support for the SoC sh

Re: [LEDE-DEV] QCA Dakota support

2017-03-09 Thread Matthew McClintock
xa8 > > > Thanks again > Mani > > On Thu, Mar 9, 2017 at 12:32 PM, John Crispin wrote: >> Hi Matthew, >> >> can you point me at the tree to use on codeaurora ? i am also looking for >> the AP145 dts file. this is ipq8062 based >> >> Joh

Re: [LEDE-DEV] QCA Dakota support

2017-03-09 Thread Matthew McClintock
On Thu, Mar 9, 2017 at 10:15 AM, K.Mani wrote: > Hi Matthew, > > (IPQ40xx) # smeminfo > flash_type: 0x6 > flash_index:0x0 > flash_chip_select: 0x0 > flash_block_size: 0x1 > flash_density: 0x100 > partition table offset 0x0 > No.: Name