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