674e099678
For most defconfigs, it was trivial to deduce the kernel version, by just reading the version string, which could be: - a standard upstream version string vX.Y.Z - a non-standard version string, but still containg the standard X.Y.Z Those for which it was not so trivial were those hosted on git tree. Since most were already using a custom linux-headers version, it could be easily deduced from that. It was confirmed by browsing said git trees and check the version there. There are a few cases were there was a mismatch: - microzed: uses a 3.18 kernel, but 3.8 headers; fixed. - xilinx_zc706: uses a 3.14 kernel, but 3.8 headers; fixed. - zedboard: uses a 3.18 kernel, but 3.8 headers; fixed. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
22 lines
589 B
Plaintext
22 lines
589 B
Plaintext
# architecture
|
|
BR2_arm=y
|
|
BR2_arm1136jf_s_r0=y
|
|
BR2_ARM_EABIHF=y
|
|
|
|
# Linux headers same as kernel, a 3.15 series
|
|
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_15=y
|
|
|
|
# system
|
|
BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
|
|
|
|
# kernel
|
|
BR2_LINUX_KERNEL=y
|
|
# Note: sadly the Linux kernel will not boot on the i.MX31 PDK, starting with
|
|
# v3.16 and at least up to v4.0-rc4; this is why we use v3.15.y here.
|
|
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
|
|
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.15.10"
|
|
BR2_LINUX_KERNEL_DEFCONFIG="imx_v6_v7"
|
|
BR2_LINUX_KERNEL_ZIMAGE=y
|
|
BR2_TARGET_ROOTFS_CPIO_GZIP=y
|
|
BR2_TARGET_ROOTFS_INITRAMFS=y
|