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
69 config KERNEL_V_2_6_39
73 config KERNEL_V_2_6_38
77 config KERNEL_V_2_6_37
81 config KERNEL_V_2_6_36
85 config KERNEL_V_2_6_33
89 This is primarily for the use of those people who are stuck using the
90 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
91 is welcome to use this one as well.
93 config KERNEL_V_2_6_32
95 prompt "2.6.32.60 (longterm)"
97 The Linux 2.6.32 tree is a "longterm" maintenance branch.
99 It is intended to fill the niche for users who are not using distribution
100 kernels but want to use a regression-free kernel for a longer time.
102 Critical bug fixes to later 2.6 releases are often ported to this branch
103 which makes 2.6.32 a very useful base for many embedded developers seeking
104 stable APIs or those who do not need the latest bleeding edge features.
106 ... and no, this kernel has not undergone any specific QA testing.
108 See the original announcement by Greg Kroah-Hartman in the following
110 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
112 config KERNEL_V_2_6_31
116 config KERNEL_V_2_6_27
118 prompt "2.6.27.62 (longterm)"
120 The Linux 2.6.27 tree is a "longterm" maintenance branch.
122 It is intended to fill the niche for users who are not using distribution
123 kernels but want to use a regression-free kernel for a longer time.
125 Critical bug fixes to later 2.6 releases are often ported to this branch
126 which makes 2.6.27 a very useful base for many embedded developers seeking
127 stable APIs or those who do not need the latest bleeding edge features.
129 ... and no, this kernel has not undergone any specific QA testing.
131 See the original announcement by Adrian Bunk in the following mailing list
133 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
135 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
136 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
138 config KERNEL_LINUX_CUSTOM
140 prompt "custom tarball or directory"
142 Use a local tarball or local kernel directory of a complete kernel source tree.
144 config KERNEL_LINUX_CUSTOM_LOCATION
146 prompt "Path to custom source, tarball or directory"
147 depends on KERNEL_LINUX_CUSTOM
149 Enter here the path to the tarball of your full kernel tree or
154 config KERNEL_VERSION
156 # Don't remove next line
157 # CT_INSERT_VERSION_STRING_BELOW
158 default "3.9" if KERNEL_V_3_9
159 default "3.8.11" if KERNEL_V_3_8
160 default "3.7.10" if KERNEL_V_3_7
161 default "3.6.11" if KERNEL_V_3_6
162 default "3.5.7" if KERNEL_V_3_5
163 default "3.4.43" if KERNEL_V_3_4
164 default "3.3.8" if KERNEL_V_3_3
165 default "3.2.44" if KERNEL_V_3_2
166 default "3.1.10" if KERNEL_V_3_1
167 default "3.0.76" if KERNEL_V_3_0
168 default "2.6.39.4" if KERNEL_V_2_6_39
169 default "2.6.38.8" if KERNEL_V_2_6_38
170 default "2.6.37.6" if KERNEL_V_2_6_37
171 default "2.6.36.4" if KERNEL_V_2_6_36
172 default "2.6.33.20" if KERNEL_V_2_6_33
173 default "2.6.32.60" if KERNEL_V_2_6_32
174 default "2.6.31.14" if KERNEL_V_2_6_31
175 default "2.6.27.62" if KERNEL_V_2_6_27
176 default "custom" if KERNEL_LINUX_CUSTOM
178 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
180 if KERNEL_LINUX_USE_CUSTOM_HEADERS
182 config KERNEL_LINUX_CUSTOM_PATH
184 prompt "Path to custom headers directory/tarball"
186 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
188 config KERNEL_LINUX_CUSTOM_IS_TARBALL
190 prompt "This is a tarball"
192 If you say 'n' here, the path above is expected to point to a directory
193 containing readily prepared headers
195 If you say 'y' here, then the path above is expected to point to a
196 tarball of such a directory.
198 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
199 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
201 Now, passing a tarball around is easier than passing a directory, so
202 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
203 say 'y' here, and enter the path to this tarball below.
205 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS