[LEDE-DEV] QCA Dakota support

Christian Lamparter chunkeey at googlemail.com
Mon Nov 21 17:11:48 PST 2016


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/git/source/build_dir/target-arm_cortex-a7+neon-vfpv4_musl-1.1.15_eabi/netifd-2016-10-27/system-linux.c:24:0:
> /home/cmehlis/git/source/staging_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-5.4.0_musl-1.1.15_eabi/include/linux/if.h:79:2: 
> error: expected identifier before numeric constant
>    IFF_UP    = 1<<0,  /* sysfs */
> 
> Do you see the same problem? Rebasing your staging branch on top of 
> lede/master did not help.

Yes, I did get the same error for netifd (and for ppp later on).
After a dirclean these showed up here too. I traced the netifd
error down to the following patch:
"include/uapi/linux/if_tunnel.h: include linux/if.h, linux/ip.h and linux/in6.h" [0]

For now, I reverted the change (in the v4.8.10), but I think this needs to be fixed
in musl (to that end, I updated to musl.git - and that was enough to fix
the ppp error).  Anyway, let me know, if this fixes the compile errors
but don't forget run make dirclean.

It would be great to add support for a IPQ4028 device too. However, the
dtsi files for the IPQ4028 never landed in upstream vanilla?! Also, the
kernel devicetree maintainers frown upon "catch-all" compatible strings [1].
So, you'll need to replace all the "qcom,ipq40xx" with either "qcom,ipq4028"
or stick with the "qcom,ipq4019" for now (you can add it as the second
compatible string.) Also note: the qcom,ipq4019.dtsi doesn't have a
memory-node. However, this node is essential for booting.

Best Regards,
Christian

[0] <https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/include?id=1fe8e0f074c77aa41aaa579345a9e675acbebfa9>
[1] <https://patchwork.kernel.org/patch/7062591/>




More information about the Lede-dev mailing list