3 ## select KERNEL_SUPPORTS_SHARED_LIBS
5 ## help Build a toolchain targeting systems running Linux as a kernel.
9 prompt "Get kernel headers from:"
11 config KERNEL_LINUX_INSTALL
13 prompt "kernel's 'headers_install'"
15 This will make use of the new headers_install rule in recent kernels.
16 This is most probably what you want to use.
18 config KERNEL_LINUX_USE_CUSTOM_HEADERS
20 prompt "pre-installed headers tree"
22 If you have some pre-installed kernel headers lying around, you can
23 enter the path to these headers, below, they will be copied from
24 there, and into the toolchain's sysroot.
27 This will *not* let you use a complete kernel tree!
28 If you want to use your own full kernel tree, then you want to
29 say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
33 if KERNEL_LINUX_INSTALL
37 prompt "Linux kernel version"
38 # Don't remove next line
39 # CT_INSERT_VERSION_BELOW
41 config KERNEL_V_2_6_39_2
45 config KERNEL_V_2_6_39_1
49 config KERNEL_V_2_6_39
53 config KERNEL_V_2_6_38_8
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_10
88 config KERNEL_V_2_6_33_15
92 config KERNEL_V_2_6_32_42
94 prompt "2.6.32.42 (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_59
117 prompt "2.6.27.59 (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.39.2" if KERNEL_V_2_6_39_2
157 default "2.6.39.1" if KERNEL_V_2_6_39_1
158 default "2.6.39" if KERNEL_V_2_6_39
159 default "2.6.38.8" if KERNEL_V_2_6_38_8
160 default "2.6.37.6" if KERNEL_V_2_6_37_6
161 default "2.6.36.4" if KERNEL_V_2_6_36_4
162 default "2.6.35.13" if KERNEL_V_2_6_35_13
163 default "2.6.34.10" if KERNEL_V_2_6_34_10
164 default "2.6.33.15" if KERNEL_V_2_6_33_15
165 default "2.6.32.42" if KERNEL_V_2_6_32_42
166 default "2.6.31.14" if KERNEL_V_2_6_31_14
167 default "2.6.27.59" if KERNEL_V_2_6_27_59
169 endif # KERNEL_LINUX_INSTALL
171 if KERNEL_LINUX_USE_CUSTOM_HEADERS
173 config KERNEL_LINUX_CUSTOM_PATH
175 prompt "Path to custom headers directory/tarball"
177 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
179 config KERNEL_LINUX_CUSTOM_IS_TARBALL
181 prompt "This is a tarball"
183 If you say 'n' here, the path above is expected to point to a directory
184 containing readily prepared headers
186 If you say 'y' here, then the path above is expected to point to a
187 tarball of such a directory.
189 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
190 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
192 Now, passing a tarball around is easier than passing a directory, so
193 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
194 say 'y' here, and enter the path to this tarball below.
196 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS