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_3
31 config KERNEL_V_2_6_38_2
35 config KERNEL_V_2_6_38_1
39 config KERNEL_V_2_6_38
43 config KERNEL_V_2_6_37_6
47 config KERNEL_V_2_6_36_4
51 config KERNEL_V_2_6_35_12
53 prompt "2.6.35.12 (longterm)"
55 The Linux 2.6.35 tree is a "longterm" maintenance branch.
57 It is intended to fill the niche for users who are not using distribution
58 kernels but want to use a regression-free kernel for a longer time.
60 Critical bug fixes to later 2.6 releases are often ported to this branch
61 which makes 2.6.35 a very useful base for many embedded developers seeking
62 stable APIs or those who do not need the latest bleeding edge features.
64 ... and no, this kernel has not undergone any specific QA testing.
66 See the original announcement by Andi Kleen in the following mailing
68 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
70 config KERNEL_V_2_6_34_8
74 config KERNEL_V_2_6_33_11
78 config KERNEL_V_2_6_32_38
80 prompt "2.6.32.38 (longterm)"
82 The Linux 2.6.32 tree is a "longterm" maintenance branch.
84 It is intended to fill the niche for users who are not using distribution
85 kernels but want to use a regression-free kernel for a longer time.
87 Critical bug fixes to later 2.6 releases are often ported to this branch
88 which makes 2.6.32 a very useful base for many embedded developers seeking
89 stable APIs or those who do not need the latest bleeding edge features.
91 ... and no, this kernel has not undergone any specific QA testing.
93 See the original announcement by Greg Kroah-Hartman in the following
95 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
97 config KERNEL_V_2_6_31_14
101 config KERNEL_V_2_6_27_58
103 prompt "2.6.27.58 (longterm)"
105 The Linux 2.6.27 tree is a "longterm" maintenance branch.
107 It is intended to fill the niche for users who are not using distribution
108 kernels but want to use a regression-free kernel for a longer time.
110 Critical bug fixes to later 2.6 releases are often ported to this branch
111 which makes 2.6.27 a very useful base for many embedded developers seeking
112 stable APIs or those who do not need the latest bleeding edge features.
114 ... and no, this kernel has not undergone any specific QA testing.
116 See the original announcement by Adrian Bunk in the following mailing list
118 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
120 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
121 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
123 config KERNEL_LINUX_CUSTOM
125 prompt "custom tarball"
127 Use a local tarball of a complete kernel source tree.
129 config KERNEL_LINUX_CUSTOM_TARBALL
131 prompt "Path to custom tarball"
132 depends on KERNEL_LINUX_CUSTOM
134 Enter here the path to the tarball of your full kernel tree.
138 config KERNEL_VERSION
140 # Don't remove next line
141 # CT_INSERT_VERSION_STRING_BELOW
142 default "2.6.38.3" if KERNEL_V_2_6_38_3
143 default "2.6.38.2" if KERNEL_V_2_6_38_2
144 default "2.6.38.1" if KERNEL_V_2_6_38_1
145 default "2.6.38" if KERNEL_V_2_6_38
146 default "2.6.37.6" if KERNEL_V_2_6_37_6
147 default "2.6.36.4" if KERNEL_V_2_6_36_4
148 default "2.6.35.12" if KERNEL_V_2_6_35_12
149 default "2.6.34.8" if KERNEL_V_2_6_34_8
150 default "2.6.33.11" if KERNEL_V_2_6_33_11
151 default "2.6.32.38" if KERNEL_V_2_6_32_38
152 default "2.6.31.14" if KERNEL_V_2_6_31_14
153 default "2.6.27.58" if KERNEL_V_2_6_27_58
157 prompt "Kernel verbosity:"
158 default KERNEL_LINUX_VERBOSITY_0
160 config KERNEL_LINUX_VERBOSITY_0
164 Print simplified command lines.
166 config KERNEL_LINUX_VERBOSITY_1
168 prompt "Full commands"
170 Print full command lines.
172 config KERNEL_LINUX_VERBOSITY_2
174 prompt "Exec reasons"
176 Print the reasons why a make target is rebuild.
180 config KERNEL_LINUX_VERBOSE_LEVEL
182 default 0 if KERNEL_LINUX_VERBOSITY_0
183 default 1 if KERNEL_LINUX_VERBOSITY_1
184 default 2 if KERNEL_LINUX_VERBOSITY_2
186 config KERNEL_LINUX_INSTALL_CHECK
188 prompt "Check installed headers"
191 If you are in doubt that installed headers are buggy, say 'Y'
192 here to have an extra check passed onto the headers.
194 endif # KERNEL_LINUX_INSTALL
196 config KERNEL_LINUX_USE_CUSTOM_HEADERS
198 prompt "pre-installed headers tree"
200 If you have some pre-installed kernel headers lying around, you can
201 enter the path to these headers, below, they will be copied from
202 there, and into the toolchain's sysroot.
205 This will *not* let you use a complete kernel tree!
206 If you want to use your own full kernel tree, then you want to
207 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
209 if KERNEL_LINUX_USE_CUSTOM_HEADERS
211 config KERNEL_LINUX_CUSTOM_IS_TARBALL
213 prompt "This is a tarball"
216 If you say 'n' here, the path below is expected to point to a directory
217 containing readily prepared headers
219 If you say 'y' here, then the path below is expected to point to a
220 tarball of such a directory.
222 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
223 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
225 Now, passing a tarball around is easier than passing a directory, so
226 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
227 say 'y' here, and enter the path to this tarball below.
229 config KERNEL_LINUX_CUSTOM_PATH
231 prompt "Path to custom headers directory/tarball"
233 See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
235 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS