I will dedicate this thread to attempt to build mainline 4.13.2 kernel for Colibri iMX6DL 512MB V1.1A, and include it in YOCTO build, so I can have Morty with 4.13.2 as final result. So, questions will follow as I progress to the target/final result.
I decided to start playing with TORADEX dts definitions, since, as suggested, they are embedded in the kernel mainline.
And, yes, they are:
user@localhost linux-4.13.2]$ find . -name imx6dl-colibri* ./arch/arm/boot/dts/imx6dl-colibri-eval-v3.dts [user@localhost linux-4.13.2]$
In oredr to set the following: make menuconfig for Colibri iMX6, I need to have another file, called: colibri-imx6-defconfig. So, before I compile dts within 4.13.2, I would like to do: make arch=ARM colibri-imx6-defconfig .
But, interestingly enough, I am not finding this file in 4.13.2 internal structures?!
[user@localhost linux-4.13.2]$ find . -name colibri* ./drivers/input/touchscreen/colibri-vf50-ts.c ./Documentation/devicetree/bindings/input/touchscreen/colibri-vf50-ts.txt ./arch/arm/configs/colibri_pxa300_defconfig ./arch/arm/configs/colibri_pxa270_defconfig ./arch/arm/mach-pxa/colibri-pxa320.c ./arch/arm/mach-pxa/colibri-evalboard.c ./arch/arm/mach-pxa/colibri-pxa3xx.c ./arch/arm/mach-pxa/colibri-pxa300.c ./arch/arm/mach-pxa/colibri-pxa270.c ./arch/arm/mach-pxa/colibri-pxa270-income.c ./arch/arm/mach-pxa/colibri.h [user@localhost linux-4.13.2]$
The question is: why? Having the ./arch/arm/boot/dts/imx6dl-colibri-eval-v3.dts really does not imply having that one: root/arch/arm/configs/colibri_imx6_defconfig , does it???
Or should I use: root/arch/arm/configs/imx_v6_v7_defconfig??? Actually, what is the difference between these two deconfigs: colibri_imx6_defconfig and imx_v6_v7_defconfig?!
The another questions (as process continues) might follow on this thread.