Re: [LEDE-DEV] QCA Dakota support

2017-03-09 Thread K.Mani
Initramfs image boots fine from the RAM. Regards Mani On Thu, Mar 9, 2017 at 9:53 PM, Matthew McClintock wrote: > 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

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

Re: [LEDE-DEV] QCA Dakota support

2017-03-09 Thread Matthew McClintock
Can you share a full log? What is the flash_type from smem? Is this a nand or nor booting board? I suggest using initramfs first until you get things going. -M On Thu, Mar 9, 2017 at 7:11 AM, K.Mani wrote: > Hi Matthew, > > I built the qsdk, but the device flash failed & bricked. > and i get the

Re: [LEDE-DEV] QCA Dakota support

2017-03-09 Thread Matthew McClintock
Most of the QCA stuff should be here: https://source.codeaurora.org/quic/qsdk The linux tree should be here: https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/ Searching for a likely branch, I'll go with 'release/dandelion' in general though 'release/*' are good candidates since thos

Re: [LEDE-DEV] QCA Dakota support

2017-03-09 Thread K.Mani
Hi Matthew, I built the qsdk, but the device flash failed & bricked. and i get the u-boot prompt only. Can you suggest me the flashing procedure for ipq40xx? https://source.codeaurora.org/quic/qsdk/releases/manifest/qstak/tree/?h=release --caf_AU_LINUX_QSDK_RELEASE_DAKOTA_CS_TARGET_ALL.3.0.10

Re: [LEDE-DEV] QCA Dakota support

2017-03-08 Thread John Crispin
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 should be in place, the various Dakota boards dk0{1,4,7}-c{1,2,3,4} are very

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

[LEDE-DEV] QCA Dakota support

2017-03-08 Thread K.Mani
I have a target board based on IPQ40xx, I want to port LEDE on it. Does LEDE has support for the following type: Model: Qualcomm Technologies, Inc. IPQ40xx/AP-DK04.1-C2 Compatible: qcom,ipq40xx-apdk04.1qcom,ipq40xx SF: MX25L25635E Thanks Mani ___ Lede-

Re: [LEDE-DEV] QCA Dakota support

2017-02-23 Thread Christian Mehlis
Hi Christian, do you plan to integrate the IPQ40XX support for Asus, ZyXEL and AVM from https://github.com/chunkeey/LEDE-IPQ40XX/commits/staging in the next days? I can provide support for Compex WPJ428 afterwards. Best, Christian Am 2017-02-17 19:22, schrieb John Crispin: On 17/02/2017 17

Re: [LEDE-DEV] QCA Dakota support

2017-02-17 Thread John Crispin
On 17/02/2017 17:06, Matthew McClintock wrote: > Cool, still personally missing a Dakota board myself. Maybe I'll get one soon. > > -M > i used your v4.7-rc for-next tree as basis for the 4.9 support ;) John ___ Lede-dev mailing list Lede-d

Re: [LEDE-DEV] QCA Dakota support

2017-02-17 Thread Christian Lamparter via Lede-dev
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- On Friday, February 17, 2017 4:29:

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-02-17 Thread John Crispin
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 working on QCA Dakota support for lede? > Heads-up! > >

Re: [LEDE-DEV] QCA Dakota support

2017-02-17 Thread Christian Lamparter via Lede-dev
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- On Monday, October 31, 2016 10:38:

Re: [LEDE-DEV] QCA Dakota support

2016-12-19 Thread Christian Lamparter via Lede-dev
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hello, On Monday, November 28, 20

Re: [LEDE-DEV] QCA Dakota support

2016-11-28 Thread Alexis Green
Hi Christian, Thank you for the usb wireless device hint! I had an ath9k-htc dongle kicking about and I'm seeing memory wastage with that device as well (albeit slower and only happening while I'm pumping a lot of traffic through it), so ath10k is likely off the hook for this one. In fact, I went

Re: [LEDE-DEV] QCA Dakota support

2016-11-28 Thread Christian Lamparter
Hello Alexis, On Sunday, November 27, 2016 12:18:00 PM CET Alexis Green wrote: > Could you post .config for your build? I cloned your repo and > successfully built and installed an image, but I'm seeing some rather > weird behavior. I added it, but I don't have any magic values in the .config. I p

Re: [LEDE-DEV] QCA Dakota support

2016-11-27 Thread Alexis Green
Hi Christian, Could you post .config for your build? I cloned your repo and successfully built and installed an image, but I'm seeing some rather weird behavior. I get kernel oops (null derefrence) in bridge code when I connect a client to WPA2 AP that is bridged. The oops is gone after I removed

Re: [LEDE-DEV] QCA Dakota support

2016-11-23 Thread Christian Lamparter
Hi Christian, On Wednesday, November 23, 2016 10:13:45 PM CET Christian Mehlis wrote: > your current staging tree works for me, it generates an itb and a trx > file! > I added some files to support the Compex board I own: > https://github.com/mehlis/source/commits/compex-wpj428 > > Feel free to

Re: [LEDE-DEV] QCA Dakota support

2016-11-23 Thread Christian Mehlis
Hi Christian, your current staging tree works for me, it generates an itb and a trx file! I added some files to support the Compex board I own: https://github.com/mehlis/source/commits/compex-wpj428 Feel free to include some bits in your tree. I had to add dk04-c5 support, perhaps you know so

Re: [LEDE-DEV] QCA Dakota support

2016-11-22 Thread Christian Lamparter
Hello Christian, On Tuesday, November 22, 2016 11:54:44 PM CET Christian Mehlis wrote: > I updated to your current staging branch 947e53a1 (which includes the > musl update). Now compile stops in a problem with the backports package, > which does not match the "new" kernel?! > > /home/c/source/

Re: [LEDE-DEV] QCA Dakota support

2016-11-22 Thread Heiner Kallweit
Am 22.11.2016 um 23:54 schrieb Christian Mehlis: > Hi Christian, > > I updated to your current staging branch 947e53a1 (which includes the musl > update). Now compile stops in a problem with the backports package, which > does not match the "new" kernel?! > > /home/c/source/build_dir/target-arm

Re: [LEDE-DEV] QCA Dakota support

2016-11-22 Thread Christian Mehlis
Hi Christian, I updated to your current staging branch 947e53a1 (which includes the musl update). Now compile stops in a problem with the backports package, which does not match the "new" kernel?! /home/c/source/build_dir/target-arm_cortex-a7+neon-vfpv4_musl-1.1.16_eabi/linux-ipq40xx/compat-w

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

Re: [LEDE-DEV] QCA Dakota support

2016-11-21 Thread Christian Lamparter
Hello, 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/system-linux.c.o > In file included from > /home/cmehlis/gi

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 Christian Mehlis
Hi Christian, 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/system-linux.c.o In file included from /home/cmehlis/git/source/build_dir/target-arm_cortex-a7+neon-vfpv4_musl-1.1.15_eabi/net

Re: [LEDE-DEV] QCA Dakota support

2016-11-13 Thread Christian Lamparter
Hello, On Saturday, November 12, 2016 12:03:54 AM CET Christian Mehlis wrote: > 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 K

Re: [LEDE-DEV] QCA Dakota support

2016-11-12 Thread Ben Greear
Have you tried the ath10k-ct driver? I think it should at least support the radios if you put on the right firmware. Not sure about the rest of the board. Thanks, Ben On 11/12/2016 09:42 AM, Matthew McClintock wrote: On Fri, Nov 11, 2016 at 5:03 PM, Christian Mehlis wrote: Hi Matthew, I t

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-11 Thread Christian Mehlis
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: compat-wireless-2016-10-08/backport-include/linux/netdevice.h:33

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-07 Thread Christian Mehlis
Hi Again, I received multiple private mails in the last days, please always include this mailing list on reply! Current situation from my perspective: 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

[LEDE-DEV] QCA Dakota support

2016-10-31 Thread Christian Mehlis
Hi, is there someone working on QCA Dakota support for lede? Linux 4.4 already has support for the dakota ref board: arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1-c1.dts I received a Compex WPJ428 board containing QSDK (which is in fact openwrt based) and I want to make lede work on it. Unfortuna