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
77 config KERNEL_V_2_6_39
81 config KERNEL_V_2_6_38
85 config KERNEL_V_2_6_37
89 config KERNEL_V_2_6_36
93 config KERNEL_V_2_6_33
97 This is primarily for the use of those people who are stuck using the
98 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
99 is welcome to use this one as well.
101 config KERNEL_V_2_6_32
103 prompt "2.6.32.60 (longterm)"
105 The Linux 2.6.32 tree is a "longterm" maintenance branch.
107 It is intended to fill the niche for users who are not using distribution
108 kernels but want to use a regression-free kernel for a longer time.
110 Critical bug fixes to later 2.6 releases are often ported to this branch
111 which makes 2.6.32 a very useful base for many embedded developers seeking
112 stable APIs or those who do not need the latest bleeding edge features.
114 ... and no, this kernel has not undergone any specific QA testing.
116 See the original announcement by Greg Kroah-Hartman in the following
118 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
120 config KERNEL_V_2_6_31
124 config KERNEL_V_2_6_27
126 prompt "2.6.27.62 (longterm)"
128 The Linux 2.6.27 tree is a "longterm" maintenance branch.
130 It is intended to fill the niche for users who are not using distribution
131 kernels but want to use a regression-free kernel for a longer time.
133 Critical bug fixes to later 2.6 releases are often ported to this branch
134 which makes 2.6.27 a very useful base for many embedded developers seeking
135 stable APIs or those who do not need the latest bleeding edge features.
137 ... and no, this kernel has not undergone any specific QA testing.
139 See the original announcement by Adrian Bunk in the following mailing list
141 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
143 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
144 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
146 config KERNEL_LINUX_CUSTOM
148 prompt "custom tarball or directory"
150 Use a local tarball or local kernel directory of a complete kernel source tree.
152 config KERNEL_LINUX_CUSTOM_LOCATION
154 prompt "Path to custom source, tarball or directory"
155 depends on KERNEL_LINUX_CUSTOM
157 Enter here the path to the tarball of your full kernel tree or
162 config KERNEL_VERSION
164 # Don't remove next line
165 # CT_INSERT_VERSION_STRING_BELOW
166 default "3.8.3" if KERNEL_V_3_8_3
167 default "3.8.2" if KERNEL_V_3_8_2
168 default "3.8.1" if KERNEL_V_3_8_1
169 default "3.8" if KERNEL_V_3_8
170 default "3.7.10" if KERNEL_V_3_7
171 default "3.6.11" if KERNEL_V_3_6
172 default "3.5.7" if KERNEL_V_3_5
173 default "3.4.36" if KERNEL_V_3_4
174 default "3.3.8" if KERNEL_V_3_3
175 default "3.2.40" if KERNEL_V_3_2
176 default "3.1.10" if KERNEL_V_3_1
177 default "3.0.69" if KERNEL_V_3_0
178 default "2.6.39.4" if KERNEL_V_2_6_39
179 default "2.6.38.8" if KERNEL_V_2_6_38
180 default "2.6.37.6" if KERNEL_V_2_6_37
181 default "2.6.36.4" if KERNEL_V_2_6_36
182 default "2.6.33.20" if KERNEL_V_2_6_33
183 default "2.6.32.60" if KERNEL_V_2_6_32
184 default "2.6.31.14" if KERNEL_V_2_6_31
185 default "2.6.27.62" if KERNEL_V_2_6_27
186 default "custom" if KERNEL_LINUX_CUSTOM
188 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
190 if KERNEL_LINUX_USE_CUSTOM_HEADERS
192 config KERNEL_LINUX_CUSTOM_PATH
194 prompt "Path to custom headers directory/tarball"
196 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
198 config KERNEL_LINUX_CUSTOM_IS_TARBALL
200 prompt "This is a tarball"
202 If you say 'n' here, the path above is expected to point to a directory
203 containing readily prepared headers
205 If you say 'y' here, then the path above is expected to point to a
206 tarball of such a directory.
208 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
209 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
211 Now, passing a tarball around is easier than passing a directory, so
212 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
213 say 'y' here, and enter the path to this tarball below.
215 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS