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>
27 lines
606 B
Plaintext
27 lines
606 B
Plaintext
# architecture
|
|
BR2_i386=y
|
|
BR2_x86_i586=y
|
|
|
|
# Linux headers same as kernel, a 3.17 series
|
|
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_17=y
|
|
|
|
# system
|
|
BR2_TARGET_GENERIC_GETTY_PORT="ttyS1"
|
|
BR2_ROOTFS_OVERLAY="board/ts/ts5x00/fs-overlay"
|
|
|
|
# kernel
|
|
BR2_LINUX_KERNEL=y
|
|
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
|
|
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.17.8"
|
|
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
|
|
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/ts/ts5x00/linux-3.17.config"
|
|
BR2_LINUX_KERNEL_INSTALL_TARGET=y
|
|
|
|
# rootfs
|
|
BR2_TARGET_ROOTFS_EXT2=y
|
|
BR2_TARGET_ROOTFS_EXT2_4=y
|
|
|
|
# bootloader
|
|
BR2_TARGET_SYSLINUX=y
|
|
BR2_TARGET_SYSLINUX_MBR=y
|