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>
13 lines
480 B
Plaintext
13 lines
480 B
Plaintext
BR2_microblaze=y
|
|
BR2_microblazeel=y
|
|
# Linux headers same as kernel, a 4.4 series
|
|
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
|
|
BR2_TARGET_GENERIC_GETTY_PORT="ttyUL0"
|
|
# BR2_TARGET_ROOTFS_TAR is not set
|
|
BR2_TARGET_ROOTFS_INITRAMFS=y
|
|
BR2_LINUX_KERNEL=y
|
|
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
|
|
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/avnet/s6lx9_microboard/lx9_mmu_defconfig"
|
|
BR2_LINUX_KERNEL_USE_CUSTOM_DTS=y
|
|
BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="board/avnet/s6lx9_microboard/lx9_mmu.dts"
|