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_1
45 config KERNEL_V_2_6_39
49 config KERNEL_V_2_6_38_8
53 config KERNEL_V_2_6_37_6
57 config KERNEL_V_2_6_36_4
61 config KERNEL_V_2_6_35_13
63 prompt "2.6.35.13 (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_9
84 config KERNEL_V_2_6_33_14
88 config KERNEL_V_2_6_32_41
90 prompt "2.6.32.41 (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_59
113 prompt "2.6.27.59 (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.39.1" if KERNEL_V_2_6_39_1
153 default "2.6.39" if KERNEL_V_2_6_39
154 default "2.6.38.8" if KERNEL_V_2_6_38_8
155 default "2.6.37.6" if KERNEL_V_2_6_37_6
156 default "2.6.36.4" if KERNEL_V_2_6_36_4
157 default "2.6.35.13" if KERNEL_V_2_6_35_13
158 default "2.6.34.9" if KERNEL_V_2_6_34_9
159 default "2.6.33.14" if KERNEL_V_2_6_33_13
160 default "2.6.32.41" if KERNEL_V_2_6_32_40
161 default "2.6.31.14" if KERNEL_V_2_6_31_14
162 default "2.6.27.59" if KERNEL_V_2_6_27_59
164 endif # KERNEL_LINUX_INSTALL
166 if KERNEL_LINUX_USE_CUSTOM_HEADERS
168 config KERNEL_LINUX_CUSTOM_PATH
170 prompt "Path to custom headers directory/tarball"
172 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
174 config KERNEL_LINUX_CUSTOM_IS_TARBALL
176 prompt "This is a tarball"
178 If you say 'n' here, the path above is expected to point to a directory
179 containing readily prepared headers
181 If you say 'y' here, then the path above is expected to point to a
182 tarball of such a directory.
184 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
185 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
187 Now, passing a tarball around is easier than passing a directory, so
188 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
189 say 'y' here, and enter the path to this tarball below.
191 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS