yann@448: # Linux kernel options yann@448: yann@2444: ## select KERNEL_SUPPORTS_SHARED_LIBS yann@2444: ## yann@2444: ## help Build a toolchain targeting systems running Linux as a kernel. yann@2446: yann@2446: config KERNEL_LINUX_USE_CUSTOM_HEADERS yann@2446: bool yann@2602: prompt "Use pre-installed headers tree (OBSOLETE)" yann@2602: depends on OBSOLETE yann@2446: help yann@2446: If you have some pre-installed kernel headers lying around, you can yann@2446: enter the path to these headers, below, they will be copied from yann@2446: there, and into the toolchain's sysroot. yann@2446: yann@2446: Note: yann@2446: This will *not* let you use a complete kernel tree! yann@2602: If you want to use your own full kernel tree, then you want to say 'N' yann@2602: here, and select KERNEL_LINUX_CUSTOM, in the versions list, below. yann@2446: yann@2603: if ! KERNEL_LINUX_USE_CUSTOM_HEADERS yann@2446: yann@2446: choice yann@2446: bool yann@2446: prompt "Linux kernel version" yann@2446: # Don't remove next line yann@2446: # CT_INSERT_VERSION_BELOW yann@2446: benoit@3017: config KERNEL_V_3_5 benoit@2996: bool benoit@3017: prompt "3.5" benoit@2996: yann@3020: config KERNEL_V_3_4_7 yann@2993: bool yann@3020: prompt "3.4.7" benoit@2940: yann@2993: config KERNEL_V_3_3_8 benoit@2940: bool yann@2993: prompt "3.3.8" benoit@2940: yann@3026: config KERNEL_V_3_2_25 benoit@2940: bool yann@3026: prompt "3.2.25" yann@2812: yann@2852: config KERNEL_V_3_1_10 yann@2799: bool yann@2852: prompt "3.1.10" yann@2799: yann@3026: config KERNEL_V_3_0_39 yann@2799: bool yann@3026: prompt "3.0.39" yann@2568: yann@2596: config KERNEL_V_2_6_39_4 yann@2566: bool yann@2596: prompt "2.6.39.4" yann@2473: bryanhundven@2513: config KERNEL_V_2_6_38_8 yann@2473: bool bryanhundven@2513: prompt "2.6.38.8" yann@2446: yann@2446: config KERNEL_V_2_6_37_6 yann@2446: bool yann@2446: prompt "2.6.37.6" yann@2446: yann@2446: config KERNEL_V_2_6_36_4 yann@2446: bool yann@2446: prompt "2.6.36.4" yann@2446: yann@2741: config KERNEL_V_2_6_33_20 yann@2446: bool yann@2741: prompt "2.6.33.20" yann@2596: help yann@2596: This is primarily for the use of those people who are stuck using the yann@2596: .33-rt kernel. Anyone else who really wants to use the .33 kernel tree yann@2596: is welcome to use this one as well. yann@2446: yann@2921: config KERNEL_V_2_6_32_59 yann@2446: bool yann@2921: prompt "2.6.32.59 (longterm)" yann@2446: help yann@2446: The Linux 2.6.32 tree is a "longterm" maintenance branch. yann@2446: yann@2446: It is intended to fill the niche for users who are not using distribution yann@2446: kernels but want to use a regression-free kernel for a longer time. yann@2446: yann@2446: Critical bug fixes to later 2.6 releases are often ported to this branch yann@2446: which makes 2.6.32 a very useful base for many embedded developers seeking yann@2446: stable APIs or those who do not need the latest bleeding edge features. yann@2446: yann@2446: ... and no, this kernel has not undergone any specific QA testing. yann@2446: yann@2446: See the original announcement by Greg Kroah-Hartman in the following yann@2446: mailing list entry: yann@2446: http://marc.info/?l=linux-kernel&m=126384198403392&w=4 yann@2446: yann@2446: config KERNEL_V_2_6_31_14 yann@2446: bool yann@2446: prompt "2.6.31.14" yann@2446: yann@2921: config KERNEL_V_2_6_27_62 yann@2446: bool yann@2921: prompt "2.6.27.62 (longterm)" yann@2446: help yann@2446: The Linux 2.6.27 tree is a "longterm" maintenance branch. yann@2446: yann@2446: It is intended to fill the niche for users who are not using distribution yann@2446: kernels but want to use a regression-free kernel for a longer time. yann@2446: yann@2446: Critical bug fixes to later 2.6 releases are often ported to this branch yann@2446: which makes 2.6.27 a very useful base for many embedded developers seeking yann@2446: stable APIs or those who do not need the latest bleeding edge features. yann@2446: yann@2446: ... and no, this kernel has not undergone any specific QA testing. yann@2446: yann@2446: See the original announcement by Adrian Bunk in the following mailing list yann@2446: entry: yann@2446: http://marc.info/?l=linux-kernel&m=122375909403298&w=4 yann@2446: yann@2446: It is now maintained by Greg Kroah-Hartman, see this mailing list entry: yann@2446: http://marc.info/?l=linux-kernel&m=129133701916793&w=4 yann@2446: yann@2446: config KERNEL_LINUX_CUSTOM yann@2446: bool sinseman44@2680: prompt "custom tarball or directory" yann@2446: help sinseman44@2680: Use a local tarball or local kernel directory of a complete kernel source tree. yann@2446: sinseman44@2680: config KERNEL_LINUX_CUSTOM_LOCATION yann@2446: string sinseman44@2680: prompt "Path to custom source, tarball or directory" yann@2446: depends on KERNEL_LINUX_CUSTOM yann@2446: help sinseman44@2680: Enter here the path to the tarball of your full kernel tree or sinseman44@2680: kernel directory yann@2446: yann@2446: endchoice yann@2446: yann@2446: config KERNEL_VERSION yann@2446: string yann@2446: # Don't remove next line yann@2446: # CT_INSERT_VERSION_STRING_BELOW benoit@3017: default "3.5" if KERNEL_V_3_5 yann@3020: default "3.4.7" if KERNEL_V_3_4_7 yann@2993: default "3.3.8" if KERNEL_V_3_3_8 yann@3026: default "3.2.25" if KERNEL_V_3_2_25 yann@2852: default "3.1.10" if KERNEL_V_3_1_10 yann@3026: default "3.0.39" if KERNEL_V_3_0_39 yann@2596: default "2.6.39.4" if KERNEL_V_2_6_39_4 bryanhundven@2513: default "2.6.38.8" if KERNEL_V_2_6_38_8 yann@2446: default "2.6.37.6" if KERNEL_V_2_6_37_6 yann@2446: default "2.6.36.4" if KERNEL_V_2_6_36_4 yann@2741: default "2.6.33.20" if KERNEL_V_2_6_33_20 yann@2921: default "2.6.32.59" if KERNEL_V_2_6_32_59 yann@2446: default "2.6.31.14" if KERNEL_V_2_6_31_14 yann@2921: default "2.6.27.62" if KERNEL_V_2_6_27_62 yann@2603: default "custom" if KERNEL_LINUX_CUSTOM yann@2446: yann@2603: endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS yann@2446: yann@2446: if KERNEL_LINUX_USE_CUSTOM_HEADERS yann@2446: yann@2446: config KERNEL_LINUX_CUSTOM_PATH yann@2446: string yann@2446: prompt "Path to custom headers directory/tarball" yann@2446: help yann@2446: See KERNEL_LINUX_CUSTOM_IS_TARBALL, below. yann@2446: yann@2446: config KERNEL_LINUX_CUSTOM_IS_TARBALL yann@2446: bool yann@2446: prompt "This is a tarball" yann@2446: help yann@2446: If you say 'n' here, the path above is expected to point to a directory yann@2446: containing readily prepared headers yann@2446: yann@2446: If you say 'y' here, then the path above is expected to point to a yann@2446: tarball of such a directory. yann@2446: yann@2446: Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include, yann@2446: say 'n' here, and enter: /foo/bar/buz/my_hdrs below. yann@2446: yann@2446: Now, passing a tarball around is easier than passing a directory, so yann@2446: if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include, yann@2446: say 'y' here, and enter the path to this tarball below. yann@2446: yann@2446: endif # KERNEL_LINUX_USE_CUSTOM_HEADERS