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
61 config KERNEL_V_3_4_18
69 config KERNEL_V_3_2_33
73 config KERNEL_V_3_1_10
77 config KERNEL_V_3_0_51
81 config KERNEL_V_2_6_39_4
85 config KERNEL_V_2_6_38_8
89 config KERNEL_V_2_6_37_6
93 config KERNEL_V_2_6_36_4
97 config KERNEL_V_2_6_33_20
101 This is primarily for the use of those people who are stuck using the
102 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
103 is welcome to use this one as well.
105 config KERNEL_V_2_6_32_60
107 prompt "2.6.32.60 (longterm)"
109 The Linux 2.6.32 tree is a "longterm" maintenance branch.
111 It is intended to fill the niche for users who are not using distribution
112 kernels but want to use a regression-free kernel for a longer time.
114 Critical bug fixes to later 2.6 releases are often ported to this branch
115 which makes 2.6.32 a very useful base for many embedded developers seeking
116 stable APIs or those who do not need the latest bleeding edge features.
118 ... and no, this kernel has not undergone any specific QA testing.
120 See the original announcement by Greg Kroah-Hartman in the following
122 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
124 config KERNEL_V_2_6_31_14
128 config KERNEL_V_2_6_27_62
130 prompt "2.6.27.62 (longterm)"
132 The Linux 2.6.27 tree is a "longterm" maintenance branch.
134 It is intended to fill the niche for users who are not using distribution
135 kernels but want to use a regression-free kernel for a longer time.
137 Critical bug fixes to later 2.6 releases are often ported to this branch
138 which makes 2.6.27 a very useful base for many embedded developers seeking
139 stable APIs or those who do not need the latest bleeding edge features.
141 ... and no, this kernel has not undergone any specific QA testing.
143 See the original announcement by Adrian Bunk in the following mailing list
145 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
147 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
148 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
150 config KERNEL_LINUX_CUSTOM
152 prompt "custom tarball or directory"
154 Use a local tarball or local kernel directory of a complete kernel source tree.
156 config KERNEL_LINUX_CUSTOM_LOCATION
158 prompt "Path to custom source, tarball or directory"
159 depends on KERNEL_LINUX_CUSTOM
161 Enter here the path to the tarball of your full kernel tree or
166 config KERNEL_VERSION
168 # Don't remove next line
169 # CT_INSERT_VERSION_STRING_BELOW
170 default "3.6.6" if KERNEL_V_3_6_6
171 default "3.6.5" if KERNEL_V_3_6_5
172 default "3.6.4" if KERNEL_V_3_6_4
173 default "3.6.3" if KERNEL_V_3_6_3
174 default "3.6.2" if KERNEL_V_3_6_2
175 default "3.6.1" if KERNEL_V_3_6_1
176 default "3.6" if KERNEL_V_3_6
177 default "3.5.7" if KERNEL_V_3_5_7
178 default "3.4.18" if KERNEL_V_3_4_18
179 default "3.3.8" if KERNEL_V_3_3_8
180 default "3.2.33" if KERNEL_V_3_2_33
181 default "3.1.10" if KERNEL_V_3_1_10
182 default "3.0.51" if KERNEL_V_3_0_51
183 default "2.6.39.4" if KERNEL_V_2_6_39_4
184 default "2.6.38.8" if KERNEL_V_2_6_38_8
185 default "2.6.37.6" if KERNEL_V_2_6_37_6
186 default "2.6.36.4" if KERNEL_V_2_6_36_4
187 default "2.6.33.20" if KERNEL_V_2_6_33_20
188 default "2.6.32.60" if KERNEL_V_2_6_32_60
189 default "2.6.31.14" if KERNEL_V_2_6_31_14
190 default "2.6.27.62" if KERNEL_V_2_6_27_62
191 default "custom" if KERNEL_LINUX_CUSTOM
193 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
195 if KERNEL_LINUX_USE_CUSTOM_HEADERS
197 config KERNEL_LINUX_CUSTOM_PATH
199 prompt "Path to custom headers directory/tarball"
201 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
203 config KERNEL_LINUX_CUSTOM_IS_TARBALL
205 prompt "This is a tarball"
207 If you say 'n' here, the path above is expected to point to a directory
208 containing readily prepared headers
210 If you say 'y' here, then the path above is expected to point to a
211 tarball of such a directory.
213 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
214 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
216 Now, passing a tarball around is easier than passing a directory, so
217 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
218 say 'y' here, and enter the path to this tarball below.
220 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS