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
761 B
Plaintext
22 lines
761 B
Plaintext
BR2_arm=y
|
|
BR2_arm926t=y
|
|
BR2_GLOBAL_PATCH_DIR="board/calao/qil-a9260/patches/"
|
|
BR2_TARGET_GENERIC_GETTY_PORT="ttyS1"
|
|
# Linux headers same as kernel, a 3.4 series
|
|
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_4=y
|
|
BR2_PACKAGE_HOST_SAM_BA=y
|
|
BR2_TARGET_ROOTFS_UBIFS=y
|
|
BR2_TARGET_AT91BOOTSTRAP=y
|
|
BR2_TARGET_AT91BOOTSTRAP_BOARD="qil_a9260"
|
|
BR2_TARGET_AT91BOOTSTRAP_NANDFLASH=y
|
|
BR2_TARGET_BAREBOX=y
|
|
BR2_TARGET_BAREBOX_CUSTOM_VERSION=y
|
|
BR2_TARGET_BAREBOX_CUSTOM_VERSION_VALUE="2012.08.0"
|
|
BR2_TARGET_BAREBOX_BOARD_DEFCONFIG="qil_a9260"
|
|
BR2_LINUX_KERNEL=y
|
|
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
|
|
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.4.7"
|
|
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
|
|
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/calao/qil-a9260/linux-3.4.7.config"
|
|
BR2_LINUX_KERNEL_ZIMAGE=y
|