3 ## select KERNEL_SUPPORTS_SHARED_LIBS
5 ## help Build a toolchain targeting systems running Linux as a kernel.
7 config KERNEL_LINUX_USE_CUSTOM_HEADERS
9 prompt "Use pre-installed headers tree (OBSOLETE)"
12 If you have some pre-installed kernel headers lying around, you can
13 enter the path to these headers, below, they will be copied from
14 there, and into the toolchain's sysroot.
17 This will *not* let you use a complete kernel tree!
18 If you want to use your own full kernel tree, then you want to say 'N'
19 here, and select KERNEL_LINUX_CUSTOM, in the versions list, below.
21 if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
25 prompt "Linux kernel version"
26 # Don't remove next line
27 # CT_INSERT_VERSION_BELOW
45 config KERNEL_V_2_6_39_4
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_14
63 prompt "2.6.35.14 (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_10
84 config KERNEL_V_2_6_33_18
88 This is primarily for the use of those people who are stuck using the
89 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
90 is welcome to use this one as well.
92 config KERNEL_V_2_6_32_45
94 prompt "2.6.32.45 (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 "3.0.3" if KERNEL_V_3_0_3
157 default "3.0.2" if KERNEL_V_3_0_2
158 default "3.0.1" if KERNEL_V_3_0_1
159 default "3.0" if KERNEL_V_3_0
160 default "2.6.39.4" if KERNEL_V_2_6_39_4
161 default "2.6.38.8" if KERNEL_V_2_6_38_8
162 default "2.6.37.6" if KERNEL_V_2_6_37_6
163 default "2.6.36.4" if KERNEL_V_2_6_36_4
164 default "2.6.35.14" if KERNEL_V_2_6_35_14
165 default "2.6.34.10" if KERNEL_V_2_6_34_10
166 default "2.6.33.18" if KERNEL_V_2_6_33_18
167 default "2.6.32.45" if KERNEL_V_2_6_32_45
168 default "2.6.31.14" if KERNEL_V_2_6_31_14
169 default "2.6.27.59" if KERNEL_V_2_6_27_59
170 default "custom" if KERNEL_LINUX_CUSTOM
172 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
174 if KERNEL_LINUX_USE_CUSTOM_HEADERS
176 config KERNEL_LINUX_CUSTOM_PATH
178 prompt "Path to custom headers directory/tarball"
180 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
182 config KERNEL_LINUX_CUSTOM_IS_TARBALL
184 prompt "This is a tarball"
186 If you say 'n' here, the path above is expected to point to a directory
187 containing readily prepared headers
189 If you say 'y' here, then the path above is expected to point to a
190 tarball of such a directory.
192 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
193 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
195 Now, passing a tarball around is easier than passing a directory, so
196 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
197 say 'y' here, and enter the path to this tarball below.
199 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS