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
41 config KERNEL_V_2_6_39
45 config KERNEL_V_2_6_38_6
49 config KERNEL_V_2_6_38_5
53 config KERNEL_V_2_6_38_4
57 config KERNEL_V_2_6_38_3
61 config KERNEL_V_2_6_38_2
65 config KERNEL_V_2_6_38_1
69 config KERNEL_V_2_6_38
73 config KERNEL_V_2_6_37_6
77 config KERNEL_V_2_6_36_4
81 config KERNEL_V_2_6_35_13
83 prompt "2.6.35.13 (longterm)"
85 The Linux 2.6.35 tree is a "longterm" maintenance branch.
87 It is intended to fill the niche for users who are not using distribution
88 kernels but want to use a regression-free kernel for a longer time.
90 Critical bug fixes to later 2.6 releases are often ported to this branch
91 which makes 2.6.35 a very useful base for many embedded developers seeking
92 stable APIs or those who do not need the latest bleeding edge features.
94 ... and no, this kernel has not undergone any specific QA testing.
96 See the original announcement by Andi Kleen in the following mailing
98 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
100 config KERNEL_V_2_6_34_9
104 config KERNEL_V_2_6_33_13
108 config KERNEL_V_2_6_32_40
110 prompt "2.6.32.40 (longterm)"
112 The Linux 2.6.32 tree is a "longterm" maintenance branch.
114 It is intended to fill the niche for users who are not using distribution
115 kernels but want to use a regression-free kernel for a longer time.
117 Critical bug fixes to later 2.6 releases are often ported to this branch
118 which makes 2.6.32 a very useful base for many embedded developers seeking
119 stable APIs or those who do not need the latest bleeding edge features.
121 ... and no, this kernel has not undergone any specific QA testing.
123 See the original announcement by Greg Kroah-Hartman in the following
125 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
127 config KERNEL_V_2_6_31_14
131 config KERNEL_V_2_6_27_59
133 prompt "2.6.27.59 (longterm)"
135 The Linux 2.6.27 tree is a "longterm" maintenance branch.
137 It is intended to fill the niche for users who are not using distribution
138 kernels but want to use a regression-free kernel for a longer time.
140 Critical bug fixes to later 2.6 releases are often ported to this branch
141 which makes 2.6.27 a very useful base for many embedded developers seeking
142 stable APIs or those who do not need the latest bleeding edge features.
144 ... and no, this kernel has not undergone any specific QA testing.
146 See the original announcement by Adrian Bunk in the following mailing list
148 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
150 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
151 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
153 config KERNEL_LINUX_CUSTOM
155 prompt "custom tarball"
157 Use a local tarball of a complete kernel source tree.
159 config KERNEL_LINUX_CUSTOM_TARBALL
161 prompt "Path to custom tarball"
162 depends on KERNEL_LINUX_CUSTOM
164 Enter here the path to the tarball of your full kernel tree.
168 config KERNEL_VERSION
170 # Don't remove next line
171 # CT_INSERT_VERSION_STRING_BELOW
172 default "2.6.39" if KERNEL_V_2_6_39
173 default "2.6.38.6" if KERNEL_V_2_6_38_6
174 default "2.6.38.5" if KERNEL_V_2_6_38_5
175 default "2.6.38.4" if KERNEL_V_2_6_38_4
176 default "2.6.38.3" if KERNEL_V_2_6_38_3
177 default "2.6.38.2" if KERNEL_V_2_6_38_2
178 default "2.6.38.1" if KERNEL_V_2_6_38_1
179 default "2.6.38" if KERNEL_V_2_6_38
180 default "2.6.37.6" if KERNEL_V_2_6_37_6
181 default "2.6.36.4" if KERNEL_V_2_6_36_4
182 default "2.6.35.13" if KERNEL_V_2_6_35_13
183 default "2.6.34.9" if KERNEL_V_2_6_34_9
184 default "2.6.33.13" if KERNEL_V_2_6_33_13
185 default "2.6.32.40" if KERNEL_V_2_6_32_40
186 default "2.6.31.14" if KERNEL_V_2_6_31_14
187 default "2.6.27.59" if KERNEL_V_2_6_27_59
189 endif # KERNEL_LINUX_INSTALL
191 if KERNEL_LINUX_USE_CUSTOM_HEADERS
193 config KERNEL_LINUX_CUSTOM_PATH
195 prompt "Path to custom headers directory/tarball"
197 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
199 config KERNEL_LINUX_CUSTOM_IS_TARBALL
201 prompt "This is a tarball"
204 If you say 'n' here, the path above is expected to point to a directory
205 containing readily prepared headers
207 If you say 'y' here, then the path above is expected to point to a
208 tarball of such a directory.
210 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
211 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
213 Now, passing a tarball around is easier than passing a directory, so
214 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
215 say 'y' here, and enter the path to this tarball below.
217 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS