4 select KERNEL_SUPPORTS_SHARED_LIBS
6 Build a toolchain targeting systems running Linux as a kernel.
10 prompt "Get kernel headers from:"
12 config KERNEL_LINUX_INSTALL
14 prompt "kernel's 'headers_install'"
16 This will make use of the new headers_install rule in recent kernels.
17 This is most probably what you want to use.
19 if KERNEL_LINUX_INSTALL
23 prompt "Linux kernel version"
24 # Don't remove next line
25 # CT_INSERT_VERSION_BELOW
27 config KERNEL_V_2_6_38_1
31 config KERNEL_V_2_6_38
35 config KERNEL_V_2_6_37_5
39 config KERNEL_V_2_6_37_4
43 config KERNEL_V_2_6_37_3
47 config KERNEL_V_2_6_37_2
51 config KERNEL_V_2_6_37_1
55 config KERNEL_V_2_6_37
59 config KERNEL_V_2_6_36_4
63 config KERNEL_V_2_6_35_11
65 prompt "2.6.35.11 (longterm)"
67 The Linux 2.6.35 tree is a "longterm" maintenance branch.
69 It is intended to fill the niche for users who are not using distribution
70 kernels but want to use a regression-free kernel for a longer time.
72 Critical bug fixes to later 2.6 releases are often ported to this branch
73 which makes 2.6.35 a very useful base for many embedded developers seeking
74 stable APIs or those who do not need the latest bleeding edge features.
76 ... and no, this kernel has not undergone any specific QA testing.
78 See the original announcement by Andi Kleen in the following mailing
80 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
82 config KERNEL_V_2_6_34_8
86 config KERNEL_V_2_6_33_8
90 config KERNEL_V_2_6_32_34
92 prompt "2.6.32.34 (longterm)"
94 The Linux 2.6.32 tree is a "longterm" maintenance branch.
96 It is intended to fill the niche for users who are not using distribution
97 kernels but want to use a regression-free kernel for a longer time.
99 Critical bug fixes to later 2.6 releases are often ported to this branch
100 which makes 2.6.32 a very useful base for many embedded developers seeking
101 stable APIs or those who do not need the latest bleeding edge features.
103 ... and no, this kernel has not undergone any specific QA testing.
105 See the original announcement by Greg Kroah-Hartman in the following
107 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
109 config KERNEL_V_2_6_31_14
113 config KERNEL_V_2_6_27_58
115 prompt "2.6.27.58 (longterm)"
117 The Linux 2.6.27 tree is a "longterm" maintenance branch.
119 It is intended to fill the niche for users who are not using distribution
120 kernels but want to use a regression-free kernel for a longer time.
122 Critical bug fixes to later 2.6 releases are often ported to this branch
123 which makes 2.6.27 a very useful base for many embedded developers seeking
124 stable APIs or those who do not need the latest bleeding edge features.
126 ... and no, this kernel has not undergone any specific QA testing.
128 See the original announcement by Adrian Bunk in the following mailing list
130 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
132 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
133 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
135 config KERNEL_LINUX_CUSTOM
137 prompt "custom tarball"
139 Use a local tarball of a complete kernel source tree.
141 config KERNEL_LINUX_CUSTOM_TARBALL
143 prompt "Path to custom tarball"
144 depends on KERNEL_LINUX_CUSTOM
146 Enter here the path to the tarball of your full kernel tree.
150 config KERNEL_VERSION
152 # Don't remove next line
153 # CT_INSERT_VERSION_STRING_BELOW
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.5" if KERNEL_V_2_6_37_5
157 default "2.6.37.4" if KERNEL_V_2_6_37_4
158 default "2.6.37.3" if KERNEL_V_2_6_37_3
159 default "2.6.37.2" if KERNEL_V_2_6_37_2
160 default "2.6.37.1" if KERNEL_V_2_6_37_1
161 default "2.6.37" if KERNEL_V_2_6_37
162 default "2.6.36.4" if KERNEL_V_2_6_36_4
163 default "2.6.35.11" if KERNEL_V_2_6_35_11
164 default "2.6.34.8" if KERNEL_V_2_6_34_8
165 default "2.6.33.8" if KERNEL_V_2_6_33_8
166 default "2.6.32.34" if KERNEL_V_2_6_32_34
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 config KERNEL_LINUX_USE_CUSTOM_HEADERS
213 prompt "pre-installed headers tree"
215 If you have some pre-installed kernel headers lying around, you can
216 enter the path to these headers, below, they will be copied from
217 there, and into the toolchain's sysroot.
220 This will *not* let you use a complete kernel tree!
221 If you want to use your own full kernel tree, then you want to
222 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
224 if KERNEL_LINUX_USE_CUSTOM_HEADERS
226 config KERNEL_LINUX_CUSTOM_IS_TARBALL
228 prompt "This is a tarball"
231 If you say 'n' here, the path below is expected to point to a directory
232 containing readily prepared headers
234 If you say 'y' here, then the path below is expected to point to a
235 tarball of such a directory.
237 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
238 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
240 Now, passing a tarball around is easier than passing a directory, so
241 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
242 say 'y' here, and enter the path to this tarball below.
244 config KERNEL_LINUX_CUSTOM_PATH
246 prompt "Path to custom headers directory/tarball"
248 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
250 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS