yann@1345: # Linux kernel options yann@1345: yann@448: # Linux kernel options yann@448: yann@861: config KERNEL_linux yann@1500: select KERNEL_SUPPORTS_SHARED_LIBS yann@861: help yann@861: Build a toolchain targeting systems running Linux as a kernel. yann@861: yann@1345: choice yann@1345: bool yann@1345: prompt "Get kernel headers from:" yann@1345: yann@1345: config KERNEL_LINUX_INSTALL yann@1345: bool yann@1345: prompt "kernel's 'headers_install'" yann@1345: help yann@1345: This will make use of the new headers_install rule in recent kernels. yann@1345: This is most probably what you want to use. yann@1345: yann@1345: if KERNEL_LINUX_INSTALL yann@1345: yann@1345: choice yann@1345: bool yann@1345: prompt "Linux kernel version" yann@1535: # Don't remove next line yann@1535: # CT_INSERT_VERSION_BELOW yann@1345: lacombar@2062: config KERNEL_V_2_6_35 lacombar@2062: bool lacombar@2062: prompt "2.6.35" lacombar@2062: lacombar@2062: config KERNEL_V_2_6_34_2 lacombar@2062: bool lacombar@2062: prompt "2.6.34.2" lacombar@2062: lacombar@2062: config KERNEL_V_2_6_33_7 lacombar@2062: bool lacombar@2062: prompt "2.6.33.7" lacombar@2062: lacombar@2062: config KERNEL_V_2_6_32_17 yann@1790: bool lacombar@2062: prompt "2.6.32.17" yann@1665: js@2011: config KERNEL_V_2_6_31_14 jocke@1702: bool js@2011: prompt "2.6.31.14" yann@1534: lacombar@2062: config KERNEL_V_2_6_27_49 yann@1534: bool lacombar@2062: prompt "2.6.27.49 (long-term stable)" jocke@1702: help jocke@1702: The Linux 2.6.27 tree is the current "long-term stable" maintenance branch. jocke@1702: It is intended to fill the niche for users who are not using distribution jocke@1702: kernels but want to use a regression-free kernel for a longer time. jocke@1702: jocke@1702: Critical bug fixes to later 2.6 releases are often ported to this branch jocke@1702: which makes 2.6.27 a very useful base for many embedded developers seeking jocke@1702: stable APIs or those who do not need the latest bleeding edge features. jocke@1702: jocke@1702: ... and no, this kernel has not undergone any specific QA testing. jocke@1702: jocke@1702: See the original announcement by Adrian Bunk in the following mailing list jocke@1702: entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2 yann@1534: yann@1990: config KERNEL_LINUX_CUSTOM yann@1990: bool yann@1990: prompt "custom tarball" yann@1990: help yann@1990: Use a local tarball of a complete kernel source tree. yann@1990: yann@1990: config KERNEL_LINUX_CUSTOM_TARBALL yann@1990: string yann@1990: prompt "Path to custom tarball" yann@1990: depends on KERNEL_LINUX_CUSTOM yann@1990: help yann@1990: Enter here the path to the tarball of your full kernel tree. yann@1990: yann@1345: endchoice yann@1345: yann@1345: config KERNEL_VERSION yann@1345: string yann@1535: # Don't remove next line yann@1535: # CT_INSERT_VERSION_STRING_BELOW lacombar@2062: default "2.6.35" if KERNEL_V_2_6_35 lacombar@2062: default "2.6.34.2" if KERNEL_V_2_6_34_2 lacombar@2062: default "2.6.33.7" if KERNEL_V_2_6_33_7 lacombar@2062: default "2.6.32.17" if KERNEL_V_2_6_32_17 js@2011: default "2.6.31.14" if KERNEL_V_2_6_31_14 lacombar@2062: default "2.6.27.49" if KERNEL_V_2_6_27_49 yann@1345: yann@1345: choice yann@1345: bool yann@1345: prompt "Kernel verbosity:" yann@1345: default KERNEL_LINUX_VERBOSITY_0 yann@1345: yann@1345: config KERNEL_LINUX_VERBOSITY_0 yann@1345: bool yann@1345: prompt "Simplified" yann@1345: help yann@1345: Print simplified command lines. yann@1345: yann@1345: config KERNEL_LINUX_VERBOSITY_1 yann@1345: bool yann@1345: prompt "Full commands" yann@1345: help yann@1345: Print full command lines. yann@1345: yann@1345: config KERNEL_LINUX_VERBOSITY_2 yann@1345: bool yann@1345: prompt "Exec reasons" yann@1345: help yann@1345: Print the reasons why a make target is rebuild. yann@1345: yann@1345: endchoice yann@1345: yann@1345: config KERNEL_LINUX_VERBOSE_LEVEL yann@1345: int yann@1345: default 0 if KERNEL_LINUX_VERBOSITY_0 yann@1345: default 1 if KERNEL_LINUX_VERBOSITY_1 yann@1345: default 2 if KERNEL_LINUX_VERBOSITY_2 yann@1345: yann@1989: config KERNEL_LINUX_INSTALL_CHECK yann@1989: bool yann@1989: prompt "Check installed headers" yann@1989: default y yann@1989: help yann@1989: If you are in doubt that installed headers are buggy, say 'Y' yann@1989: here to have an extra check passed onto the headers. yann@1989: yann@1989: endif # KERNEL_LINUX_INSTALL yann@1345: yann@1345: config KERNEL_LINUX_USE_CUSTOM_HEADERS yann@1345: bool yann@1990: prompt "pre-installed headers tree" yann@1345: help yann@1990: If you have some pre-installed kernel headers lying around, you can yann@1990: enter the path to these headers, below, they will be copied from yann@1990: there, and into the toolchain's sysroot. yann@1990: yann@1990: Note: yann@1990: This will *not* let you use a complete kernel tree! yann@1990: If you want to use your own full kernel tree, then you want to yann@1990: say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM. yann@1345: yann@1345: if KERNEL_LINUX_USE_CUSTOM_HEADERS yann@1345: yann@1345: config KERNEL_LINUX_CUSTOM_IS_TARBALL yann@1345: bool yann@1345: prompt "This is a tarball" yann@1345: default n yann@1345: help yann@1345: If you say 'n' here, the path below is expected to point to a directory yann@1345: containing readily prepared headers yann@1345: yann@1345: If you say 'y' here, then the path below is expected to point to a yann@1345: tarball of such a directory. yann@1345: yann@1345: Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include, yann@1345: say 'n' here, and enter: /foo/bar/buz/my_hdrs below. yann@1345: yann@1345: Now, passing a tarball around is easier than passing a directory, so yann@1345: if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include, yann@1345: say 'y' here, and enter the path to this tarball below. yann@1345: yann@1345: config KERNEL_LINUX_CUSTOM_PATH yann@1345: string yann@1345: prompt "Path to custom headers directory/tarball" yann@1345: help yann@1345: See KERNEL_LINUX_CUSTOM_IS_TARBALL, above. yann@1345: yann@1989: endif # KERNEL_LINUX_USE_CUSTOM_HEADERS yann@1345: yann@1345: endchoice