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
31 config KERNEL_V_2_6_37_34
35 config KERNEL_V_2_6_37_3
39 config KERNEL_V_2_6_37_2
43 config KERNEL_V_2_6_37_1
47 config KERNEL_V_2_6_37
51 config KERNEL_V_2_6_36_4
55 config KERNEL_V_2_6_35_11
57 prompt "2.6.35.11 (longterm)"
59 The Linux 2.6.35 tree is a "longterm" maintenance branch.
61 It is intended to fill the niche for users who are not using distribution
62 kernels but want to use a regression-free kernel for a longer time.
64 Critical bug fixes to later 2.6 releases are often ported to this branch
65 which makes 2.6.35 a very useful base for many embedded developers seeking
66 stable APIs or those who do not need the latest bleeding edge features.
68 ... and no, this kernel has not undergone any specific QA testing.
70 See the original announcement by Andi Kleen in the following mailing
72 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
74 config KERNEL_V_2_6_34_8
78 config KERNEL_V_2_6_33_7
82 config KERNEL_V_2_6_32_33
84 prompt "2.6.32.33 (longterm)"
86 The Linux 2.6.32 tree is a "longterm" maintenance branch.
88 It is intended to fill the niche for users who are not using distribution
89 kernels but want to use a regression-free kernel for a longer time.
91 Critical bug fixes to later 2.6 releases are often ported to this branch
92 which makes 2.6.32 a very useful base for many embedded developers seeking
93 stable APIs or those who do not need the latest bleeding edge features.
95 ... and no, this kernel has not undergone any specific QA testing.
97 See the original announcement by Greg Kroah-Hartman in the following
99 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
101 config KERNEL_V_2_6_31_14
105 config KERNEL_V_2_6_27_58
107 prompt "2.6.27.58 (longterm)"
109 The Linux 2.6.27 tree is a "longterm" maintenance branch.
111 It is intended to fill the niche for users who are not using distribution
112 kernels but want to use a regression-free kernel for a longer time.
114 Critical bug fixes to later 2.6 releases are often ported to this branch
115 which makes 2.6.27 a very useful base for many embedded developers seeking
116 stable APIs or those who do not need the latest bleeding edge features.
118 ... and no, this kernel has not undergone any specific QA testing.
120 See the original announcement by Adrian Bunk in the following mailing list
122 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
124 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
125 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
127 config KERNEL_LINUX_CUSTOM
129 prompt "custom tarball"
131 Use a local tarball of a complete kernel source tree.
133 config KERNEL_LINUX_CUSTOM_TARBALL
135 prompt "Path to custom tarball"
136 depends on KERNEL_LINUX_CUSTOM
138 Enter here the path to the tarball of your full kernel tree.
142 config KERNEL_VERSION
144 # Don't remove next line
145 # CT_INSERT_VERSION_STRING_BELOW
146 default "2.6.38" if KERNEL_V_2_6_38
147 default "2.6.37.34" if KERNEL_V_2_6_37_34
148 default "2.6.37.3" if KERNEL_V_2_6_37_3
149 default "2.6.37.2" if KERNEL_V_2_6_37_2
150 default "2.6.37.1" if KERNEL_V_2_6_37_1
151 default "2.6.37" if KERNEL_V_2_6_37
152 default "2.6.36.4" if KERNEL_V_2_6_36_4
153 default "2.6.35.11" if KERNEL_V_2_6_35_11
154 default "2.6.34.8" if KERNEL_V_2_6_34_8
155 default "2.6.33.7" if KERNEL_V_2_6_33_7
156 default "2.6.32.33" if KERNEL_V_2_6_32_33
157 default "2.6.31.14" if KERNEL_V_2_6_31_14
158 default "2.6.27.58" if KERNEL_V_2_6_27_58
162 prompt "Kernel verbosity:"
163 default KERNEL_LINUX_VERBOSITY_0
165 config KERNEL_LINUX_VERBOSITY_0
169 Print simplified command lines.
171 config KERNEL_LINUX_VERBOSITY_1
173 prompt "Full commands"
175 Print full command lines.
177 config KERNEL_LINUX_VERBOSITY_2
179 prompt "Exec reasons"
181 Print the reasons why a make target is rebuild.
185 config KERNEL_LINUX_VERBOSE_LEVEL
187 default 0 if KERNEL_LINUX_VERBOSITY_0
188 default 1 if KERNEL_LINUX_VERBOSITY_1
189 default 2 if KERNEL_LINUX_VERBOSITY_2
191 config KERNEL_LINUX_INSTALL_CHECK
193 prompt "Check installed headers"
196 If you are in doubt that installed headers are buggy, say 'Y'
197 here to have an extra check passed onto the headers.
199 endif # KERNEL_LINUX_INSTALL
201 config KERNEL_LINUX_USE_CUSTOM_HEADERS
203 prompt "pre-installed headers tree"
205 If you have some pre-installed kernel headers lying around, you can
206 enter the path to these headers, below, they will be copied from
207 there, and into the toolchain's sysroot.
210 This will *not* let you use a complete kernel tree!
211 If you want to use your own full kernel tree, then you want to
212 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
214 if KERNEL_LINUX_USE_CUSTOM_HEADERS
216 config KERNEL_LINUX_CUSTOM_IS_TARBALL
218 prompt "This is a tarball"
221 If you say 'n' here, the path below is expected to point to a directory
222 containing readily prepared headers
224 If you say 'y' here, then the path below is expected to point to a
225 tarball of such a directory.
227 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
228 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
230 Now, passing a tarball around is easier than passing a directory, so
231 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
232 say 'y' here, and enter the path to this tarball below.
234 config KERNEL_LINUX_CUSTOM_PATH
236 prompt "Path to custom headers directory/tarball"
238 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
240 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS