5 prompt "Get kernel headers from:"
7 config KERNEL_LINUX_INSTALL
9 prompt "kernel's 'headers_install'"
11 This will make use of the new headers_install rule in recent kernels.
12 This is most probably what you want to use.
14 config KERNEL_LINUX_USE_CUSTOM_HEADERS
16 prompt "pre-installed headers tree"
18 If you have some pre-installed kernel headers lying around, you can
19 enter the path to these headers, below, they will be copied from
20 there, and into the toolchain's sysroot.
23 This will *not* let you use a complete kernel tree!
24 If you want to use your own full kernel tree, then you want to
25 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
29 if KERNEL_LINUX_INSTALL
33 prompt "Linux kernel version"
34 # Don't remove next line
35 # CT_INSERT_VERSION_BELOW
37 config KERNEL_V_2_6_38_4
41 config KERNEL_V_2_6_38_3
45 config KERNEL_V_2_6_38_2
49 config KERNEL_V_2_6_38_1
53 config KERNEL_V_2_6_38
57 config KERNEL_V_2_6_37_6
61 config KERNEL_V_2_6_36_4
65 config KERNEL_V_2_6_35_13
67 prompt "2.6.35.13 (longterm)"
69 The Linux 2.6.35 tree is a "longterm" maintenance branch.
71 It is intended to fill the niche for users who are not using distribution
72 kernels but want to use a regression-free kernel for a longer time.
74 Critical bug fixes to later 2.6 releases are often ported to this branch
75 which makes 2.6.35 a very useful base for many embedded developers seeking
76 stable APIs or those who do not need the latest bleeding edge features.
78 ... and no, this kernel has not undergone any specific QA testing.
80 See the original announcement by Andi Kleen in the following mailing
82 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
84 config KERNEL_V_2_6_34_9
88 config KERNEL_V_2_6_33_12
92 config KERNEL_V_2_6_32_39
94 prompt "2.6.32.39 (longterm)"
96 The Linux 2.6.32 tree is a "longterm" maintenance branch.
98 It is intended to fill the niche for users who are not using distribution
99 kernels but want to use a regression-free kernel for a longer time.
101 Critical bug fixes to later 2.6 releases are often ported to this branch
102 which makes 2.6.32 a very useful base for many embedded developers seeking
103 stable APIs or those who do not need the latest bleeding edge features.
105 ... and no, this kernel has not undergone any specific QA testing.
107 See the original announcement by Greg Kroah-Hartman in the following
109 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
111 config KERNEL_V_2_6_31_14
115 config KERNEL_V_2_6_27_58
117 prompt "2.6.27.58 (longterm)"
119 The Linux 2.6.27 tree is a "longterm" maintenance branch.
121 It is intended to fill the niche for users who are not using distribution
122 kernels but want to use a regression-free kernel for a longer time.
124 Critical bug fixes to later 2.6 releases are often ported to this branch
125 which makes 2.6.27 a very useful base for many embedded developers seeking
126 stable APIs or those who do not need the latest bleeding edge features.
128 ... and no, this kernel has not undergone any specific QA testing.
130 See the original announcement by Adrian Bunk in the following mailing list
132 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
134 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
135 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
137 config KERNEL_LINUX_CUSTOM
139 prompt "custom tarball"
141 Use a local tarball of a complete kernel source tree.
143 config KERNEL_LINUX_CUSTOM_TARBALL
145 prompt "Path to custom tarball"
146 depends on KERNEL_LINUX_CUSTOM
148 Enter here the path to the tarball of your full kernel tree.
152 config KERNEL_VERSION
154 # Don't remove next line
155 # CT_INSERT_VERSION_STRING_BELOW
156 default "2.6.38.4" if KERNEL_V_2_6_38_4
157 default "2.6.38.3" if KERNEL_V_2_6_38_3
158 default "2.6.38.2" if KERNEL_V_2_6_38_2
159 default "2.6.38.1" if KERNEL_V_2_6_38_1
160 default "2.6.38" if KERNEL_V_2_6_38
161 default "2.6.37.6" if KERNEL_V_2_6_37_6
162 default "2.6.36.4" if KERNEL_V_2_6_36_4
163 default "2.6.35.13" if KERNEL_V_2_6_35_13
164 default "2.6.34.9" if KERNEL_V_2_6_34_9
165 default "2.6.33.12" if KERNEL_V_2_6_33_12
166 default "2.6.32.39" if KERNEL_V_2_6_32_39
167 default "2.6.31.14" if KERNEL_V_2_6_31_14
168 default "2.6.27.58" if KERNEL_V_2_6_27_58
172 prompt "Kernel verbosity:"
173 default KERNEL_LINUX_VERBOSITY_0
175 config KERNEL_LINUX_VERBOSITY_0
179 Print simplified command lines.
181 config KERNEL_LINUX_VERBOSITY_1
183 prompt "Full commands"
185 Print full command lines.
187 config KERNEL_LINUX_VERBOSITY_2
189 prompt "Exec reasons"
191 Print the reasons why a make target is rebuild.
195 config KERNEL_LINUX_VERBOSE_LEVEL
197 default 0 if KERNEL_LINUX_VERBOSITY_0
198 default 1 if KERNEL_LINUX_VERBOSITY_1
199 default 2 if KERNEL_LINUX_VERBOSITY_2
201 config KERNEL_LINUX_INSTALL_CHECK
203 prompt "Check installed headers"
206 If you are in doubt that installed headers are buggy, say 'Y'
207 here to have an extra check passed onto the headers.
209 endif # KERNEL_LINUX_INSTALL
211 if KERNEL_LINUX_USE_CUSTOM_HEADERS
213 config KERNEL_LINUX_CUSTOM_IS_TARBALL
215 prompt "This is a tarball"
218 If you say 'n' here, the path below is expected to point to a directory
219 containing readily prepared headers
221 If you say 'y' here, then the path below is expected to point to a
222 tarball of such a directory.
224 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
225 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
227 Now, passing a tarball around is easier than passing a directory, so
228 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
229 say 'y' here, and enter the path to this tarball below.
231 config KERNEL_LINUX_CUSTOM_PATH
233 prompt "Path to custom headers directory/tarball"
235 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
237 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS