3 ## select KERNEL_SUPPORTS_SHARED_LIBS
5 ## help Build a toolchain targeting systems running Linux as a kernel.
7 config KERNEL_LINUX_USE_CUSTOM_HEADERS
9 prompt "Use pre-installed headers tree (OBSOLETE)"
12 If you have some pre-installed kernel headers lying around, you can
13 enter the path to these headers, below, they will be copied from
14 there, and into the toolchain's sysroot.
17 This will *not* let you use a complete kernel tree!
18 If you want to use your own full kernel tree, then you want to say 'N'
19 here, and select KERNEL_LINUX_CUSTOM, in the versions list, below.
21 if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
25 prompt "Linux kernel version"
26 # Don't remove next line
27 # CT_INSERT_VERSION_BELOW
93 config KERNEL_V_2_6_39
97 config KERNEL_V_2_6_38
101 config KERNEL_V_2_6_37
105 config KERNEL_V_2_6_36
109 config KERNEL_V_2_6_33
113 This is primarily for the use of those people who are stuck using the
114 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
115 is welcome to use this one as well.
117 config KERNEL_V_2_6_32
119 prompt "2.6.32.60 (longterm)"
121 The Linux 2.6.32 tree is a "longterm" maintenance branch.
123 It is intended to fill the niche for users who are not using distribution
124 kernels but want to use a regression-free kernel for a longer time.
126 Critical bug fixes to later 2.6 releases are often ported to this branch
127 which makes 2.6.32 a very useful base for many embedded developers seeking
128 stable APIs or those who do not need the latest bleeding edge features.
130 ... and no, this kernel has not undergone any specific QA testing.
132 See the original announcement by Greg Kroah-Hartman in the following
134 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
136 config KERNEL_V_2_6_31
140 config KERNEL_V_2_6_27
142 prompt "2.6.27.62 (longterm)"
144 The Linux 2.6.27 tree is a "longterm" maintenance branch.
146 It is intended to fill the niche for users who are not using distribution
147 kernels but want to use a regression-free kernel for a longer time.
149 Critical bug fixes to later 2.6 releases are often ported to this branch
150 which makes 2.6.27 a very useful base for many embedded developers seeking
151 stable APIs or those who do not need the latest bleeding edge features.
153 ... and no, this kernel has not undergone any specific QA testing.
155 See the original announcement by Adrian Bunk in the following mailing list
157 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
159 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
160 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
162 config KERNEL_LINUX_CUSTOM
164 prompt "custom tarball or directory"
166 Use a local tarball or local kernel directory of a complete kernel source tree.
168 config KERNEL_LINUX_CUSTOM_LOCATION
170 prompt "Path to custom source, tarball or directory"
171 depends on KERNEL_LINUX_CUSTOM
173 Enter here the path to the tarball of your full kernel tree or
178 config KERNEL_VERSION
180 # Don't remove next line
181 # CT_INSERT_VERSION_STRING_BELOW
182 default "3.8.7" if KERNEL_V_3_8_7
183 default "3.8.6" if KERNEL_V_3_8_6
184 default "3.8.5" if KERNEL_V_3_8_5
185 default "3.8.4" if KERNEL_V_3_8_4
186 default "3.8.3" if KERNEL_V_3_8_3
187 default "3.8.2" if KERNEL_V_3_8_2
188 default "3.8.1" if KERNEL_V_3_8_1
189 default "3.8" if KERNEL_V_3_8
190 default "3.7.10" if KERNEL_V_3_7
191 default "3.6.11" if KERNEL_V_3_6
192 default "3.5.7" if KERNEL_V_3_5
193 default "3.4.40" if KERNEL_V_3_4
194 default "3.3.8" if KERNEL_V_3_3
195 default "3.2.43" if KERNEL_V_3_2
196 default "3.1.10" if KERNEL_V_3_1
197 default "3.0.73" if KERNEL_V_3_0
198 default "2.6.39.4" if KERNEL_V_2_6_39
199 default "2.6.38.8" if KERNEL_V_2_6_38
200 default "2.6.37.6" if KERNEL_V_2_6_37
201 default "2.6.36.4" if KERNEL_V_2_6_36
202 default "2.6.33.20" if KERNEL_V_2_6_33
203 default "2.6.32.60" if KERNEL_V_2_6_32
204 default "2.6.31.14" if KERNEL_V_2_6_31
205 default "2.6.27.62" if KERNEL_V_2_6_27
206 default "custom" if KERNEL_LINUX_CUSTOM
208 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
210 if KERNEL_LINUX_USE_CUSTOM_HEADERS
212 config KERNEL_LINUX_CUSTOM_PATH
214 prompt "Path to custom headers directory/tarball"
216 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
218 config KERNEL_LINUX_CUSTOM_IS_TARBALL
220 prompt "This is a tarball"
222 If you say 'n' here, the path above is expected to point to a directory
223 containing readily prepared headers
225 If you say 'y' here, then the path above is expected to point to a
226 tarball of such a directory.
228 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
229 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
231 Now, passing a tarball around is easier than passing a directory, so
232 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
233 say 'y' here, and enter the path to this tarball below.
235 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS