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_3
41 config KERNEL_V_2_6_38_2
45 config KERNEL_V_2_6_38_1
49 config KERNEL_V_2_6_38
53 config KERNEL_V_2_6_37_6
57 config KERNEL_V_2_6_36_4
61 config KERNEL_V_2_6_35_12
63 prompt "2.6.35.12 (longterm)"
65 The Linux 2.6.35 tree is a "longterm" maintenance branch.
67 It is intended to fill the niche for users who are not using distribution
68 kernels but want to use a regression-free kernel for a longer time.
70 Critical bug fixes to later 2.6 releases are often ported to this branch
71 which makes 2.6.35 a very useful base for many embedded developers seeking
72 stable APIs or those who do not need the latest bleeding edge features.
74 ... and no, this kernel has not undergone any specific QA testing.
76 See the original announcement by Andi Kleen in the following mailing
78 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
80 config KERNEL_V_2_6_34_8
84 config KERNEL_V_2_6_33_11
88 config KERNEL_V_2_6_32_38
90 prompt "2.6.32.38 (longterm)"
92 The Linux 2.6.32 tree is a "longterm" maintenance branch.
94 It is intended to fill the niche for users who are not using distribution
95 kernels but want to use a regression-free kernel for a longer time.
97 Critical bug fixes to later 2.6 releases are often ported to this branch
98 which makes 2.6.32 a very useful base for many embedded developers seeking
99 stable APIs or those who do not need the latest bleeding edge features.
101 ... and no, this kernel has not undergone any specific QA testing.
103 See the original announcement by Greg Kroah-Hartman in the following
105 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
107 config KERNEL_V_2_6_31_14
111 config KERNEL_V_2_6_27_58
113 prompt "2.6.27.58 (longterm)"
115 The Linux 2.6.27 tree is a "longterm" maintenance branch.
117 It is intended to fill the niche for users who are not using distribution
118 kernels but want to use a regression-free kernel for a longer time.
120 Critical bug fixes to later 2.6 releases are often ported to this branch
121 which makes 2.6.27 a very useful base for many embedded developers seeking
122 stable APIs or those who do not need the latest bleeding edge features.
124 ... and no, this kernel has not undergone any specific QA testing.
126 See the original announcement by Adrian Bunk in the following mailing list
128 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
130 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
131 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
133 config KERNEL_LINUX_CUSTOM
135 prompt "custom tarball"
137 Use a local tarball of a complete kernel source tree.
139 config KERNEL_LINUX_CUSTOM_TARBALL
141 prompt "Path to custom tarball"
142 depends on KERNEL_LINUX_CUSTOM
144 Enter here the path to the tarball of your full kernel tree.
148 config KERNEL_VERSION
150 # Don't remove next line
151 # CT_INSERT_VERSION_STRING_BELOW
152 default "2.6.38.3" if KERNEL_V_2_6_38_3
153 default "2.6.38.2" if KERNEL_V_2_6_38_2
154 default "2.6.38.1" if KERNEL_V_2_6_38_1
155 default "2.6.38" if KERNEL_V_2_6_38
156 default "2.6.37.6" if KERNEL_V_2_6_37_6
157 default "2.6.36.4" if KERNEL_V_2_6_36_4
158 default "2.6.35.12" if KERNEL_V_2_6_35_12
159 default "2.6.34.8" if KERNEL_V_2_6_34_8
160 default "2.6.33.11" if KERNEL_V_2_6_33_11
161 default "2.6.32.38" if KERNEL_V_2_6_32_38
162 default "2.6.31.14" if KERNEL_V_2_6_31_14
163 default "2.6.27.58" if KERNEL_V_2_6_27_58
167 prompt "Kernel verbosity:"
168 default KERNEL_LINUX_VERBOSITY_0
170 config KERNEL_LINUX_VERBOSITY_0
174 Print simplified command lines.
176 config KERNEL_LINUX_VERBOSITY_1
178 prompt "Full commands"
180 Print full command lines.
182 config KERNEL_LINUX_VERBOSITY_2
184 prompt "Exec reasons"
186 Print the reasons why a make target is rebuild.
190 config KERNEL_LINUX_VERBOSE_LEVEL
192 default 0 if KERNEL_LINUX_VERBOSITY_0
193 default 1 if KERNEL_LINUX_VERBOSITY_1
194 default 2 if KERNEL_LINUX_VERBOSITY_2
196 config KERNEL_LINUX_INSTALL_CHECK
198 prompt "Check installed headers"
201 If you are in doubt that installed headers are buggy, say 'Y'
202 here to have an extra check passed onto the headers.
204 endif # KERNEL_LINUX_INSTALL
206 if KERNEL_LINUX_USE_CUSTOM_HEADERS
208 config KERNEL_LINUX_CUSTOM_IS_TARBALL
210 prompt "This is a tarball"
213 If you say 'n' here, the path below is expected to point to a directory
214 containing readily prepared headers
216 If you say 'y' here, then the path below is expected to point to a
217 tarball of such a directory.
219 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
220 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
222 Now, passing a tarball around is easier than passing a directory, so
223 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
224 say 'y' here, and enter the path to this tarball below.
226 config KERNEL_LINUX_CUSTOM_PATH
228 prompt "Path to custom headers directory/tarball"
230 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
232 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS