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
45 config KERNEL_V_2_6_39_3
49 config KERNEL_V_2_6_39_2
53 config KERNEL_V_2_6_39_1
57 config KERNEL_V_2_6_39
61 config KERNEL_V_2_6_38_8
65 config KERNEL_V_2_6_37_6
69 config KERNEL_V_2_6_36_4
73 config KERNEL_V_2_6_35_13
75 prompt "2.6.35.13 (longterm)"
77 The Linux 2.6.35 tree is a "longterm" maintenance branch.
79 It is intended to fill the niche for users who are not using distribution
80 kernels but want to use a regression-free kernel for a longer time.
82 Critical bug fixes to later 2.6 releases are often ported to this branch
83 which makes 2.6.35 a very useful base for many embedded developers seeking
84 stable APIs or those who do not need the latest bleeding edge features.
86 ... and no, this kernel has not undergone any specific QA testing.
88 See the original announcement by Andi Kleen in the following mailing
90 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
92 config KERNEL_V_2_6_34_10
96 config KERNEL_V_2_6_33_16
100 config KERNEL_V_2_6_32_43
102 prompt "2.6.32.43 (longterm)"
104 The Linux 2.6.32 tree is a "longterm" maintenance branch.
106 It is intended to fill the niche for users who are not using distribution
107 kernels but want to use a regression-free kernel for a longer time.
109 Critical bug fixes to later 2.6 releases are often ported to this branch
110 which makes 2.6.32 a very useful base for many embedded developers seeking
111 stable APIs or those who do not need the latest bleeding edge features.
113 ... and no, this kernel has not undergone any specific QA testing.
115 See the original announcement by Greg Kroah-Hartman in the following
117 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
119 config KERNEL_V_2_6_31_14
123 config KERNEL_V_2_6_27_59
125 prompt "2.6.27.59 (longterm)"
127 The Linux 2.6.27 tree is a "longterm" maintenance branch.
129 It is intended to fill the niche for users who are not using distribution
130 kernels but want to use a regression-free kernel for a longer time.
132 Critical bug fixes to later 2.6 releases are often ported to this branch
133 which makes 2.6.27 a very useful base for many embedded developers seeking
134 stable APIs or those who do not need the latest bleeding edge features.
136 ... and no, this kernel has not undergone any specific QA testing.
138 See the original announcement by Adrian Bunk in the following mailing list
140 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
142 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
143 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
145 config KERNEL_LINUX_CUSTOM
147 prompt "custom tarball"
149 Use a local tarball of a complete kernel source tree.
151 config KERNEL_LINUX_CUSTOM_TARBALL
153 prompt "Path to custom tarball"
154 depends on KERNEL_LINUX_CUSTOM
156 Enter here the path to the tarball of your full kernel tree.
160 config KERNEL_VERSION
162 # Don't remove next line
163 # CT_INSERT_VERSION_STRING_BELOW
164 default "3.0" if KERNEL_V_3_0
165 default "2.6.39.3" if KERNEL_V_2_6_39_3
166 default "2.6.39.2" if KERNEL_V_2_6_39_2
167 default "2.6.39.1" if KERNEL_V_2_6_39_1
168 default "2.6.39" if KERNEL_V_2_6_39
169 default "2.6.38.8" if KERNEL_V_2_6_38_8
170 default "2.6.37.6" if KERNEL_V_2_6_37_6
171 default "2.6.36.4" if KERNEL_V_2_6_36_4
172 default "2.6.35.13" if KERNEL_V_2_6_35_13
173 default "2.6.34.10" if KERNEL_V_2_6_34_10
174 default "2.6.33.16" if KERNEL_V_2_6_33_16
175 default "2.6.32.43" if KERNEL_V_2_6_32_43
176 default "2.6.31.14" if KERNEL_V_2_6_31_14
177 default "2.6.27.59" if KERNEL_V_2_6_27_59
179 endif # KERNEL_LINUX_INSTALL
181 if KERNEL_LINUX_USE_CUSTOM_HEADERS
183 config KERNEL_LINUX_CUSTOM_PATH
185 prompt "Path to custom headers directory/tarball"
187 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
189 config KERNEL_LINUX_CUSTOM_IS_TARBALL
191 prompt "This is a tarball"
193 If you say 'n' here, the path above is expected to point to a directory
194 containing readily prepared headers
196 If you say 'y' here, then the path above is expected to point to a
197 tarball of such a directory.
199 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
200 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
202 Now, passing a tarball around is easier than passing a directory, so
203 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
204 say 'y' here, and enter the path to this tarball below.
206 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS