3 ## select KERNEL_SUPPORTS_SHARED_LIBS
5 ## help Build a toolchain targeting systems running Linux as a kernel.
9 prompt "Get kernel headers from:"
11 config KERNEL_LINUX_INSTALL
13 prompt "kernel's 'headers_install'"
15 This will make use of the new headers_install rule in recent kernels.
16 This is most probably what you want to use.
18 config KERNEL_LINUX_USE_CUSTOM_HEADERS
20 prompt "pre-installed headers tree"
22 If you have some pre-installed kernel headers lying around, you can
23 enter the path to these headers, below, they will be copied from
24 there, and into the toolchain's sysroot.
27 This will *not* let you use a complete kernel tree!
28 If you want to use your own full kernel tree, then you want to
29 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
33 if KERNEL_LINUX_INSTALL
37 prompt "Linux kernel version"
38 # Don't remove next line
39 # CT_INSERT_VERSION_BELOW
49 config KERNEL_V_2_6_39_4
53 config KERNEL_V_2_6_38_8
57 config KERNEL_V_2_6_37_6
61 config KERNEL_V_2_6_36_4
65 config KERNEL_V_2_6_35_14
67 prompt "2.6.35.14 (longterm)"
69 The Linux 2.6.35 tree is a "longterm" maintenance branch.
71 It is intended to fill the niche for users who are not using distribution
72 kernels but want to use a regression-free kernel for a longer time.
74 Critical bug fixes to later 2.6 releases are often ported to this branch
75 which makes 2.6.35 a very useful base for many embedded developers seeking
76 stable APIs or those who do not need the latest bleeding edge features.
78 ... and no, this kernel has not undergone any specific QA testing.
80 See the original announcement by Andi Kleen in the following mailing
82 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
84 config KERNEL_V_2_6_34_10
88 config KERNEL_V_2_6_33_17
92 This is primarily for the use of those people who are stuck using the
93 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
94 is welcome to use this one as well.
96 config KERNEL_V_2_6_32_44
98 prompt "2.6.32.44 (longterm)"
100 The Linux 2.6.32 tree is a "longterm" maintenance branch.
102 It is intended to fill the niche for users who are not using distribution
103 kernels but want to use a regression-free kernel for a longer time.
105 Critical bug fixes to later 2.6 releases are often ported to this branch
106 which makes 2.6.32 a very useful base for many embedded developers seeking
107 stable APIs or those who do not need the latest bleeding edge features.
109 ... and no, this kernel has not undergone any specific QA testing.
111 See the original announcement by Greg Kroah-Hartman in the following
113 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
115 config KERNEL_V_2_6_31_14
119 config KERNEL_V_2_6_27_59
121 prompt "2.6.27.59 (longterm)"
123 The Linux 2.6.27 tree is a "longterm" maintenance branch.
125 It is intended to fill the niche for users who are not using distribution
126 kernels but want to use a regression-free kernel for a longer time.
128 Critical bug fixes to later 2.6 releases are often ported to this branch
129 which makes 2.6.27 a very useful base for many embedded developers seeking
130 stable APIs or those who do not need the latest bleeding edge features.
132 ... and no, this kernel has not undergone any specific QA testing.
134 See the original announcement by Adrian Bunk in the following mailing list
136 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
138 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
139 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
141 config KERNEL_LINUX_CUSTOM
143 prompt "custom tarball"
145 Use a local tarball of a complete kernel source tree.
147 config KERNEL_LINUX_CUSTOM_TARBALL
149 prompt "Path to custom tarball"
150 depends on KERNEL_LINUX_CUSTOM
152 Enter here the path to the tarball of your full kernel tree.
156 config KERNEL_VERSION
158 # Don't remove next line
159 # CT_INSERT_VERSION_STRING_BELOW
160 default "3.0.1" if KERNEL_V_3_0_1
161 default "3.0" if KERNEL_V_3_0
162 default "2.6.39.4" if KERNEL_V_2_6_39_4
163 default "2.6.38.8" if KERNEL_V_2_6_38_8
164 default "2.6.37.6" if KERNEL_V_2_6_37_6
165 default "2.6.36.4" if KERNEL_V_2_6_36_4
166 default "2.6.35.14" if KERNEL_V_2_6_35_14
167 default "2.6.34.10" if KERNEL_V_2_6_34_10
168 default "2.6.33.17" if KERNEL_V_2_6_33_17
169 default "2.6.32.44" if KERNEL_V_2_6_32_44
170 default "2.6.31.14" if KERNEL_V_2_6_31_14
171 default "2.6.27.59" if KERNEL_V_2_6_27_59
173 endif # KERNEL_LINUX_INSTALL
175 if KERNEL_LINUX_USE_CUSTOM_HEADERS
177 config KERNEL_LINUX_CUSTOM_PATH
179 prompt "Path to custom headers directory/tarball"
181 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
183 config KERNEL_LINUX_CUSTOM_IS_TARBALL
185 prompt "This is a tarball"
187 If you say 'n' here, the path above is expected to point to a directory
188 containing readily prepared headers
190 If you say 'y' here, then the path above is expected to point to a
191 tarball of such a directory.
193 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
194 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
196 Now, passing a tarball around is easier than passing a directory, so
197 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
198 say 'y' here, and enter the path to this tarball below.
200 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS